How to Convert Subtitles to SRT Online (TXT, VTT, ASS, SBV)

Editors, players, and platforms disagree on subtitle formats - SRT remains the lingua franca. Subtitle to SRT converts TXT, WebVTT, ASS/SSA, YouTube SBV, or normalizes existing SRT files to standard SubRip syntax in your browser.

Supported input formats

Output is standard SRT for broad compatibility.

Step-by-step: convert to SRT

1. Open Subtitle to SRT and select your subtitle file from your computer.
2. Confirm detected format and entry count match expectations.
3. Review parsing - exotic ASS styles may simplify to plain text in SRT (styling is dropped).
4. Click Convert & Download to save .srt.
5. Import it into your video editor or pair it with Add Subtitle to Video.

Parsing happens locally - subtitle text is not uploaded to a server.

SRT vs styled formats

ASS carries fonts, colors, and positioning. SRT carries index, timecodes, and text only. Conversion is ideal for:

• Uploading to platforms that reject ASS
• Archiving a simple copy
• Fixing broken timecodes in legacy files

If you need burned-in styles on picture, use Add Subtitle to Video with burn-in enabled.

When to normalize vs convert

You do not always need a format change. If you already have .srt but players show duplicate lines, broken indices, or mixed comma/dot milliseconds, run the file through Subtitle to SRT to normalize structure without leaving the SRT family.

Full conversion (VTT, ASS, SBV, TXT → SRT) is for platforms that reject the source format or editors that only import SubRip. Normalization is for legacy files that are "almost SRT" but fail strict parsers.

If timing is wrong by seconds throughout, fix drift in your NLE after import — this tool does not auto-sync to video.

Multi-file and translation workflows

Localization teams often receive ASS from fansub groups and need clean SRT for enterprise upload portals. Convert each language to its own .srt — never stack languages in one file unless the player explicitly expects it.

When translating, keep cue indices aligned across languages so editors can swap tracks without retiming. If indices shift after conversion, renumber in a text editor before handoff.

For YouTube SBV exports, verify chapter markers did not import as spurious cues — delete boilerplate blocks before muxing with Add Subtitle to Video.

After conversion: validating SRT

Open the downloaded .srt in a text editor and spot-check:

• Indices increment 1, 2, 3... without gaps
• Timecodes use HH:MM:SS,mmm commas for milliseconds
• Blank line separates blocks

Import it into your NLE's subtitle panel and scrub the first minute - fixes here are faster than re-exporting video.

Tips for clean conversions

• UTF-8 encoding - save source files as UTF-8 to avoid mojibake in CJK or accented characters.
• Fix timing in editor - conversion does not magically sync drift; adjust in your NLE after import.
• One language per file - multi-language tracks should be separate files.
• Validate entry count - a sudden drop may mean malformed source blocks.

Common issues

Entry count lower than expected. Source file may have gaps or invalid blocks - open it in a text editor.

Styling lost. Expected when leaving ASS for SRT - use burn-in if visuals matter.

Player still rejects SRT. Check BOM, line endings, or try re-importing through this tool to normalize.

Frequently asked questions

Are subtitles uploaded?

No - parsing and conversion run on your device.

Can TXT without timing work?

Plain TXT may parse if structure matches expected patterns; timing-heavy sources work best.

What about SCC or TTML?

Stick to listed formats; convert externally first if needed.

Related tools

• Add Subtitle to Video - mux or burn subtitles into MP4
• Trim Video - align video length after subtitle edits
• Video to MP4 - container prep before subtitling