SubToolbox

ASS to SRT Converter — Tags Stripped, Timings Kept

Convert Aegisub ASS/SSA subtitles to plain SRT — styling tags stripped, dialogue and timings intact, in your browser.

Quick answer: Drop an .ass (or .ssa) file and download an .srt: each Dialogue line becomes a numbered cue with the same start and end times, and ASS styling tags like {\i1} or {\fad(200,200)} are removed because SRT cannot display them.

Drop a subtitle file here, or browse — it stays on your device

Output: SRT (.srt)

Core facts
InputASS (.ass) and SSA (.ssa), any Format field order
OutputSRT with sequential numbering
Stripped{\...} override tags, \N kept as line breaks
TimingsASS centiseconds → SRT milliseconds, values identical
LostFonts, colours, positioning, karaoke effects (by design of SRT)

What this tool does

ASS is what Aegisub and the fansub world produce: a powerful script format with styles, colours, positioning and karaoke effects encoded in {\...} tags. SRT is the opposite — plain text, no styling, universally accepted. Converting ASS to SRT means walking the [Events] section, taking each Dialogue line's Start, End and Text fields, deleting the tag soup from the text, and writing standard SRT cues. The conversion here reads the Format line to respect any field order, keeps \N line breaks as real line breaks, and shows you the resulting cue table before download.

Common uses

  • An Aegisub-timed file needs uploading to YouTube, which only takes plain text
  • A fansub-styled .ass must play on a TV or device that only renders SRT
  • Karaoke effects break a video editor's subtitle import — flatten to SRT
  • SSA v4 files from old projects need modernising

What those {\...} tags were doing

ASS override tags control everything a style can and more: {\i1} italics, {\b1} bold, {\an8} positioning at the top, {\fad(200,200)} fade in/out, {\k...} karaoke timing per syllable. They are baked into the text field, which is why an untagged conversion can look like soup. Stripping them leaves pure dialogue — which is precisely what SRT can hold, and what YouTube, TV players and most editors will render.

Frequently Asked Questions

What happens to italics, colours and positioning?
They are removed, because SRT cannot express any styling. The words and their timings are untouched. If you need italic emphasis, some players render <i> in SRT, but support is spotty — the safe assumption is plain text.
Does it handle both .ass and .ssa files?
Yes. SSA (SubStation Alpha v4) is the older ancestor; the parser reads both the [V4+ Styles] and [V4 Styles] variants and follows whichever Format line your file uses, so custom field orders parse correctly.
Why does my text have commas inside — will they break the conversion?
No. ASS stores the dialogue text as the last field, so text containing commas is reconstructed correctly — the parser joins everything after the Text field back together.
Are comments in the ASS file converted?
No — lines starting with “Comment:” are skipped; only “Dialogue:” lines become cues, which matches how players treat them.

More subtitle converters