Skip to content

Platforms · Updated

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:

  • Wrong format for the extension. A file named .vtt that is actually SRT (comma decimals, no WEBVTT header) 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. The enhanced download alongside CaptionPass's YouTube preset wraps lines at 42 characters and flags anything faster than 17 CPS. 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

  1. Confirm SRT commas vs VTT dots match the file type you upload.
  2. UTF-8, no stray styling wrappers unless you intend them.
  3. No overlapping cues on dialogue-heavy sections.
  4. Spot-check three timestamps in Studio preview against the master.
  5. Run the file through CaptionPass with the YouTube preset and read the report.

Common questions

Why does YouTube accept my SRT but captions do not show on the video?
Studio can ingest a file while the player rejects individual cues: wrong decimal separator (comma in WebVTT), missing WEBVTT header on a .vtt upload, overlapping cues, or encoding the player cannot parse. Validate with a platform preset before publish.
What line length does YouTube expect for subtitles?
YouTube publishes no limit, but very long single-line cues wrap awkwardly on mobile and can fail QC in third-party review. The CaptionPass enhanced YouTube download wraps at 42 characters a line and 2 lines a cue.
Can I upload WebVTT to YouTube?
Yes. YouTube supports SRT and WebVTT. WebVTT must start with WEBVTT on line one and use dot decimals. A file renamed from .srt without fixing punctuation will drop cues silently.