Practical yt-dlp docs: install, commands, fixes, cookies, and workflows.
Current section
Troubleshooting & Errors hub
Fix yt-dlp faster by identifying the error bucket first instead of thrashing randomly.
Most yt-dlp debugging gets slow because people mix together three different problems: outdated extractor logic, broken environment setup, and auth or format issues. This pillar exists to separate those buckets quickly so the next step is obvious.
Fix common yt-dlp errors
Start with the general troubleshooting guide before guessing at random flags or stale forum fixes.
Fix "ffmpeg not found"
Use this when downloads start but merges, conversions, or audio extraction fail because ffmpeg is missing.
Update yt-dlp
A lot of breakages are just extractor drift. Update first before you waste time on deeper debugging.
Use cookies with yt-dlp
Go here when the failure is really auth, age verification, or a signed-in browser state problem.
Usually an update problem
- • the site changed and yt-dlp suddenly stopped working
- • extractor errors appeared out of nowhere
- • 403 or signature-related failures started recently
Usually a format problem
- • requested format is not available
- • old format IDs no longer exist
- • a command copied from months ago suddenly fails
Usually an environment or auth problem
- • ffmpeg is missing or not found on PATH
- • sign in to confirm your age
- • private, gated, or login-required content is blocked
Fast troubleshooting order
- 1. Update yt-dlp and confirm the version actually changed.
- 2. Decide whether the failure is auth, ffmpeg, format selection, or extractor drift.
- 3. Run the smallest command that reproduces the issue before stacking more flags.
- 4. Move to platform or workflow guides only after the base failure bucket is clear.
The failure pattern to avoid
The slowest way to debug yt-dlp is to keep pasting more flags into a broken command. That hides whether the real issue is stale yt-dlp, a bad format assumption, missing ffmpeg, or a site that now requires cookies.
Good troubleshooting strips the command down, updates first, and then tests one hypothesis at a time.
Later
Need a cleaner workflow after the fix?
Solve the issue first. If yt-dlp becomes part of a repeated process afterward, Importly is worth a look when you want the workflow to be more organized and less manual.
Next places to go
Install & Update
Return here if the problem is really setup, PATH, or ffmpeg visibility.
Commands & Usage
Go there once the broken command works again and you want cleaner patterns.
Authentication & Access
For sign-in, age verification, cookies, and private-content blockers.
Reference & Concepts
Use this when the issue is really about format IDs and selection logic.