SRT to VTT Converter Online — Free Subtitle Converter

CodexFuse Team · 2026-11-06T03:44:38.856Z · 11 min read min read

Convert SRT subtitles to WebVTT in seconds: what changes, a worked course example, and the checks to run before you publish.

SRT to VTT conversion is the small, annoying step that stands between a finished video and a video people can actually watch with subtitles. You have a perfectly good .srt file from your editor or transcription service, you drop it into an HTML5 video player or a browser-based course platform, and nothing shows up — because the web speaks WebVTT, not SRT. The fix takes about thirty seconds once you know the difference, and this guide walks through it with a real example.

What is the difference between SRT and VTT?

SRT (SubRip) and VTT (WebVTT) look almost identical at a glance, but they are built for different worlds. SRT is the older, simpler format: a sequence number, a time range, and one or two lines of text, repeated for every cue. It is the format most desktop editors, transcription tools, and subtitle download sites produce by default.

VTT is the web-native format. It adds a WEBVTT header at the top, uses a period instead of a comma in timestamps, and supports styling, positioning, and metadata that browsers understand. HTML5 video players read VTT natively through the <track> element, which is why every major browser, learning platform, and streaming service expects it.

The conversion itself is mechanical — header, timestamp punctuation, and a few formatting cleanups. It is exactly the kind of job a converter should do for you, because doing it by hand across a 400-cue file invites exactly the kind of silent error that leaves half your subtitles missing.

Why do SRT files fail in web players?

An SRT file fails in a web player for one of a handful of reasons, and the error is almost always silent: the player simply shows no captions. The most common cause is the missing WEBVTT header — browsers reject a track file that does not declare itself as WebVTT. The second is the comma in timestamps, which the WebVTT parser treats as invalid. The third is formatting that SRT tolerates but VTT does not, such as HTML tags inside cue text or sequence numbers that restart mid-file.

There is also a subtler failure: a file that converts cleanly but displays out of sync. That usually traces back to frame-rate assumptions in the original SRT, or to cues that overlap after a sloppy edit. A good converter preserves your timings exactly and flags nothing, so the check is on you — always preview the first and last minute of the converted file before you ship it.

How do you convert SRT to VTT online?

Converting SRT to VTT online takes three steps: provide your SRT file, run the conversion, and download the resulting .vtt file. You upload the file or paste its text, the converter rewrites the header and timestamps into WebVTT format, and you get a file you can attach to any HTML5 video player. No software to install, no command line, and no account on most tools.

The SRT to VTT converter on CodexFuse follows exactly that flow. Upload your .srt file or paste the subtitle text directly into the tool, hit convert, and preview the output in the browser before downloading. The preview matters: it is your chance to spot a broken cue or a timing that shifted before the file goes anywhere near your audience.

1. Upload or paste your SRT: drop the .srt file into the tool, or paste the full subtitle text if you copied it from an editor.
2. Convert: one click rewrites the file into WebVTT — header added, commas changed to periods, cue numbering normalised.
3. Preview the output: scan the first and last cues in the preview pane and confirm the timings match your video.
4. Download the .vtt file: save it next to your video file and attach it with a <track kind="subtitles"> element.

A worked example: converting subtitles for an online course

Consider a realistic scenario. Amira runs a small online training business in Lahore, selling recorded Excel courses. Her latest course has 14 lessons, each around 18 minutes, and her editor delivered one SRT file per lesson. Her course platform is browser-based and only accepts WebVTT tracks — the SRT files upload fine but display nothing, and three students have already emailed asking where the subtitles went.

Her old workflow was painful: open each SRT in a text editor, add the WEBVTT header by hand, find-and-replace every comma in every timestamp, save as .vtt, and hope nothing broke. Fourteen files, roughly 20 minutes each, and one lesson where a missed comma left the final five minutes captionless until a student reported it.

With the converter, her new workflow looks like this:

• Batch the uploads: she opens the SRT to VTT converter and processes one file at a time — upload, convert, preview, download — at roughly 40 seconds per file, including the preview check.
• Verify the edges: for each file she checks the first cue (00:00:01.200, "Welcome back to the course") and the last cue, confirming the timestamps survived the conversion intact.
• Name consistently: each output is saved as lesson-03-en.vtt beside lesson-03.mp4, so the platform picks the track up automatically.
• Test one lesson live: she uploads lesson 1 first, plays it in the browser, confirms captions appear, then uploads the remaining 13 in one batch.

Total time for all 14 lessons: under 15 minutes, including the live test. The old manual method would have taken most of an afternoon and still carried the risk of a silent error. The real saving is not the minutes — it is the confidence that every student sees captions on every lesson, first time.

What should you check after converting?

A converted file is not a verified file. Run through this short checklist before you publish, because subtitle errors are the kind your audience notices instantly and your player never reports.

