Plays for You, Fails to Download

The four causes

The private-window test settles the first and rules it out for the rest, which is why it is worth doing before anything else. It takes ten seconds and it is the only check that shows you what a downloader sees.

If the video plays for a logged-out visitor and still will not download, the cause is one of the other three — all of which are about where the request comes from rather than who is making it.

Being signed in changes more than people expect

An account is invisible while you have one, which is what makes this so confusing.

Signed in, a platform may show you: content from private accounts you follow, age-gated material, members-only videos, region-restricted content available in your account's country, and higher qualities reserved for subscribers. All of that looks like ordinary public video from inside.

Signed out, most of it disappears. A downloader has no account and never will — there is nothing for it to sign in with, and any service claiming otherwise is either using pools of accounts or asking for yours — the honest answer.

The pattern to recognise: if the private window shows a login prompt, an age gate or a subscribe wall, that is the whole explanation and no tool changes it.

Where the request comes from

The second half of the difference, and the part nobody can see.

Your connection belongs to a person in a place. A downloader's belongs to a server in a datacentre, usually in a different country. Platforms judge both, and they judge them differently.

Region. A video available where you are may be blocked where the server is, and the block that applies is the server's — which cuts both ways.

Datacentre suspicion. Servers make requests at machine speed, which is what scraping looks like, so some platforms refuse them outright and others throttle them sooner. Your home connection is never treated that way — tested per platform.

Neither is something a tool can engineer around honestly. Rotating through addresses until one is not blocked is the technique that exists, and it is fragile, against platform terms, and the mechanism behind most claims to bypass restrictions.

The timing clue

When it worked earlier and does not now, the cause is usually rate limiting rather than anything about the video.

The tell is a run of downloads shortly before. Platforms escalate: slower answers, then fewer formats offered, then a refusal or a bot check. By the time it is obvious, several requests have already been counted — the escalation in detail.

The correct response is the opposite of the instinctive one. Retrying extends the limit you are waiting out; waiting a few minutes clears it. Your browser meanwhile is unaffected, which is exactly why the video still plays for you.

The same thing happens on shared connections without you doing anything. On an office or campus network everyone shares one public address, so you can inherit someone else's throttling on your first attempt of the day.

Working through it in order

1. Open the link in a private window. If it does not play there, no tool will reach it and you have your answer.
2. Try a different video from the same platform. If others work, the problem is this video; if none do, it is the platform.
3. Try a video from a different platform. If that works, the tool is fine.
4. Wait ten minutes. If it then works, that was rate limiting.
5. Read the message. A specific one names the cause; a generic one usually means the platform refused before saying anything — what each message means.

Four checks, about a minute, and they distinguish every cause on this page. Trying another download service instead is the common move and rarely helps, because the constraint is almost never the software.

What is genuinely worth trying

• A different quality. Occasionally a specific rung is unavailable while others are fine.
• The audio option. A different delivery path, and sometimes the one still working.
• Waiting. Free, and it fixes throttling and processing delays on new uploads.
• Another copy of the video. Reposts have different restrictions; lower quality, and it exists.
• A local tool. It runs from your own connection, so it inherits your standing rather than a server's — with the trade-offs involved.

The last one is the only genuine fix for the datacentre problem, and it is worth knowing that it exists rather than concluding the video is unreachable.