Technical
Why a download fails, and what cookies actually do
A downloader is a small program that asks a platform the same questions a browser asks, and then saves the answer instead of playing it. Almost every failure is one of those questions being refused. Sorting the refusals into four families turns a wall of red text into a decision.
Family one: the work is not there
This video is unavailable, private video, removed by the uploader, not available in your country. Nothing is broken on your side. The platform will not serve the file to anyone without the right relationship to it — the uploader's permission, a session, or a network location inside the licensed territory.
Check the link in a normal browser, signed out. If it does not play there either, the desk cannot help. A private video is a permissions problem, not a formatting problem.
Family two: the platform wants a session
Instagram, Facebook, X and parts of YouTube increasingly require a logged-in session before they serve media. To the platform, "logged in" means a cookie — a small token your browser presents with each request, issued after you proved you were you.
A cookie file is that token, exported. You can produce one with a browser extension that writes Netscape-format cookies, save it next to the desk as cookies.txt, and restart. The desk now asks its questions as you.
- Use a session you are comfortable exporting. A cookie is a credential: anyone holding it can act as that session until it expires or you sign out everywhere.
- Export only the site you need. Some extensions dump cookies for every domain; trim the file to the platform in question.
- Re-export when it stops working. Sessions expire, and a stale cookie produces exactly the same "login required" error as no cookie at all.
A cookie is a borrowed key. Borrow it for one door, keep it in one place, and throw it away when you are done.
Family three: you are being rate-limited
HTTP Error 429, too many requests, or a sudden run of failures after a long queue. Platforms meter requests per address, and a home connection that pulls forty videos in ten minutes looks like a scraper. The fix is patience, not cleverness: wait, lower concurrency, and download in batches you would be comfortable explaining.
This is also why public download sites break constantly and why a local desk is more stable — you are one address with one ordinary pattern, not ten thousand strangers sharing one reputation.
Family four: the file is protected, or the tool is stale
Two different problems share a symptom.
DRM. Subscription services wrap video in Widevine, FairPlay or PlayReady. The bytes on the wire are encrypted and the key is issued only to a licensed player. No cookie, header or flag changes that, and a tool that claims otherwise is either breaking the law or selling you malware. This desk declines DRM-protected sources outright.
Stale extractors. A platform renames a field and the extraction recipe stops matching. The engine reports something cryptic and every link to that site fails at once. The cure is a one-line update — py -m pip install -U yt-dlp — because the project ships fixes within days of a break.
Reading the message instead of the wall
Errors arrive with a prefix and a sentence. The prefix tells you where to look:
| Message begins with | Meaning | What to do |
|---|---|---|
[youtube] … unavailable | The item is gone or gated | Verify in a browser, signed out |
Sign in to confirm… | Session required | Add a fresh cookies.txt |
HTTP Error 429 | Rate limited | Wait; reduce the batch |
Requested format is not available | That resolution is not offered | Pick a lower rung or best |
Unsupported URL | Not a single video page | Open the item and copy its own link |
The short version
Unavailable means unavailable. Login walls are solved with your own session, exported deliberately and kept briefly. Rate limits are solved with patience. DRM is not solved at all, and a tool that says otherwise is lying. Everything else is usually a stale engine waiting for one update.