YouTube Downloader Not Working? Fixes for Editors

What should you try first for any download error?

Restart B-ROLL first, because B-ROLL updates yt-dlp to the latest nightly build at every launch. Then work through these checks in order and stop when the download goes through:

1. Restart B-ROLL, or click Force update yt-dlp in the Advanced panel.
2. Click ↻ retry on the failed card for a fresh attempt.
3. In About (the ⓘ button), click Check for updates.
4. If the card says “Sign-in required”, add a cookies.txt from your own signed-in YouTube account. B-ROLL tries your browser’s YouTube login first, then opens its Sign-in needed wizard.

When YouTube started answering “Sign in to confirm you’re not a bot” on Ema Zamboni’s downloads, a fresh cookies.txt from a signed-in browser fixed it. Cookies expire, so the message can return: export again.

Which error are you seeing?

Each YouTube download error in B-ROLL maps to one likely cause and one first fix. Find the card message or editor symptom, then open its page.

Symptom	Likely cause	First fix	Page
“Sign in to confirm you’re not a bot”	YouTube verifies requests	Restart, then add a cookies.txt	Sign in to confirm you’re not a bot, fixed
“Sign-in rejected: refresh your cookies.txt”	Expired cookies	Export a fresh file	Export, use and refresh a YouTube cookies.txt
“YouTube blocked this (HTTP 403)”	YouTube refused a request	Restart, then retry	HTTP Error 403 Forbidden on downloads
Download crawls, or a ProRes file takes long	YouTube limiting, or the conversion running	Restart; conversion shows its own progress	Slow or throttled YouTube downloads
File is only 360p or 720p	Only the combined stream arrived	Check Quality, restart	Getting 1080p and 4K instead of 360p
Progress frozen at start or end	Preparing, merging or converting	Wait, then restart and retry	Downloads stuck at the start or the end
Some playlist videos fail	Private, deleted, age-restricted or blocked videos	Retry failed cards one by one	Playlist downloads that skip or stop
Subtitles missing	No track in that language	Check the language picker	Subtitles that do not download
Clip starts early or minutes off	Keyframe cut, or a plain number read as minutes	Tick Exact frame cut, check the times	Clips that start at the wrong time
“Preview needs VLC installed.”	VLC is missing	Install 64-bit VLC	Preview player not loading
“Windows protected your PC”	B-ROLL is not code-signed	Compare the SHA-256 checksum	SmartScreen, signing and checksums
Clip stutters in DaVinci Resolve	AV1 or VP9 video	Edit a DNxHR or ProRes copy	Choppy AV1 and VP9 playback in Resolve

Why do YouTube downloaders stop working from time to time?

YouTube downloaders stop working when YouTube changes how it serves video, and they recover once yt-dlp adapts in an update.

As of September 2026, the yt-dlp PO Token Guide describes one such change: YouTube expects a proof-of-origin token from some clients, and requests without one may be refused with HTTP Error 403. The same guide says those tokens have a limited lifespan, so a download left waiting for hours can need a fresh retry.

Why does a file fail or stutter in your NLE?

A YouTube file that stutters, goes offline or gets rejected in your NLE usually holds AV1 or VP9 video, long-GOP codecs that are heavy to decode. MP4, MKV and WEBM downloads keep YouTube’s own codecs, often AV1 or VP9 video with Opus audio.

On Ema Zamboni’s timeline in DaVinci Resolve Studio on Windows 11, 4K60 AV1 downloads were heavy to play back, and AV1 or VP9 files crashed Resolve at times. B-ROLL’s ProRes and DNx formats were built for that: after the download, ffmpeg converts the file automatically into an intraframe .mov for editing.

The same codec is behind the Premiere Pro VP09 unsupported compression error and many cases of Media Offline on a YouTube clip in Resolve. The codecs themselves are explained in codecs and formats for editing YouTube footage.

How does B-ROLL keep yt-dlp current?

B-ROLL runs yt-dlp --update-to nightly at every launch, so a restart always brings the newest yt-dlp build.

Only yt-dlp updates itself. ffmpeg and Deno stay as installed until you click Reinstall tools in the Advanced panel, which downloads both again. The same button fixes “JS runtime: missing”, which appears when B-ROLL found an ffmpeg on the Windows PATH at first launch and skipped Deno. B-ROLL checks GitHub for a newer app release 4 seconds after launch.

Once the download works again, the guides from YouTube download to timeline cover the rest of the job.