Why a Video Transcript Fails — and What Each Error Actually Means
Private, login-gated, region-blocked, no audio track, platform changed. A plain-English guide to every reason a transcript fails, which ones are worth retrying, and which aren't.
Most transcription tools fail the same way: a red box that says "something went wrong, please try again." So you try again. It fails again. You've now spent five minutes and learned nothing.
The truth is that failures need different answers: some go away if you try again, some go away only when something changes — a password, a sharing setting, or you supplying the file yourself — and some can never work no matter how many times you click. Knowing which is which saves a lot of time.
Here's every category, what causes it, and what to actually do.
Failures Where Retrying Won't Help
"This video is private"
The video isn't publicly viewable. If a logged-out browser in an incognito window can't play it, the platform isn't showing it to the public, and no tool can transcribe it from the link.
What to do: if it's your own video, set it to public or unlisted temporarily. If it isn't, download it (if you have access) and upload the file directly — that path works regardless of privacy, because the file comes from you. A Google Drive file that isn't shared has one more way in: the failed page offers Choose it from Google Drive, which opens Google's own picker and lets SubGrab open that one file without changing its sharing.
"This video requires a login"
Distinct from private, and increasingly common. The video may be visible to you because you're signed in, but the platform refuses to serve it to anyone who isn't. Vimeo has been tightening this through 2026, and members-only YouTube content behaves the same way.
What to do: the file-upload route again. This is the single most reliable workaround for anything access-gated. If you can play the video but can't download it, the failed page offers Record it from a tab instead (signed in, on desktop Chrome or Edge): play the video in another tab, share that tab with its audio, and its sound is recorded as it plays — up to 60 minutes a recording — and transcribed like an upload. See recording a browser tab's audio and Vimeo transcripts and what's reachable.
"This video is password-protected"
On Vimeo, SubGrab asks for the password on the video's page before taking any credit, and uses it for that one job without storing it — see transcribing a password-protected Vimeo video. Other platforms can't take a password.
What to do: on Vimeo, enter the password. Elsewhere, ask for a link without one, or upload the file.
"This video doesn't have an audio track"
Occasionally literal — silent footage, a slideshow, a screen recording made with the microphone off. There is nothing to transcribe.
Worth saying plainly: this message is only trustworthy if the tool actually checked. A common bug in transcription pipelines is downloading a video-only rendition of a video that does have sound, then reporting "no audio" — the file genuinely had no audio, but a different rendition of the same video would have. SubGrab now verifies the downloaded media carries an audio stream and automatically tries alternative renditions before it ever reports this, so if you see it, the video really is silent.
What to do: confirm you can hear sound when you play it. If you can, report the link.
"This video is not available in your region"
The platform geo-blocks it. Servers have locations too.
"The video is too long"
A link can run up to 10 hours, and YouTube videos and Kick, SOOP and CHZZK streams up to 16 hours; anything longer is turned away before you're charged. Uploaded files go up to 10 hours as well (100 MB), because a recent browser such as Chrome or Edge compresses the audio before sending it. In a browser that can't compress audio, uploads stop at about 50 minutes.
What to do: within those limits, a link and an upload both work. For something longer, save the part you need and upload it. See transcribing full livestream VODs.
Failures Where Retrying Genuinely Helps
"Our video access service is temporarily degraded"
A network or infrastructure hiccup between the service and the platform. This is transient by definition.
What to do: usually nothing. SubGrab retries a temporary failure for you — 10 minutes, 40 minutes and then 2 hours after each failure, up to three tries — charges you only if one works, and emails you when the transcript is ready. You can also try again yourself, or stop the retries from the failed page.
"We couldn't read this video's page"
The platform changed something. Video platforms restructure their pages and APIs without notice, and extraction tooling has to catch up — usually within days.
What to do: try again later, and report the link. A reported link is what turns a silent breakage into a fix.
Rate limiting
Platforms throttle automated access. Under heavy load, a request that would normally succeed gets refused.
What to do: wait and retry — or let the automatic retries above do it. Almost always resolves itself.
What Should Happen to Your Credits
This matters more than the error message. A failed transcript should never cost you anything.
Every failure category above triggers an automatic refund — the credits go back to your balance immediately, and the movement is recorded in a ledger you can inspect in your dashboard. You should never be in a position of arguing about whether you were charged for something that didn't work.
If a video fails and your balance doesn't come back, that's a bug worth reporting, not something to absorb quietly.
The Single Best Workaround
If you take one thing from this: when a URL won't work, upload the file.
URL-based transcription depends on being able to reach the video anonymously, and that's the part platforms keep restricting. Uploading sidesteps all of it — privacy settings, login walls, passwords, region blocks, and extractor breakage — because you're supplying the media directly. Your browser extracts just the audio first, so a 500 MB video becomes a few megabytes in transit and the video itself never leaves your machine.
In a recent Chrome or Edge that works for recordings up to 10 hours, because the browser compresses the audio before sending it; in a browser that can't compress audio, the ceiling is about 50 minutes. Within that, it's the most reliable path there is.