Full build
Best first install for most people who want the smoother setup path.
Download FullThe cleanest path is simple: most people should use Full, download from GitHub Releases, verify SHA256 if they want an extra check, then run the installer.
Best first install for most people who want the smoother setup path.
Download FullBetter when you prefer to keep more of the tooling boundary under your own control.
Download LiteIf you want the most cautious install flow, verify SHA256 before running the installer and start from GitHub Releases.
Verify SHA256The install process should be direct: choose the right build, verify if you want the extra check, then run the installer and launch the app.
Most people should choose Full. Use Lite only if you actively prefer managing more of the yt-dlp and ffmpeg boundary yourself. Use WinGet for convenience, not as the most authoritative release source.
Open the latest GitHub Release and download the Full or Lite installer from there. WinGet is supported, but the release page is the direct route to the newest build.
Open SHA256SUMS.txt from the same release and compare the installer hash before first run. This matters more because the installer is not code-signed yet.
Finish the setup flow, launch the app, and confirm the Windows-first UI opens correctly. If SmartScreen warns, verify source plus checksum before continuing.
That warning is expected while the installer is not code-signed. Do not treat it as a reason to skip verification. Treat it as a reason to verify source plus SHA256 first.
If you are ready to install, the download page is still the main decision page. If you want more proof before first run, go straight to the SHA256 guide.