Fix yt-dlp HTTP Error 403: Forbidden (2026)

If you've run yt-dlp on a YouTube URL and hit this wall:

Windows PowerShell — yt-dlp 403 Error

Error Reproduced

Terminal log capturing the missing FFmpeg warning and subsequent HTTP Error 403: Forbidden download failure.

...you're not alone. This is one of the single most common yt-dlp errors in 2026, and it almost always comes down to one of three things:

• 1An outdated yt-dlp version missing the latest YouTube player signature patches.
• 2A missing FFmpeg install, forcing yt-dlp into throttled pre-muxed legacy formats.
• 3YouTube rejecting the default extraction client (web client) yt-dlp is using.

Here's exactly why it happens and the step-by-step blueprint to fix it immediately.

Video Walkthrough: Watch How to Fix the 403 Error

Prefer a quick visual walkthrough? Here is the complete step-by-step video tutorial demonstrating the error in real-time and running through the exact working fix:

Why This Happens

YouTube frequently changes its backend signing algorithms, n-sig challenges, and player JavaScript logic to prevent unauthorized downloading.

When yt-dlp's extractor is out of date or uses a client that YouTube's bot-detection has flagged, the URLs it pulls for video/audio streams are often already invalid or tied to a session/client YouTube no longer trusts — resulting in an HTTP 403 Forbidden error the moment your system tries to actually fetch the raw video chunks from Google's CDN servers.

The Step-by-Step Fix

Step 1Update yt-dlp to the Latest Version

This alone fixes the issue most of the time, since the yt-dlp core team ships frequent patches for exactly this kind of breakage. If you downloaded a binary months ago, it is almost certainly attempting to solve obsolete player challenges.

If using the standalone binary / Windows:

yt-dlp -U

If installed via pip (Python):

pip install -U yt-dlp

If installed via Homebrew (macOS / Linux):

brew upgrade yt-dlp

If installed via winget (Windows):

winget upgrade yt-dlp

Step 2Install FFmpeg and Add It to PATH

Have you seen this warning in your terminal?

Why this causes 403 errors: YouTube serves modern high-resolution video (1080p, 1440p, 4K) as separate video-only and audio-only DASH streams. Without FFmpeg, yt-dlp cannot combine these streams into a single container. Instead, it falls back to a single lower-quality pre-muxed format (such as format 18 at 360p or format 22) — which YouTube aggressively throttles and subjects to stricter CDN token expirations, leading directly to 403 Forbidden rejections.

Install FFmpeg on Windows via Winget:

winget install ffmpeg

Install FFmpeg on macOS via Homebrew:

brew install ffmpeg

Install FFmpeg on Ubuntu / Debian Linux:

sudo apt update && sudo apt install ffmpeg

Step 3Force a Working Player Client (The Real Fix)

This is usually the definitive fix when updating alone doesn't resolve it. By default, yt-dlp attempts to extract streams using YouTube's standard web browser client. When YouTube tightens server-side restrictions on web clients, mobile and TV clients continue functioning smoothly.

You can override the extractor client on the fly using the --extractor-args parameter:

Option A: Force the Android Player Client (Recommended)

yt-dlp --extractor-args "youtube:player_client=android" https://www.youtube.com/watch?v=VIDEO_ID

Option B: Force the Smart TV Player Client

yt-dlp --extractor-args "youtube:player_client=tv" https://www.youtube.com/watch?v=VIDEO_ID

Option C: Force the iOS Player Client

yt-dlp --extractor-args "youtube:player_client=ios" https://www.youtube.com/watch?v=VIDEO_ID

Step 4Pass Cookies from Your Browser (If Still Failing)

Some YouTube videos require an authenticated session (e.g. age-restricted videos, private member streams, or requests coming from data center IPs that trigger Cloudflare / Google bot challenges). You can supply cookies directly from your installed desktop browser:

Export session cookies from Google Chrome:

yt-dlp --cookies-from-browser chrome https://www.youtube.com/watch?v=VIDEO_ID

Or from Firefox, Edge, or Brave:

yt-dlp --cookies-from-browser firefox https://www.youtube.com/watch?v=VIDEO_ID
yt-dlp --cookies-from-browser edge https://www.youtube.com/watch?v=VIDEO_ID
yt-dlp --cookies-from-browser brave https://www.youtube.com/watch?v=VIDEO_ID

The All-In-One Fix Command

If you just want one single command to copy, paste, and run in your terminal that updates yt-dlp, installs FFmpeg, and downloads with the Android client in highest quality:

Windows (PowerShell):

yt-dlp -U ; winget install ffmpeg ; yt-dlp --extractor-args "youtube:player_client=android" -f best https://www.youtube.com/watch?v=VIDEO_ID

macOS / Linux (Bash):

yt-dlp -U && yt-dlp --extractor-args "youtube:player_client=android" -f best https://www.youtube.com/watch?v=VIDEO_ID

Make It Permanent with a Config File

Instead of typing --extractor-args every time you download, you can persist this configuration in yt-dlp's global config file:

• Windows path: %APPDATA%\yt-dlp\config (e.g. C:\Users\<You>\AppData\Roaming\yt-dlp\config)
• macOS / Linux path: ~/.config/yt-dlp/config

Add the following settings to your config file:

# Force the reliable Android client by default
--extractor-args "youtube:player_client=android"

# Automatically merge best video and audio using FFmpeg
-f "bv*+ba/b"
--merge-output-format mp4

# Embed thumbnail and metadata
--embed-thumbnail
--embed-metadata

Still Seeing 403 Forbidden? Check Upstream Patches

If you're still seeing a 403 after applying all four steps, YouTube likely deployed a zero-day structural change to their video delivery network within the last few hours.

Check the active issues on the official yt-dlp GitHub issues repository . YouTube-side changes almost always have a thread with thousands of comments and maintainers posting hotfix pull requests or alternative player client arguments within hours.

Run with full verbose logging to inspect the exact failing URL:

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

Quick Troubleshooting Matrix

Frequently Asked Questions