Choose WebVTT for HTML5 web video workflows or SRT for broad subtitle and editing compatibility, then review the timing and text after conversion. The formats look similar, but their headers, timestamp punctuation and supported styling differ.
Convert a subtitle file
Choose SRT or WebVTT and download a converted text-based subtitle file.
SRT and WebVTT differences
SRT is a simple and widely accepted subtitle format built from numbered cues, start and end timestamps and text. WebVTT is designed for web video and begins with a WEBVTT header. It can also support web-specific cue settings and styling.
A typical SRT timestamp looks like 00:00:05,250, while WebVTT uses 00:00:05.250. Conversion changes the required syntax while keeping the intended time positions.
Advanced styling or unusual cue metadata may not translate perfectly between formats. For important projects, compare the source and output in a subtitle editor or video player.
How to convert subtitles with Mediaivo
- Identify the destination
Use WebVTT for a web player that requests .vtt or SRT for software and platforms that request .srt.
- Choose the source subtitle file
Start from a valid UTF-8 text file with correctly ordered timestamps.
- Select the output format
Choose the format opposite the source and process the file.
- Test with the matching video
Check the first cue, scene changes, overlapping dialogue and the final cue.
Which subtitle format should you use?
Follow the requirement of the player, platform or editor receiving the file.
| Situation | Recommended choice | Check before publishing |
|---|---|---|
| HTML5 website video | WebVTT (.vtt) | Confirm the player loads the file and displays special characters. |
| General editing or upload workflow | SRT (.srt) | Check whether the destination requires a language code or naming convention. |
| Advanced styled captions | Use the format required by the target system | Inspect styling because basic conversion may not preserve every feature. |
How to verify converted subtitles
Open the subtitle file in a plain-text editor and confirm that its first line and timestamp punctuation match the chosen format. Then load it with the video and watch representative sections.
Pay attention to names, accented letters and non-Latin scripts. Character-encoding problems can turn readable text into question marks or broken symbols even when cue timing remains correct.
Common mistakes to avoid
1. Renaming the extension only
Changing .srt to .vtt does not add the required header or convert timestamp syntax.
2. Testing without the video
A structurally valid file can still be early, late or attached to the wrong version of the video.
3. Ignoring special characters
Encoding problems may affect names, accents and multilingual captions.
4. Assuming all styling will transfer
SRT and WebVTT support different levels of cue settings and presentation.
Final check before downloading or publishing
- The output has the correct extension.
- Timestamp punctuation matches the format.
- Cue order and text are complete.
- Special characters display correctly.
- Captions stay synchronized with the final video.
Frequently asked questions
Can I rename SRT to VTT?
No. WebVTT requires different timestamp punctuation and a WEBVTT header, so the file content must be converted.
Which format is best for a website?
WebVTT is designed for HTML5 video and is normally the appropriate choice when a web player requests captions.
Why are subtitles out of sync after conversion?
The subtitle file may match a different edit or frame timing of the video. Conversion preserves times but cannot know if the source timing was correct.
Will styling be preserved?
Basic text and timing transfer well, but advanced styling or cue settings may need manual review.
Prepare subtitles for the player that needs them
Convert the syntax, then test cue timing and characters with the final video.