SRT vs VTT: convert plain subtitles and check the result

A subtitle conversion should leave you with a file you can inspect and use. It should also tell you when the input contains information the target workflow cannot preserve. This guide uses a small, invented example that you can reproduce in Topicut's free tools; it is not an audio-alignment demonstration.

1. Choose the delivery you actually need

SRT is a numbered text-cue format. WebVTT is used with web text tracks and has a WEBVTT header and full-stop milliseconds. The full formats differ in more than their file extensions. Check the intended player or upload destination's current requirements. For example, YouTube documents basic plain UTF-8 SRT and does not recognize its styling markup.

2. Try a small, known example

Open the SRT/VTT converter and select Use example, or paste:

1
00:00:01,000 --> 00:00:03,500
Keep the original source.

2
00:00:04,000 --> 00:00:07,000
Review every subtitle
before you publish.

Choose WebVTT and convert. In the preview, the first boundary becomes 00:00:01.000, not a newly calculated time. The second cue must still contain two lines. Download the VTT, open that local file in the same tool, choose SRT, and convert back. Check the original comma-based boundaries and both lines again. The tool normalizes numbering and newline style; it does not promise byte-for-byte file identity.

3. Stop rather than silently drop a feature

Topicut accepts a deliberately limited plain-text subset. A position setting, style or region block, markup, header metadata or non-numeric cue ID produces an explicit error. Keep your original and use a workflow that supports those features if they are needed. Do not delete meaningful formatting just to make an error disappear.

4. Validate with the media

A format conversion cannot hear a recording. Test the downloaded file in its intended player, with the correct video revision. Check a caption near the start, one in the middle and one near the end. Confirm the track can be selected if the delivery calls for closed captions.

Use the reading-speed checker to locate cue-level findings. If every caption has the same delay, use the time-shift guide. If only the wording is wrong, correct the words; changing the file extension will not fix them.

Keep the result available

These tools process your input in your browser, with no sign-up required for preview or download. Their current limits are 1 MiB UTF-8 text, 5,000 cues and 24-hour timestamps. Preserve the original file and identify your corrected copy. Registration is optional if you later want to organize a project brief and script.

Sources and review date

• Library of Congress: SubRip format
• W3C: WebVTT
• WHATWG: HTML text tracks
• YouTube: supported caption files

Format and product references checked October 28, 2026. Guide updated 2026-10-29.