top of page

SRT Subtitles Not Working? Check Encoding, Timing and the Track

Oct 22
4 min read

Updated: Nov 13

When an SRT subtitle file fails, separate an import error from a display or timing problem. Verify that the file is plain text in a format the destination supports, inspect the cue timestamps and load it against the exact final video. Renaming a text file, converting its extension or turning captions on cannot fix every kind of failure.


Identify the failure category


If the platform rejects the file, start with format, encoding and cue structure. If it imports but no text appears, check the selected language track, caption visibility and whether cue times fall inside the video. If it appears at the wrong time, check the edit version and time offsets.


If text is already burned into the video picture, it will remain visible when a separate subtitle track is disabled. That is a different delivery from an SRT file. Avoid fixing a duplicated caption display by deleting the only editable text source.


Save an untouched copy before editing. Record the video filename, duration and caption filename together. “final.srt” may have been timed to an earlier cut even when the spoken words look identical.


Inspect a small cue in plain text


A basic SubRip cue has a sequence number, a start and end time separated by an arrow, caption text, and separation before the next cue. Use a plain text editor or subtitle editor; a word processor's document format is not the same as an SRT text file.


For an original example, cue 1 could use the timing line “00:00:01,200 --> 00:00:03,800” and the text “Choose the blue folder.” Its display duration is 3.800 − 1.200 = 2.600 seconds. Confirm that this is enough time for the actual audience and that the instruction matches the picture.


Keep start times before end times and check cue ordering. A timestamp later than the video's end will not help a player show the caption. For ordinary single-speaker narration, inspect accidental overlaps instead of assuming every importer will interpret them the same way.


Check the destination's encoding rules


YouTube's current documentation supports basic SRT in plain UTF-8 and does not recognize styling markup in that basic format. Save or export a UTF-8 copy and check accented letters, apostrophes and non-Latin characters after import. A successful upload does not prove every character survived correctly.


Make filename extensions visible in your operating system. A file called “captions.srt.txt” can look misleading when extensions are hidden. Changing an extension is useful only when the underlying content already has the right format; it does not transform a spreadsheet or document into valid timed captions.


Do not copy platform-specific filename rules from another service. Confirm the receiving platform's current format and language requirements, and use its documented importer. Different caption formats use different conventions; a VTT file is not converted to SRT simply by changing its suffix.


How to fix an SRT file that will not load

Open a copy in a plain-text editor and confirm that each cue has a number, a timestamp line such as 00:00:01,000 --> 00:00:03,000, subtitle text, and a blank line. Save as UTF-8 and test a two-cue file in the player before repairing the full set.

Test with two short cues before editing the full file

Make a copy containing one early cue and one later cue. Check that the player displays both in order and at the expected times. If one is missing, inspect cue numbering, timestamps and blank lines before changing the entire file.

Diagnose timing separately


A constant delay across the whole video suggests an offset or added opening material. A growing mismatch suggests a different edit, a duration change or another timing issue. Compare a cue near the start, middle and end before shifting every timestamp by the same amount.


For a hypothetical edit, removing a two-second opening card moves later dialogue earlier. Captions made for the previous version may need corresponding timing changes. If cuts occur throughout the video, one global shift will not restore every cue; retime against the approved final cut.


Review names, numbers and meaningful non-speech sounds. Automatically created text is a starting point for checking, not evidence of an accurate transcript. Keep language translation review separate from the technical fact that a file imports.


Test the actual viewing experience


Enable the intended track, play several sections and inspect the destination's processed video on a phone and a larger screen. Check line breaks, missing characters, late final cues and duplicate burned-in text. Save the corrected caption file beside the video version it matches.


AI LEMNISCATA's current video workspace does not promise SRT creation or import. Prepare the video there if appropriate, review the displayed total, then create and validate its caption delivery in a suitable separate workflow. Our caption-planning guide covers the broader content choices.


Common questions


Does a script document count as an SRT?


No. A script without timed cues is a transcript or production source. It needs timing and the correct file structure for a timed subtitle import.


Why are my colors and fonts ignored?


The destination may not support that styling in basic SRT. Use its documented caption controls or a supported format rather than assuming desktop styling will carry over.


Should I burn captions into every copy?


That depends on the delivery. Burned text is always part of the picture and is harder to revise; a supported separate track can be selected or disabled by viewers.


Related guides





Sources and scope

Sources checked 22 October 2026. The diagnostic workflow and hypothetical examples are independently written; no paid generation or claimed repair test was performed for this guide.


YouTube: supported subtitle files and basic SRT


VideoLAN: subtitle encoding troubleshooting


Create on AI LEMNISCATA

Use the current workspace to prepare your next video brief. Check the available choices and displayed total before ordering. Any external editing or technical delivery checks described above remain separate.



bottom of page