Troubleshooting / 7 min read
Why online video downloads fail and how to fix them
Most failures come from wrong link types, private or expired content, source-side rate limits, missing media variants, browser save permissions, or temporary parser changes on the platform.
Updated 2026-06-27
Quick answer
Most failures come from wrong link types, private or expired content, source-side rate limits, missing media variants, browser save permissions, or temporary parser changes on the platform.
- First verify that the URL is a specific public media page, not a profile, search, feed, or app page.
- Retry with queue mode for long videos, HLS streams, batch tasks, and unstable source servers.
- If a platform has changed its page format or anti-bot behavior, a parser update may be required.
Check the link type first
FreeSaveVideo routes URLs through platform matchers and service parsers. Those parsers need concrete media identifiers, source metadata, or supported embed data. A profile page or search result usually does not contain one clear downloadable target.
The project has platform-specific guidance for Douyin search and profile links, Weibo video address links, Haokan public video pages, and Bilibili multi-part content because each platform exposes media differently.
Understand source-side failures
A public link can still fail when the source platform expires a token, blocks a region, changes its page structure, hides media behind login, or serves incomplete metadata. Recent project work added generic HTML probing, yt-dlp fallback paths, TikTok-specific handling, and upstream failover tracing to reduce these failures.
When a failure is temporary, retrying later or switching networks can help. When a platform changes its page format, code needs to be updated.
Separate parsing problems from saving problems
Parsing means FreeSaveVideo found a usable media result. Saving means the browser or queue successfully wrote the file. If a queue item completes but you cannot find the file, check whether it still needs a Save click or whether auto-save directory permission was granted.
Reference table
| Symptom | Likely cause | Fix |
|---|---|---|
| No result | Wrong link type or private/deleted media | Copy a specific public video or post URL |
| Only low quality | Source exposes limited variants | Change quality settings and parse again |
| Long task stalls | Large media, HLS, or unstable source | Use queue mode and keep the tab open |
| File not found after queue | Save step not completed | Click Save or enable auto-save directory |
| Platform suddenly fails | Source page or anti-bot change | Retry later and report the failing public URL |
FAQ
Why does a link work in the app but not in a browser downloader?
Apps can use authenticated or private APIs. A public browser downloader should only use publicly accessible media and metadata.
Why does queue mode help?
Queue mode gives long or multi-step downloads more room for retries, continuation, and explicit saving than a single direct browser download.
What should I include in a bug report?
Include the public URL, platform name, whether direct or queue mode was used, the selected output settings, and the visible error message.