SSubToolDesk
en
SRT → ASS

Convert SubRip (.srt) to Advanced SubStation Alpha

Turn a plain .srt caption file into a styled .ass subtitle track with a proper style definition and centisecond timing, ready for players and editors that expect ASS. Nothing uploaded to do it.

Detected: …
Drop a file, paste, or edit directly
…

Your files never touch a server. Every conversion on this page runs locally in your browser using the JavaScript FileReader API. Nothing is uploaded, logged, or stored. Safe for confidential Zoom/Teams recordings, unreleased video, and legal interviews.

How the SRT to ASS conversion works

SubRip (.srt) is the simplest widely-used caption format: a cue number, a HH:MM:SS,mmm --> HH:MM:SS,mmm timecode range, and a line or two of text. Advanced SubStation Alpha (.ass), the format Aegisub, many fansub groups, and advanced players like MPV and VLC use, is built for far more: a [Script Info] header, a [V4+ Styles] section defining fonts, colors, outlines, and screen position, and an [Events] section where each line of dialogue references one of those styles. It's a different structure entirely, not just a different timecode separator.

SubToolDesk's SRT to ASS converter parses your SRT cues locally in your browser, converts every timecode from SRT's millisecond format to ASS's centisecond H:MM:SS.cc format, and writes out a complete, valid .ass file: a working [Script Info] block, a single Default style sized and colored for general-purpose viewing, and one Dialogue: line per cue in the [Events] section.

How to convert SRT to ASS (step-by-step)

  • Drag your .srt file onto the converter above, or click “Upload File” to browse for it.
  • Confirm the auto-detected format badge reads SRT.
  • Toggle Strip speaker labels or Strip formatting tags if your source has either.
  • Press Download to save a valid .ass file, named to match your original file.

What the generated .ass file contains

The output is a complete, player-ready ASS file, not just a fragment. It includes a real [Script Info] block, a [V4+ Styles] section with one style named Default (white text, a thin outline and shadow for legibility over video, bottom-centered), and an [Events] section with a Dialogue: line for every cue, each referencing that Default style. You can open the result in Aegisub afterward to adjust fonts, colors, or position, the structural groundwork is already there.

Before and after

SRT input:
1
00:00:09,400 --> 00:00:12,900
Revenue was up eight percent.

ASS output:
[Script Info]
Title: SubToolDesk Export
ScriptType: v4.00+
...

[V4+ Styles]
Format: Name, Fontname, Fontsize, ...
Style: Default,Arial,20,&H00FFFFFF,...

[Events]
Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
Dialogue: 0,0:00:09.40,0:00:12.90,Default,,0,0,0,,Revenue was up eight percent.

Why timecodes look different in ASS

SRT times to the millisecond (00:00:09,400); ASS times to the centisecond, one-hundredth of a second, with a different separator and a non-zero-padded hour (0:00:09.40). The converter handles that rounding automatically, so a cue starting at 9.4 seconds in the source lands at the correct centisecond in the output, no manual recalculation needed.

Why people move from SRT to ASS

  • Fansubbing and anime release groups, where ASS's styling and positioning overrides are the de facto standard for karaoke effects, signage translation, and per-character color coding.
  • Editors working in Aegisub, which is built around the ASS format and expects it as a native project file rather than a plain SRT import.
  • Players and pipelines that render styled overrides, like MPV or certain streaming encoders, where SRT's plain text can't carry positioning or font instructions at all.
  • Starting a styled subtitle project from an existing plain transcript, using this converter to get a structurally valid ASS file in place before adding styles by hand.

Privacy by architecture, not by policy

Parsing the SRT and writing the ASS file both happen in JavaScript running in your browser tab. There is no upload endpoint this feature could hit, which matters as much for a pre-release fansub script as it does for a confidential corporate video.

What this tool intentionally doesn't do

It writes one Default style and doesn't attempt to guess at karaoke timing, per-character colors, or positioning overrides, those are a manual (or Aegisub-assisted) step once you have a valid base file. It also won't parse an existing .ass file's own styling back out if you convert in the other direction; this tool is built for getting plain caption text into valid ASS structure, not round-tripping an already-styled one.

Frequently Asked Questions

How do I convert an SRT file to ASS?

Drag your .srt file onto the converter above, or paste its contents into the left pane. Once the format badge confirms SRT, press Download. A complete, valid .ass file is generated in your browser.

Will the ASS file open correctly in Aegisub, VLC, or MPV?

Yes. The output includes a valid [Script Info] header, a [V4+ Styles] section with a Default style, and an [Events] section with properly formatted Dialogue lines, the structure all three expect.

Does the converter add any styling or just convert the text?

It defines one general-purpose Default style (white text with a thin outline and shadow, bottom-centered) so the file is immediately usable. It doesn't add karaoke timing, per-character colors, or custom positioning, those are a manual follow-up step in an editor like Aegisub.

Why do the timecodes look different in the ASS output?

ASS uses centisecond precision with a different separator than SRT's millisecond format (0:00:09.40 instead of 00:00:09,400). The converter handles this conversion automatically.

Is my subtitle file uploaded anywhere to do this conversion?

No. Parsing the SRT and generating the ASS file both happen entirely in your browser's JavaScript engine. Nothing is sent to a server.

Will YouTube or Vimeo accept an .ass subtitle file?

No. Most upload forms, YouTube and Vimeo included, accept SRT (and sometimes VTT), not ASS. Convert to ASS for editors and players that render its styling (Aegisub, MPV, VLC), but keep an SRT copy for platform uploads.

Is ASS better than SRT, or should I just stick with SRT?

It depends on what you need. ASS supports positioning, karaoke timing, and per-line font and color overrides that SRT simply can't express; SRT is smaller, simpler, and far more widely accepted for general distribution. Use ASS when your workflow specifically needs styling; use SRT for everything else.