When an SRT Subtitle File Won't Load: A Checklist That Finds the Cause

What not working can mean

The symptom narrows the cause, so note exactly what happens:

• The player shows no subtitles at all and offers no subtitle track.
• A platform rejects the upload with an invalid format or unsupported file message.
• Subtitles appear for a while, then stop partway through.
• Two cues appear merged, or a cue number or timestamp shows on screen as text.
• Subtitles appear but are out of time; that is a timing problem covered in subtitle timestamp alignment, not a loading one.
• Accented letters or whole scripts look garbled; that is an encoding or font issue, covered in subtitles showing strange characters.

The layout every SRT reader expects

SRT is plain text with a deliberately simple structure, repeated for each cue:

First line

The cue number, counting up from 1

Second line

Start and end time, such as 00:01:05,200 --> 00:01:08,900, with a comma before the milliseconds

Following lines

The subtitle text, one or more lines

Separator

One empty line before the next cue number

Players differ in how forgiving they are. Desktop players often skip a broken cue and carry on, while upload validators on platforms may reject the whole file for one error. The guide to SRT vs VTT explains where the two formats differ.

Common causes, most likely first

1. The file name does not match the video. Desktop players load subtitles automatically only when the SRT sits in the same folder and shares the video's name, such as lesson-03.mp4 with lesson-03.srt. Many also accept a language code, as in lesson-03.en.srt.
2. The real extension is not .srt. Windows hides known extensions by default, so a file that looks like lesson-03.srt can actually be lesson-03.srt.txt.
3. It was saved by a word processor. Word, Pages or TextEdit in rich text mode can save formatting codes, or a different file type, under a name ending in .srt.
4. The content is WebVTT. A file that starts with the word WEBVTT and uses periods before the milliseconds is a VTT file, even if someone renamed it.
5. A timestamp is malformed. Typical slips are a period instead of the comma, a missing hour field, a mistyped arrow, or an end time earlier than the start time.
6. Blank lines are wrong. A missing empty line merges two cues; an empty line inside a cue's text ends the cue early and leaves the rest looking like a broken cue.
7. Platform rules. Some services also check the language you select, the file size, or cue numbering and overlaps more strictly than players do.

Check the file in this order

1. Turn on visible file extensions (in Windows File Explorer, View then File name extensions; on a Mac, Finder settings, Advanced) and confirm the name really ends in .srt.
2. Open the file in a plain text editor such as Notepad, TextEdit in plain text mode or VS Code. If you see formatting codes or unreadable symbols, it was saved in the wrong format.
3. Read the first three cues against the layout above, then jump to the place where subtitles stop showing and read the cues around it.
4. Load it manually in VLC with the video playing, through Subtitle then Add Subtitle File. If VLC shows it, the file is structurally usable and the problem is naming or the destination.
5. Open it in a subtitle editor such as Subtitle Edit or Aegisub, which list malformed timestamps, overlaps and empty cues.
6. Re-read the destination's subtitle requirements, including any language or size rules, and upload again.

Fixes for each cause

Name and location. Rename the subtitle file to match the video exactly and keep both in the same folder. For a phone or TV that reads subtitles from a USB stick, the same rule usually applies.

Hidden extension or wrong file type. Rename lesson-03.srt.txt to lesson-03.srt. If a word processor touched the file, copy the text into a plain text editor and save it fresh as plain text with the .srt extension.

VTT content. Convert rather than rename. Subtitle editors convert in one step, and ffmpeg can do it from a terminal:

ffmpeg -i captions.vtt captions.srt

Malformed timestamps and blank lines. Fix them by hand for a few cues, or run the subtitle editor's automatic error fixing for many, then review what it changed. Renumbering cues sequentially is a standard option in those tools.

Players that will not load external files. Some devices only show subtitles embedded in the video. Muxing the SRT into an MKV file adds it as a selectable track without re-encoding anything:

ffmpeg -i talk.mp4 -i talk.srt -map 0 -map 1 -c copy talk.mkv

A worked example: a course upload that keeps failing

The lesson generalizes: check the boring things, the name and the extension, before the clever ones.

Pitfalls and limits of fixing SRT by hand

• SRT has no formal styling standard. Some players honor simple italic or bold tags, others show them as text or strip them.
• There is no positioning in plain SRT, so a subtitle cannot be moved away from on-screen text without switching to VTT or another format.
• Hand editing a long file invites new errors, such as deleting a blank line or a comma; validate after every editing session.
• A file that works in VLC can still fail a strict platform validator, so test where it will actually be used.
• Fixing structure does not fix wording. Proofread the text separately.

What mydubly's subtitle files contain

mydubly generates SRT and VTT files from a video or audio file's speech; it creates subtitles rather than repairing files you already have, and it cannot import an existing SRT or VTT. Each job produces one subtitle track, in the spoken language or one chosen target language. Each cue is one recognized speech segment written as a single line, cues are numbered in order, and the SRT and VTT files carry the same cues and times. mydubly does not add manual line breaks and does not burn subtitles into the picture.

Before using a downloaded file with a desktop player, rename it to match your video as described above. If a platform wants shorter lines or two-line cues, reflow them in a subtitle editor; editing SRT files step by step is covered in how to edit an SRT file.

When a different tool is the right call

• Viewers on a platform that cannot show subtitle files need subtitles burned into the picture, which a video editor does; open vs closed captions explains the trade-off.
• A file that needs styling, positioning or strict reading-speed limits belongs in a dedicated subtitle editor.
• An existing SRT that needs translating cannot be uploaded to mydubly; generate translated subtitles from the original video instead.

Next step: generate a clean file from the source

If a damaged SRT would take longer to repair than to recreate, run the original video through the subtitle generator and get fresh SRT and VTT files. Transcripts and subtitles cost 1 credit per minute with a 5-credit minimum, so a 20-minute lesson costs 20 credits, which is 2¢. Audio-only recordings go through video to text and audio tools the same way.