Skip to main content
Tech Provider forFree foreverNo credit cardUnlimited DMsNo watermark
Guides

YouTube SRT Upload Not Working: Timing and UTF-8 Fixes

Check a rejected or out-of-sync YouTube SRT file: UTF-8 encoding, timestamp syntax, upload mode and the final video cut. Includes a small test example.

5 min read
Don't feel like reading?

Reviewed October 31, 2026. Includes original teaching examples and source-backed instructions. Third-party features and terms can change.

Quick answer

When YouTube will not accept an SRT file, check that it is plain UTF-8 text with valid numbered caption blocks and timestamps. Upload it as a file with timing. If it uploads but plays incorrectly, compare the subtitle timing with the exact video cut instead of repeatedly changing the extension.

The following checks separate three problems: an invalid file, the wrong upload workflow, and a valid file matched to the wrong edit. This is a documentation-based workflow with an original syntax example, not a guarantee that every upload error has the same cause.

Identify the failure before editing anything

Make a backup of the caption file and note the exact message in Studio. "Not working" could mean the file is rejected, the words never appear, the timing is wrong, or the visual style changed.

What you observeFirst checkAvoid doing this
The file is rejected immediatelyEncoding, real extension and cue structureRe-transcribing before inspecting the file
Upload succeeds but captions are absentCorrect video, language and saved trackAssuming the successful upload is the final review
Every cue is early or lateWhether the edit has an added or removed introMoving individual cues without checking the whole cut
Captions start correctly then driftCompare timing near the endApplying one offset without testing it
Font or color is missingDestination's supported subtitle stylingTreating styling loss as a text-transcription failure

These are diagnostic starting points, not a claim that one symptom uniquely identifies one bug.

Check the actual file, not its icon

Open a copy in a plain-text editor. You should be able to inspect cue numbers, timing lines and caption text. A Word document or rich-text file does not become a subtitle file when its name ends in .srt.

YouTube's supported subtitle formats specify basic SRT in plain UTF-8 and do not recognize SRT styling markup. Save from a text or subtitle editor using that encoding. Check that the final filename is not secretly ending in .srt.txt.

For a file that contains mixed-language names, inspect the saved text again after reopening it. If characters are already corrupted in the local copy, uploading it again cannot recover the missing spelling. Return to a good source copy and export correctly.

Compare a tiny, original SRT example

This sample illustrates structure only. Its text and times are invented for this guide; replace them with the words and timing of your own video.

1
00:00:01,000 --> 00:00:03,400
Open the subtitle track.

2
00:00:04,000 --> 00:00:06,600
Check the final video cut.

Look for a cue number, a start and end time, and text, with a blank line before the next cue. The sample uses hours, minutes, seconds and comma-separated milliseconds. Each end time comes after its start time.

Use a throwaway copy or private test upload when experimenting with sample cues. Do not replace a published accessibility track with unrelated sample text. If a small valid file works but the complete file fails, inspect the full file for a malformed cue rather than assuming the whole transcription must be discarded.

Choose the upload path that matches the file

In YouTube Studio, open Subtitles, select the video and choose the language. Add the subtitle track, choose Upload file, and select With timing for an already timed SRT. Review the result and save it. The sequence is documented in YouTube's caption upload instructions.

An untimed transcript is a different input. Do not choose a workflow based only on the fact that both files contain words. Before finishing, confirm that you are reviewing the intended language track on the intended video.

Test timing at three checkpoints

Use the first clear sentence, a middle sentence and the final spoken sentence as checkpoints. Write down the spoken time, displayed time and observed difference for each.

If all three differ by roughly the same amount, investigate an offset such as a new opening card. If the discrepancy grows, investigate a mismatch between the subtitle master and the video version. If it changes abruptly after one section, compare that edit point. These observations help narrow the cause; they are not a substitute for reviewing the full corrected track.

See subtitle offset versus timing drift before applying a global shift. Preserve the original subtitle master, and only approve a corrected copy after it has been checked against the final upload.

Finish with a viewer-side review

After saving, play the video with the intended caption track selected. Review proper names, quantities, punctuation and meaningful sounds, not just whether a CC control exists.

Record the video title or ID, language, subtitle filename and cut revision together. That small delivery record helps prevent a later editor from uploading an older SRT to a newer video. If the source export came from Premiere, the Premiere caption-export guide helps check the file before it reaches Studio.

YouTube subtitle upload QA sheet

Separate a rejected file from a timing or wrong-version problem.

Preview the complete template
YOUTUBE SUBTITLE QA

Video title / ID:
Final cut revision / duration:
Language:
Subtitle filename:
Source editor and export date:
Backup location:
Exact upload error, if any:

FILE CHECK
[ ] Opened as plain text, not a formatted document
[ ] Saved as UTF-8
[ ] Actual filename ends in .srt
[ ] Numbered cues with start and end times
[ ] Each end time is later than its start time
[ ] Blank line separates caption blocks
[ ] No accidental commentary or notes inside the file
[ ] Names and mixed-language characters survive reopening

UPLOAD CHECK
[ ] Correct video and language selected
[ ] Timed SRT uploaded using With timing
[ ] Track reviewed and saved
[ ] Viewer-side playback checked

TIMING LOG
Beginning sentence:
Spoken time / caption time / difference:

Middle sentence:
Spoken time / caption time / difference:

Final sentence:
Spoken time / caption time / difference:

Pattern: constant offset / growing drift / jump at edit / other
Proposed correction:
Corrected copy filename:
Full corrected track reviewed by:
Remaining uncertainties:

DELIVERY NOTE
This subtitle file matches cut revision:
It does not replace text already burned into the video.
Do not reuse it for a recut without checking every changed section.

Free plain-text file. Edit it in any notes app or document. You may adapt our original worksheet for personal and client work; linked third-party assets keep their own licences.

What to work on next

Frequently asked

Will uploading a new SRT change captions already burned into the video?
No. Text already rendered into the picture remains in the video. Review whether the additional selectable track creates duplicated visible captions for viewers.
Should translated subtitles use the same wording as the original transcript?
No. A translation should preserve meaning in the target language, while matching the relevant spoken intervals. Have a fluent reviewer check names, numbers and meaning before delivery.
Can I use one SRT for a Short and the full-length video?
Only if its cues match that specific video. A shortened or rearranged cut usually needs its own timed subtitle file; verify rather than relying on a shared project name.