Home/Tools/Subtitle converter

Subtitle converter

Convert subtitles between SRT, ASS and WebVTT. The file is read in your browser and never uploaded; ASS styling, fonts and positioning do not follow it into SRT.

Pick a subtitle file

UTF-8, GBK and files with a BOM are all read. The file is parsed on this page only; no network request is made.

No file selected yet.

Result

Detected
—
Cues
—
Encoding
—
Notes
—

Preview

The first 60 lines of the result. Use Download for the whole file.

What a conversion loses

DirectionWhat is lost
ASS / SSA → SRT, VTTStyles, fonts, sizes, colours, positioning (\pos, \move), transition effects (\t), karaoke timing and vector drawings. Timecodes and text only.
ASS → anythingComment lines, sound and drawing events are not converted; only Dialogue is taken.
VTT → SRT, ASSNOTE, STYLE and REGION blocks, cue alignment and line position (align:, line:), and inline tags such as <c>.
SRT, VTT → ASSNothing is lost, but one default style is applied: Microsoft YaHei 64, white text with a dark outline, bottom centre. Change it in the player or in Aegisub.
Time precisionASS is centisecond (10 ms); SRT and VTT are millisecond. Writing ASS rounds down so neighbouring cues do not overlap.

FAQ

All the layout disappeared after converting to SRT. Did I do something wrong?

No. SRT carries timecodes and plain text only; it has nowhere to put fonts, positions or effects. If you need the layout, do not convert to SRT — watch the file in a player that supports ASS.

Why are there fewer cues than before?

Two kinds get skipped: cues with no text left after tags are stripped, and vector drawing events in ASS. The result column reports how many were skipped.

Is the file uploaded to a server?

No. The page reads the file through the browser's own file API and does all parsing and output locally; no upload request is made.

Why do GBK subtitles look garbled, and can this read them?

It can. The file is first validated as strict UTF-8; if that fails it falls back to GB18030 (which covers GBK), and the result column shows which encoding was used.

Related