Why won’t my subtitles work on YouTube? Common fixes
A subtitle file that plays fine on your computer can still fail on YouTube. Almost always it is one of three things — the format, the encoding, or the timing.
You export a subtitle file, it looks perfect in VLC, you upload it to YouTube — and it is rejected, or it uploads but shows nothing, or every accented letter has turned into garbage. The frustrating part is that the file is not obviously broken. YouTube is simply stricter than a desktop player, and it fails quietly. Once you know the three things it cares about, the fix is quick.
This guide walks through each cause in the order worth checking, with a troubleshooting table you can scan when you are in a hurry.
Which subtitle formats does YouTube accept?
YouTube supports a specific set of caption formats, and the styled ones are not on it. The most common upload failure is trying to feed it an ASS file — the anime and karaoke format full of fonts and positioning. YouTube has no interest in that styling and simply refuses the file.
- Accepted and reliable: SRT (SubRip) and SBV (YouTube’s own older format).
- Rejected: ASS / SSA — the styled formats. Convert them to SRT first.
- Works but unnecessary: several broadcast formats upload, but SRT is the path of least resistance.
If your file is an ASS, run it through ASS to SRT — the styling is dropped, which is exactly what YouTube wants, and you are left with a clean SRT it accepts. For anything else exotic, the general subtitle converter will get you to SRT, and an old SBV export can go to SRT too if you would rather standardise on one format.
Convert ASS to a YouTube-ready SRTWhy are my accented characters garbled?
If the timing works but names like “Björk” or “Málaga” come out as “Björk” or “Málaga”, the problem is the file’s text encoding. YouTube expects UTF-8. Many editors on Windows still save subtitles in a legacy code page like Windows-1252, and every non-English character is then misread.
The fix is to re-save the file as UTF-8 — specifically UTF-8 without a byte-order mark, because a leading BOM can confuse the parser on the very first cue. This is not a change to the words, only to how the bytes are stored, so nothing about the content is altered.
The fix subtitle encoding tool re-encodes a file to clean UTF-8 in your browser, so the accented characters come through correctly on upload. It never sends the file anywhere — the conversion happens on your own device.
Re-encode subtitles to UTF-8Why does YouTube reject my timing?
The third cause is bad cue timing, and it is the sneakiest because the file opens fine locally. YouTube validates the timeline and rejects files with structural timing errors. Two problems account for most of them.
- Overlapping cues — one caption is still on screen when the next is set to begin. YouTube cannot decide which to show and rejects the pair.
- Zero-duration cues — a cue whose start time equals its end time, so it is meant to display for no time at all. Often the result of a rounding bug in whatever exported it.
Both are easy to miss by eye in a long file. The subtitle timing checker scans the whole file and flags every overlap and zero-length cue so you can correct them before uploading. Fixing the flagged cues — trimming an overlap, giving an empty cue a real duration — is usually all it takes.
While you are in there, it is worth checking a third timing issue that will not get the file rejected but does hurt viewers: cues that flash on for a fraction of a second. A caption needs roughly a second on screen at minimum for a reader to catch it, and a good rule of thumb is to keep reading speed under about twenty characters per second. YouTube will accept a caption that appears for 200 milliseconds, but nobody watching can actually read it.
| Symptom | Cause | Fix |
|---|---|---|
| Upload rejected outright | Styled format (ASS/SSA) | Convert to SRT |
| Accented letters look garbled | Not UTF-8 encoded | Re-encode as UTF-8 (no BOM) |
| File rejected as invalid | Overlapping or zero-length cues | Run a timing check and fix them |
| Uploads but no captions show | Wrong track language or not published | Set language, publish the track |
| Only some lines appear | Mixed encoding or stray blank lines | Re-save clean UTF-8 SRT |
What is the reliable upload recipe?
Put the three fixes together and you have a file that uploads first time, every time.
- Convert to SRT if the file is anything else — especially if it is ASS.
- Re-save it as UTF-8 without a byte-order mark so accented characters survive.
- Run a timing check and remove any overlapping or zero-duration cues.
- Upload it in YouTube Studio, set the correct caption language, and publish the track.
If a file came off YouTube in the first place as VTT or SBV and you want to standardise, VTT to SRT will convert it back to the format everything expects. And if you are also adding these captions to a video for another platform, our guide to add subtitles to a video covers burning them in.
Frequently asked questions
Does YouTube accept ASS subtitle files?
No. ASS is a styled format and YouTube ignores that styling, so it rejects the file. Convert it to SRT first — the words and timing are all YouTube needs.
Why do my subtitles show strange symbols instead of accents?
The file is not saved as UTF-8. A legacy encoding like Windows-1252 misrepresents accented and non-Latin characters. Re-encode the file to UTF-8 without a BOM and the symbols will display correctly.
My file uploads but no captions appear. Why?
Usually the track was uploaded but not published, or the caption language was not set. Check both in YouTube Studio. If it still fails, an overlapping or zero-duration cue may have invalidated the timeline.
What is the safest format to upload to YouTube?
A plain SRT saved as UTF-8 with clean, non-overlapping timing. It is the most widely tested path and sidesteps the styling and encoding problems that cause most rejections.
Can I upload subtitles to a video that already has auto-captions?
Yes. Uploading your own SRT adds a track alongside the automatic one, and you can choose which is published. Your accurate, punctuated file is almost always the better one to show, so publish it and leave the auto-captions unpublished.
My SRT works in VLC but YouTube still rejects it. Why?
VLC is forgiving and will play a file with mixed encoding or minor overlaps that YouTube refuses. Re-save it as clean UTF-8 without a BOM and run a timing check — one of those two is almost certainly the difference.
Does the subtitle filename need to match the video?
Not on YouTube — you upload the caption file directly in Studio and pick its language there, so the name does not matter. Matching filenames only matter for local players like VLC that pair a subtitle to a video by name.