Exe versus zip
OBS Studio ships Windows x64 payloads on GitHub Releases: a Nullsoft installer exe as the default, and a portable zip as supporting. Public copy still says the current release. Latest/download URLs omit the tag.
Winget does not install the zip. It wraps the exe for id OBSProject.OBSStudio:
winget install -e --id OBSProject.OBSStudioRelated: install on Windows, winget command, obs studio releases, and obs studio for this computer.
Default x64 Nullsoft installer
The file of record is OBS-Studio-*-Windows-x64-Installer.exe. It is the standard Windows installer for Intel or AMD 64-bit PCs. It adds OBS Studio to the Start menu and installs it like a normal app. Winget metadata puts that family at %ProgramFiles%\obs-studio on x64.
Nullsoft is the installer type in winget-pkgs. Scope is machine. Daily users double-click the exe or run winget. the guides do not invent extra Silent flags the project does not document as the typed command.
You do not install a separate runtime as a second CopyRow after this exe. Local record still needs no OBS Project account.
Portable zip and OBS64.exe
OBS-Studio-*-Windows-x64.zip is for portable use, testing, or running without a machine-scope setup. Extract it first, then run bin/64bit/obs64.exe. That inner path is what winget-pkgs lists for the zip shape.
A portable folder is a good fit when you want the app next to a USB work tree, or when you cannot run a machine-scope exe. It is a worse fit when you want Start menu registration and winget upgrade. Winget will not keep a loose zip folder updated. You replace the folder yourself from the current release.
Do not treat the zip as a second product. It is the same OBS Studio tree in archive form. After extract, run obs64.exe from bin/64bit. If two copies sit on the PC, run one.
VCRedist for the zip path
Winget-pkgs notes Microsoft.VCRedist.2015+.x64 on the portable zip installer entry. That note is from the catalog yaml, not a second CopyRow on the exe path. If obs64.exe from a zip extract fails to start with a runtime error, install the current Microsoft Visual C++ 2015 or later x64 redistributable, then retry.
The Nullsoft exe path does not list that redistributable as a separate command of record. Do not paste a VCRedist winget line as a substitute for OBSProject.OBSStudio. The command of record stays the OBS Project id.
Official site: obsproject.com. License: GPL-2.0 in COPYING. Help: obsproject.com/help.
File chooser
| File | Role | Run it? |
|---|---|---|
OBS-Studio-*-Windows-x64-Installer.exe | Default 64-bit Nullsoft installer | Yes, on x64 Windows |
OBS-Studio-*-Windows-x64.zip | Portable zip | Extract, then run bin/64bit/obs64.exe |
Winget id OBSProject.OBSStudio | Catalog wrap of the exe | Yes, when App Installer works |
OBS-Studio-*-Windows-arm64.zip | ARM64 portable | Supporting. Not the x64 path. |
| macOS dmg / Ubuntu deb | Other OS assets on the tag | Supporting mention only |
| PDBs, dSYMs, Sources | Debug or source archives | Skip for daily use |
| GitHub automatic source zip | Source snapshot | Skip as the daily install |
Safe-download framing: download obs studio safely. Trust notes: is obs studio safe. Repo: obs studio on GitHub. Product home: obsproject.com.
Supporting assets to skip
Hashes, if a tag publishes them, are checksums, not an installer. Debug symbol archives are for people who already debug. Skip them on a normal PC. Automatic GitHub source zips and tarballs are not the Nullsoft exe.
A USB work folder is the usual reason to take the zip. Keep the extract on media you control. Do not unpack into C:\Windows. After you finish, you can delete the folder. Exe and winget copies uninstall through Apps settings instead.
Pick one copy
Installed exe and winget share Program Files. Portable zip lives wherever you extracted it. Keep one. After you pick, add a source: first scene and source. Record: record locally. Virtual camera: virtual camera.
the guides map Windows x64. ARM64 zip, macOS dmg, and Ubuntu deb can exist on the same tag. Do not mint extra install URLs for them here. Home: obs studio. Guides: guides. About: about. Move off Game Bar: move off Game Bar.
Frequently asked questions
Should I use the portable zip or the installer exe?
Use OBS-Studio-*-Windows-x64-Installer.exe, or winget, when you want a Start-menu install in Program Files. Use OBS-Studio-*-Windows-x64.zip when you want a folder you can move. Both sit on GitHub Releases. Match the Windows x64 installer or winget id OBSProject.OBSStudio against the current GitHub release before you change anything else.
Does winget install the portable archive?
No. Winget wraps the Nullsoft exe for id OBSProject.OBSStudio. Portable is a zip on the same GitHub tag. Command: winget command. Setup path: install on Windows. Match the Windows x64 installer or winget id OBSProject.OBSStudio against the current GitHub release before you change anything else.
Where is the portable executable?
After you extract the x64 zip, run bin/64bit/obs64.exe. That path is what winget-pkgs lists for the zip installer shape. Match the Windows x64 installer or winget id OBSProject.OBSStudio against the current GitHub release before you change anything else.
Does the zip need a Visual C++ runtime?
Winget-pkgs notes Microsoft.VCRedist.2015+.x64 on the zip path. The Nullsoft exe path does not list that as a separate command. Install the current VC++ 2015+ x64 redistributable from Microsoft if the portable exe fails to start. Match the Windows x64 installer or winget id OBSProject.OBSStudio against the current GitHub release before you change anything else.
What about ARM64, macOS, or Ubuntu files?
Those assets can sit on the same GitHub tag. the guides map Windows x64. Take the x64 installer exe or the x64 zip. Match the Windows x64 installer or winget id OBSProject.OBSStudio against the current GitHub release before you change anything else.