Last updated May 24, 2026 (UTC)
YouTube caption upload issues
YouTube Studio often reports success while playback shows missing, drifting, or garbled captions. This guide walks through the failures editors see after upload — and what to fix before you send a file to a client or channel manager.
Studio says uploaded — player shows nothing
The most common causes are structural, not “YouTube is broken.” Check in order:
Run your file through CaptionPass — free caption converter with a full QA report.
Convert & fix free →- Wrong format for the extension. A file named
.vttthat is actually SRT (comma decimals, noWEBVTTheader) will ingest inconsistently. See SRT vs VTT. - Encoding. UTF-8 without a BOM is the safe default. Mojibake in Studio preview usually means the export was not UTF-8. See caption file encoding.
- Overlapping cues. Overlaps can make cues flicker or disappear in the player. Trim earlier end times or run an overlap repair pass. See fix overlapping subtitles.
Timing drift after upload
If captions are consistently early or late across the whole video, the export frame rate or timecode mode may not match the mezzanine YouTube received. Re-export from the NLE with the same frame rate as the published video, or adjust offset in your editor before upload. For background on drop-frame vs non-drop, see timecode and frame rate.
Line length and reading speed
YouTube does not publish a hard CPS cap like broadcast, but long single-line cues are hard to read on phones and fail client QC. Split lines and watch characters-per-second on dense dialogue. CaptionPass's YouTube preset flags aggressive CPS and wraps lines toward common delivery norms. More detail: reading speed for captions.
Official reference
For YouTube's own steps on adding subtitles, use YouTube Help — Add your own subtitles & closed captions. When Studio and the player disagree, trust a structured validation report on the file itself before re-uploading.
Pre-publish checklist
- Confirm SRT commas vs VTT dots match the file type you upload.
- UTF-8, no stray styling wrappers unless you intend them.
- No overlapping cues on dialogue-heavy sections.
- Spot-check three timestamps in Studio preview against the master.
- Run the file through CaptionPass with the YouTube preset and read the report.
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 rejected my SRT — invalid file and Studio errorsWhen YouTube Studio blocks an SRT upload: encoding, index gaps, bad timestamps, and how to validate before you retry.
- 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