---
title: "yt-dlp not working on YouTube: a ten-minute triage"
description: "Sort a failing yt-dlp command into one of five causes by reading the error line, then apply the matching check instead of guessing."
url: https://tornadoapi.io/blog/yt-dlp-not-working-youtube
published: 2026-11-14
---

# yt-dlp not working on YouTube: a ten-minute triage

When yt-dlp stops working on YouTube, the error line already tells you which family of problem you have. Read it before changing anything. Most failures fall into five groups, and each has one check that confirms it.

## Start with two commands

```bash
yt-dlp --version
yt-dlp -v "https://www.youtube.com/watch?v=VIDEO_ID"
```

Compare the version with the latest release. Then read the last `ERROR:` line of the verbose output and find it in the table.

| Error line contains | Family | First check |
|---|---|---|
| `HTTP Error 403: Forbidden` | Media request refused | Update, clear cache, download in one step |
| `Sign in to confirm you're not a bot` | Address or volume challenged | Try another network |
| `Requested format is not available` | Format selection | List formats with `-F` |
| `Video unavailable`, `Private video`, `members-only` | Content restriction | Open the URL in a private browser window |
| `Unable to extract`, `nsig extraction failed` | yt-dlp behind YouTube | Update to the latest or nightly release |

## The five families

**1. yt-dlp is behind YouTube.** Extraction errors that appear overnight on every video usually mean YouTube changed something. Update:

```bash
yt-dlp -U
```

If the latest stable release still fails, check the project's open issues and try the nightly channel with `yt-dlp --update-to nightly`. Recent releases also need a JavaScript runtime for full YouTube support; the verbose log says when one is missing.

**2. The media request is refused.** A 403 after formats were found has its own causes and checks, covered in [yt-dlp 403 Forbidden](https://tornadoapi.io/blog/yt-dlp-403-error-fix).

**3. The address or the volume is challenged.** The sign-in message is a decision about your address, not about the video. See [Sign in to confirm you're not a bot](https://tornadoapi.io/blog/sign-in-to-confirm-you-are-not-a-bot) for what lasts and what does not.

**4. The format selector asks for something that does not exist.** List what is offered, then relax the selector:

```bash
yt-dlp -F URL
yt-dlp -f "bv*+ba/b" URL
```

A selector written for one video, with a fixed format code or a fixed container, fails on videos that do not offer it. Merging separate video and audio streams also requires FFmpeg on the machine.

**5. The content is restricted.** Private, removed, age-restricted, members-only and region-restricted videos fail whatever the tool. Confirm in a private browser window from the same country as your server. These are outcomes to record, not errors to retry.

## Is it one failure or a pattern

A single failing video is a triage problem and the table above settles it. A failure rate is a different problem. If you run downloads in a backend, log the error family of every failure for a week. Two results are common:

- Families 4 and 5 dominate. Your pipeline is healthy; improve format selection and handle restricted content as a normal result.
- Families 1 to 3 dominate and grow with traffic. The failures come from operating downloads against YouTube at volume. Updates, addresses and sessions have become recurring work.

In the second case, compare the hours you spend on that work with the cost of handing the download step to a service.

## Handing off the download step

[Tornado API](https://tornadoapi.io/youtube-downloader-api) takes a source URL and returns a job. You follow the job to a final status and receive the file in your storage. Restricted content ends in a recorded outcome with its reason, and 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. A useful test is to replay last week's failed URLs and compare. The [migration guide](https://tornadoapi.io/vs/yt-dlp) lists what remains in your application afterwards: source selection, naming and everything downstream of the file.

## Sources

- [yt-dlp README: update channels](https://github.com/yt-dlp/yt-dlp#update)
- [yt-dlp wiki: FAQ](https://github.com/yt-dlp/yt-dlp/wiki/FAQ)
- [yt-dlp wiki: PO Token Guide](https://github.com/yt-dlp/yt-dlp/wiki/PO-Token-Guide)
