Troubleshooting guide
"Forcing SABR streaming" and then a 403
yt-dlp prints a warning that some formats were skipped because YouTube is "forcing SABR streaming," and then the download dies with HTTP Error 403: Forbidden. This is a different problem from an ordinary 403 — it's about howYouTube is handing out the media, not just whether your request was allowed. Here's what it means and the fixes in the order that actually helps.
The warning you're seeing
WARNING: [youtube] Some web client https formats have been skipped as they are
missing a url. YouTube is forcing SABR streaming for this client.
...
ERROR: unable to download video data: HTTP Error 403: ForbiddenSABR (Server-side Adaptive BitRate) is YouTube's newer streaming delivery. For some clients YouTube no longer returns plain progressive/DASH URLs you can GET directly — it only offers the SABR stream. yt-dlp can't pull a direct file out of that for every client, so it skipsthose formats. If the only formats left still need a token your request doesn't carry, the actual media request comes back 403.
The official yt-dlp PO Token guide is blunt about the underlying cause: without the right token, "requests for the affected clients' format URLs may return HTTP Error 403, or result in your account or IP address being blocked." So the fix is about giving yt-dlp a client that still returns real URLs, plus the token those URLs now require.
Fix 1: update yt-dlp first (not optional)
SABR handling and the default client list change almost every release. A build from a few weeks ago can be forcing SABR on clients that a current build already works around. Update before you touch any flags:
yt-dlp -U # if you installed the standalone binary
python3 -m pip install -U yt-dlp # if you installed via pip
yt-dlp --version # confirm you're on a recent buildIf you're still broken on the latest stable, try the nightly channel (yt-dlp --update-to nightly) — SABR fixes often land there first.
Fix 2: make sure a JS runtime is present
yt-dlp needs a JavaScript engine to solve YouTube's challenges and unlock the full format list. Without one it falls back to a reduced set of clients — exactly the ones most likely to be SABR-only. Check what it found:
yt-dlp -v --simulate "https://www.youtube.com/watch?v=jNQXAC9IVRw" 2>&1 | grep -i runtime
# [debug] JS runtimes: deno-2.9.8Empty output means no runtime. This bites server and Docker setups most — see Fix "No supported JavaScript runtime" in Docker.
Fix 3: supply a GVS PO token
The format URLs that survive now want a GVS PO token (the token for Google Video Server requests — the actual media streams). Check whether yt-dlp has a provider:
yt-dlp -v --simulate "https://www.youtube.com/watch?v=jNQXAC9IVRw" 2>&1 | grep -i "pot"
# [debug] [youtube] [pot] PO Token Providers: none <- nothing to issue tokensIf it says none, install the maintained PO token provider plugin, bgutil-ytdlp-pot-provider (it's maintained by a yt-dlp maintainer). The yt-dlp guide no longer recommends pasting tokens by hand, because YouTube now binds them to the video ID — a provider regenerates them per video. Once it's installed, that debug line should list a provider and the skipped formats come back. On a headless box, run the provider as a sidecar — see Run a PO token provider on a server.
About the "just switch player_client" advice
Forum threads will tell you to force a specific client, e.g. --extractor-args "youtube:player_client=..." with android_vr, tv, or web_embedded. Sometimes one of them still returns direct URLs. Treat these as temporary: which clients are SABR-only changes constantly, and the clients people recommended a month ago are often the ones throwing 403 today (the android_vr 403 report, yt-dlp issue #17456, is already closed). If a client flag works, keep it in a config file but expect to revisit it — the durable fix is Fixes 1–3, not a hardcoded client.
Still 403 on a server? It's probably the IP
Here's the trap: you add a runtime and a PO token provider, it works on your laptop, and the same setup still 403s on an AWS/GCP/Hetzner box. A PO token doesn't launder a datacenter IP. YouTube flags those ranges, and the official guide explicitly warns the result can be a blocked IP. On a flagged IP you need requests to come from a residential address — see yt-dlp works locally but not on my server for cookies and residential-proxy options.
Servers & agents
Works on your laptop but not on the server?
Paste a link to see what a hosted API returns from a clean residential IP — no cookies, proxies, or runtime to maintain on the box.