Desktop troubleshooting
Source sign-in, tools, and optional remote fallbacks.
A source returns 403
The site rejected the request. Update managed tools, check that the media remains available, and refresh an authorized session you intentionally use. Not every 403 means a tool is missing.
The app does not bypass DRM, paywalls, or access controls. Private media still requires permission.
Browser cookies
Site sign-in is optional. Authorized browser profiles or Netscape-format cookies.txt files can be supplied to local extractors. A selected file takes precedence over direct browser access.
Firefox is the documented reliable direct-browser option on Windows. Chromium can lock its cookie database, and newer browser protections can prevent external decryption. The app does not terminate browsers or weaken those protections. Use an authorized Firefox session or fresh cookie export when appropriate.
Never upload cookie exports to public issues or partner API requests.
Remote fallbacks
Configure self-hosted providers or endpoints whose owners permit your use. A provider can see the source URL and network request. Arbitrary public endpoint lists are not a dependable or private service.
The README explains which credentials stay in memory and which settings persist. The optional Instagram embed fallback is disabled by default and does not receive cookies or provider credentials.
Existing files and history
The app avoids overwriting existing files. Choose another destination or inspect the existing output. Desktop history is separate from website playlists.
Report bugs through the Desktop issue tracker, with secrets and signed URLs removed.