Last updated May 1, 2026 (UTC)
YouTube rejected my SRT — what actually went wrong
YouTube Studio sometimes blocks a subtitle upload with a generic “invalid file” message. The file might still look fine in a text editor. These are the failures we see most often on freelance delivery — and how to catch them before you send the link to a client.
Common Studio rejection causes
- Wrong decimal separator. SRT requires a comma in timestamps (
00:01:02,500). A dot makes the cue invalid. - Broken cue index. SRT expects sequential numbers starting at 1. Gaps or duplicates after a merge confuse parsers.
- Encoding. UTF-16 exports, stray BOMs, or Windows-1252 characters from an old template produce mojibake or empty cues.
- Empty or zero-duration cues. Exports from auto-transcription sometimes include blank blocks Studio refuses.
- HTML or styling tags. Tags copied from another platform may not survive YouTube's ingest.
Run your file through CaptionPass — free caption converter with a full QA report.
Convert & fix free →Studio accepted the file but playback is wrong
That is a different failure mode — overlap, reading speed, or drift. See YouTube caption upload issues and why captions are not showing.
Validate before you upload again
Run the file through CaptionPass with the YouTube preset: you get a repaired SRT plus a report listing every normalization and fix by cue index — useful when a producer asks what changed.
Convert your captions free
Upload on CaptionPass, pick a delivery preset, and download upload-ready output with optional enhanced formatting — free tier, no account required.
Convert & fix free →More guides
- Free online caption converter — SRT, VTT, and delivery QAHow CaptionPass works as a free caption converter with upload-ready and enhanced exports, platform presets, and explainable fixes.
- SRT to VTT converter guide — headers, timestamps, and pitfallsWhen to convert SRT to WebVTT, what breaks if you rename extensions, and how to validate before HTML5 or YouTube delivery.
- SRT vs VTT — when each format silently failsComma vs dot timestamps, WEBVTT headers, and where YouTube, TikTok, and HTML5 bite.
- Caption file encoding — UTF-8, BOM, and garbled textWhy uploads show mojibake or blank cues: UTF-8 vs legacy encodings and quick fixes.
- Burned-in vs soft subtitles — what to deliver whenOpen captions burned into the picture vs separate SRT/VTT tracks — tradeoffs for editors and clients.
- Reading speed for captions — CPS, line length, and platformsCharacters per second, lines per cue, and where YouTube, TikTok, and HTML5 push back.
- YouTube caption upload issues — silent rejection and timingWhen Studio accepts a file but captions vanish: format, line length, drift, and how to validate before publish.
- Caption timing drift after export from Premiere or DaVinciWhy captions slip after NLE export: frame rates, timecode starts, and how to normalize before YouTube or client delivery.
- CaptionPass vs generic subtitle convertersFormat swap tools vs delivery QA: explainable fixes, platform presets, and when each approach fits your workflow.
- CaptionPass vs Subtitle EditDesktop authoring vs delivery QA: when to use Subtitle Edit for editing and CaptionPass for platform-safe validation and API automation.
- Caption QA API for CI/CD pipelinesAutomate SRT and VTT validation in GitHub Actions or your build pipeline with POST /api/v1/process and Bearer API keys.
- TikTok subtitle format — short lines, CPS, and clean SRTVertical video reading speed, styling stripped on upload, and export settings that survive TikTok delivery.
- Why your captions are not showing — a triage guideHTML5, YouTube, and TikTok checks when subtitles vanish after upload.
- Fix overlapping subtitlesWhat overlap means and why some players drop overlapping cues.
- TTML and DFXP — broadcast-style timed text on the webNamespaces, timing, styling stripped in practice, and when TTML is the right interchange vs SRT or WebVTT.
- CaptionPass JSON IR and the developer-json presetLossless-ish cue interchange for tooling: when to use JSON IR, version tag, and how it pairs with the HTTP API.
- Timecode, frame rate, and caption syncWhy captions drift or jump: drop-frame vs non-drop, fractional frame rates, and export settings that survive upload.
- WCAG-minded captions — reading speed, sound tags, and burned-in contrastHow WCAG 1.2.x thinking maps to real files: CPS, line length, SDH-style cues, and contrast for open captions.
- Educators & classrooms — CaptionPass for instructionPartner program for instructors: API keys, workspace pilots, Learn guides, and classroom-appropriate access.
Fix in CaptionPass
Free caption converter · Homepage tool · HTTP API (v1) · Pro workspace