YouTube Subtitles

How to Download YouTube Subtitles with Timestamps

A practical guide to obtaining timestamped YouTube captions, choosing the right source, and validating the file before editing.

Downloading subtitles is easy only when the video exposes a caption track. The useful part is obtaining the right track, preserving its timing, and knowing what you are allowed to do with it. A transcript copied from the watch page is not always equivalent to a subtitle file: it may omit cue boundaries, speaker labels, formatting, and millisecond precision.

First, identify the source you actually have

Open the video’s caption menu and note whether the track is creator-uploaded, automatically generated, or translated. A creator-uploaded English track is usually the best editing source. Auto captions are valuable but commonly contain sentence fragments and rapid cue changes. An auto-translated track has already passed through one translation step, so translating it again compounds errors.

If you control the channel, use YouTube Studio’s subtitle download action. It preserves the track YouTube stores and avoids relying on third-party scraping. If you do not control the channel, use YouTube’s visible transcript where available and respect the creator’s rights and the platform’s terms. LumaTool’s YouTube Transcript Extractor can help with supported public inputs, but it cannot make a private or unavailable track appear.

What timestamped output should look like

A clean SRT file contains a sequence number, a start and end time, and text:

1
00:00:12,400 --> 00:00:15,180
Today we are testing three caption workflows.

2
00:00:15,300 --> 00:00:18,020
We will compare accuracy, timing, and export formats.

WebVTT uses a header and a dot before milliseconds:

WEBVTT

00:00:12.400 --> 00:00:15.180
Today we are testing three caption workflows.

A transcript such as 0:12 Today we are testing... is readable, but it is not yet an import-ready subtitle file. It has a start marker and no explicit end time. Do not invent the end time by adding a fixed number of seconds to every line; measure the next cue and the spoken phrase instead.

A reliable download and verification routine

  1. Select the original-language track, preferably the human-edited one.
  2. Download VTT or SRT when the interface offers a format choice. Keep the untouched source file.
  3. Open the file in a plain-text editor and confirm that timestamps are present throughout, not only at the beginning.
  4. Check the first cue, a cue near the middle, and the final cue against the video.
  5. Save text as UTF-8 and avoid word processors that may replace quotes or add formatting.
  6. If your next application requires another format, follow the SRT and VTT comparison before converting.

Three spot checks catch different failures. The first detects a leading offset, the middle exposes progressive drift, and the last reveals a truncated or misaligned export. For a two-hour video, checking only the opening ten seconds is not enough.

Common failure modes

No caption track appears. The creator may not have published captions, the video may be live, private, age-restricted, or still processing. See creating subtitles when YouTube has no captions for a transcription-first workflow.

The file contains duplicated rolling text. Auto-caption exports sometimes repeat words as the recognition window updates. Keep the original, then use the method in cleaning auto-generated captions.

Timing is consistently early or late. That is usually a constant offset and can be fixed without rewriting text. A delay that grows over time is progressive drift and needs a different correction; the subtitle timing guide explains both.

Characters look corrupted. Reopen the file as UTF-8 before changing any words. If don’t becomes don’t, the bytes were decoded with the wrong character set. Follow the SRT encoding repair checklist instead of manually replacing every visible artifact.

Preserve evidence before you edit

Keep the downloaded file, its source URL, track language, download date, and whether it was auto-generated. When a later editor asks why a phrase or timestamp changed, you can compare against the actual source rather than an already-cleaned copy. The same provenance is useful when translation, QA, and dubbing are handled by different people.

The full sequence—extract, clean, convert, translate, time, review, and prepare speech—is mapped in the complete YouTube subtitle workflow.