• Header present: the first line of the file must read exactly WEBVTT, with a blank line after it.
• Timestamps use periods: every cue should read 00:00:05.000 --> 00:00:08.500, never with a comma.
• No overlapping cues: a cue's end time must be earlier than the next cue's start time, or players may drop one of them.
• Encoding is UTF-8: if your subtitles include Urdu, Arabic, or accented characters, a file saved in the wrong encoding will show as gibberish. Re-save as UTF-8 if anything looks wrong in the preview.
• Test in a real browser: open the video with the track attached in Chrome or Firefox and watch the first 60 seconds with captions on.

If a cue is missing after conversion, the usual culprit is a malformed block in the source SRT — a missing blank line between cues, or a timestamp with the wrong number of digits. Fix it in the SRT and convert again rather than patching the VTT by hand.

What are the honest limits of an SRT to VTT converter?

A converter changes format, nothing more. It will not fix bad timings, translate your subtitles, or repair a file where the transcription itself is wrong — if the SRT says the wrong words at the wrong time, the VTT will faithfully say the wrong words at the wrong time. It also will not re-time subtitles to a different frame rate or a re-edited cut of the video; that is an editor's job, not a converter's.

Styling is another limit. VTT supports colour and positioning cues, but a plain converter carries over only the text and timing — it does not invent styling from an SRT that never had any. If you need styled captions (speaker colours, top-of-frame placement), add those in a subtitle editor after converting.

Finally, watch the file size and the workflow around it. The CodexFuse converter is free and unlimited, and you will need a free CodexFuse account to use the tool — a small step, but worth knowing before you are mid-deadline. For a one-off conversion that is trivial; for a team converting hundreds of files, agree on the naming convention and the preview check first, or the speed of the tool just lets a mistake propagate faster.

Where else does VTT matter beyond video players?

WebVTT is not only for <video> tags. Learning management systems, accessibility checkers, and search engines all read it. A course platform that indexes your VTT track makes your lesson content searchable; a screen reader user benefits from captions that the browser renders natively; and some SEO tools treat a properly attached subtitle track as a signal that the page's video content is accessible and complete.

It also matters for repurposing. The same VTT file that captions your video can be stripped back to plain text for a transcript page, fed into a speech-to-text workflow for comparison, or converted again for a different platform. Keep one canonical subtitle file per video, in SRT as the master and VTT as the web derivative, and every downstream use stays consistent.

For creators who record their screen as well as their face, the same discipline applies to the recording itself — a clean browser screen recording with matching captions is what separates a professional course from a shaky screencast.

Frequently Asked Questions

Is the SRT to VTT converter free?

Yes. The CodexFuse SRT to VTT converter is free and unlimited — you can convert as many files as you need, with no per-file charge. You will need a free CodexFuse account to use the tool.

Will converting change my subtitle timings?

No. A proper conversion only changes the file format — the header and the timestamp punctuation. The start and end times of every cue stay exactly as they were in the SRT. If timings look wrong after conversion, the problem was in the source file, not the conversion.

Can I convert VTT back to SRT?

Yes, the reverse conversion is straightforward: remove the WEBVTT header and change the periods in timestamps back to commas. Some tools do this in one click. Keep your original SRT as the master copy anyway, so you rarely need to convert backwards.

Do browsers need a plugin to show VTT captions?

No. All modern browsers — Chrome, Firefox, Safari, and Edge — render WebVTT natively through the HTML5 <track> element. No plugin is needed; you only need to attach the .vtt file to the video and enable captions in the player controls.

Why do my subtitles show as question marks or boxes?

That is an encoding problem, not a conversion problem. Your file was probably saved in a legacy encoding instead of UTF-8. Re-save the source SRT as UTF-8 (most text editors offer this under Save As), convert again, and the characters should display correctly.

Can I style VTT captions with colours or fonts?

Yes, WebVTT supports styling through CSS-like cues, such as ::cue selectors for colour and background. A plain converter does not add styling — you add it afterwards in a subtitle editor or by editing the VTT directly. Keep styling subtle; captions exist to be read, not admired.

Stop hand-editing subtitle files

Every minute spent find-and-replacing commas in a subtitle file is a minute not spent recording, editing, or selling the video itself. Convert the file in seconds, preview the edges, attach the track, and move on — that is the whole job, and it should feel like it.

Then look at the rest of the workflow around your videos with the same eye. If the hosting, the email that delivers your course links, and the backups of your recordings all need the same kind of hand-holding, they are costing you the same kind of hidden afternoon. Move them to CodexFuse: one fully managed platform, on pay-as-you-go credits, where the infrastructure stops being your second job. Sign up free, move your hosting and business email over, and let the platform carry the parts that were never your work in the first place.