ERROR: [youtube] VIDEO_ID: Sign in to confirm you're not a bot is YouTube refusing to describe the video to an anonymous request. yt-dlp only relays the message. Nothing is wrong with the video or with your command: YouTube has decided that requests from your address need a signed-in user.
Where the message comes from
YouTube scores incoming requests. When the score is poor, it stops answering anonymous requests for video data and asks for a sign-in. Two inputs weigh the most:
- The address. Cloud and hosting ranges are distrusted from the first request. The same command often works on a laptop at home and fails on a server.
- The volume. An address that was fine yesterday is challenged after enough requests. The threshold is not published and it moves.
This is why the usual first reactions do nothing. Restarting the process, rebuilding the container or reinstalling yt-dlp keeps the same address, so the challenge stays.
Workarounds and what they cost
Update first. yt-dlp -U rules out the case where an old release makes requests that look unusual. It is free and takes seconds.
Slow down. If the challenge appears in the middle of a long run, add pauses:
yt-dlp --sleep-requests 1 --sleep-interval 5 --max-sleep-interval 15 URL
This delays the challenge on a trusted address. It does not lift one that is already in place.
Use another network. A different address has a different history. This confirms the diagnosis: if the command works elsewhere, your address is the cause.
Pass browser cookies. The message itself suggests it, and yt-dlp supports it:
yt-dlp --cookies-from-browser firefox URL
It works because requests now belong to a signed-in account. Read the cost before putting it in production:
- The account carries the risk. The yt-dlp wiki warns that an account used with yt-dlp can be banned, temporarily or permanently. Never use an account you care about.
- Cookies expire and rotate. A browser session exported to a server stops working, and someone has to export it again.
- One account is one identity. Volume through a single account gets that account challenged too.
Buy other addresses. Residential proxies move the requests to addresses with a better reputation. You pay per gigabyte for video traffic, the reputation still wears out with use, and you now operate a rotation system.
Why it returns on servers
On one laptop, updating and slowing down is usually enough. A backend is in the opposite position on both inputs: it runs on hosting addresses and it sends many requests. Teams commonly go through the same sequence. First proxies. Then cookies, when proxies start being challenged. Then several accounts, when the first one is flagged. Each step works for a while and adds something to maintain, and none of it is the product the team set out to build.
The practical test is simple. Track the share of downloads that fail with this message per day. If it stays near zero, your setup is fine. If it climbs with your traffic, the problem is structural and more tuning will only move the date of the next incident.
Getting the file without the challenge
If what you need is the file, a job API moves the whole problem out of your code. With Tornado API the request contains no cookies and no account of yours:
curl -X POST "https://api.tornadoapi.io/jobs" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://www.youtube.com/watch?v=VIDEO_ID"}'
You receive a job_id, follow the job to its final status and collect the file from your storage. Failed jobs are not billed. Over a 14-day window measured in October 2026, 236,054 jobs ran with 0 extraction failures.
Eligible new accounts get 100 GB free for 7 days. Use them on the exact URLs that are challenged in your environment, then compare the outcomes. The first workflow guide walks through one job from the dashboard to the API, and yt-dlp 403 Forbidden covers the other common failure.
Limits
Some videos require a signed-in viewer for reasons unrelated to bot detection, such as age restrictions or channel memberships. Those remain restricted whichever tool you use, and a job reports them as content issues. Only download content you are authorized to use.