Aegisub Alternative: When to Switch and When to Stay

Short answer: Aegisub is still the reference tool for typesetting: ASS styling, positioning, karaoke and signs. If that's your job, there's no real replacement. People who search for an Aegisub alternative usually want something else: subtitles generated from speech, a browser tool with nothing to install, or QC and translation for plain SRT/VTT deliveries. For those jobs, generate a draft with Video to Subtitles, repair it with Fix Subtitles, and bring it into Aegisub only if it needs typesetting.

What Aegisub is (and isn't)

From aegisub.org: Aegisub is "a free, cross-platform open source tool for creating and modifying subtitles," which makes it "quick and easy to time subtitles to audio," with "many powerful tools for styling them, including a built-in real-time video preview." It's BSD-licensed, and the site lists v3.5.1 at the time of writing.

What the site doesn't list is speech recognition. Aegisub expects you to type the subtitles, or to arrive with a script or a timed file. That's the gap most "alternative" searches are really about.

Match the tool to the job

All three are legitimate. A common professional stack uses two of them: generate and QC in one, typeset in Aegisub.

ASS vs SRT: what you lose when you leave Aegisub's format

Aegisub's native format is ASS (Advanced SubStation Alpha). A minimal file:

[Script Info]
ScriptType: v4.00+
PlayResX: 1920
PlayResY: 1080

[V4+ Styles]
Format: Name, Fontname, Fontsize, PrimaryColour, ..., Alignment, MarginL, MarginR, MarginV, Encoding
Style: Default,Arial,64,&H00FFFFFF,...,2,40,40,60,1
Style: Sign,Arial,48,&H00FFFFFF,...,8,40,40,60,1

[Events]
Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
Dialogue: 0,0:00:01.00,0:00:03.50,Default,0,0,0,{\i1}Are you coming?{\i0}
Dialogue: 0,0:00:02.00,0:00:05.00,Sign,0,0,0,{\pos(960,120)}CLOSED

Three details trip people up:

1. ASS times are centiseconds (0:00:01.00, one-digit hours). SRT uses milliseconds (00:00:01,000). Converters handle this, but hand edits break it.
2. Styles and override tags ({\pos}, {\i1}, colours, fades) have no SRT equivalent. SRT supports at most basic <i>/<b> tags, and some players ignore those.
3. Overlapping events are normal in ASS. A sign and dialogue can be on screen at once, on different layers. In SRT they become overlapping cues, which many platforms reject.

So when a client wants SRT from an ASS project, run it through ASS to SRT. It strips the styling tags and keeps dialogue and timing, in the browser. Then handle the overlaps (merge the sign into the dialogue cue, or drop it) and run the result through Fix Subtitles.

From our test. We converted a styled .ass file with two styles, override tags and a positioned sign using ASS to SRT. It ran in the browser, with no upload. The sign went in as:

Dialogue: 1,0:00:04.00,0:00:09.00,Sign,0,0,0,{\pos(1420,180)}NORTH HARBOUR - PLATFORM 2

and came out as:

3
00:00:04,000 --> 00:00:09,000
NORTH HARBOUR - PLATFORM 2

All 8 events became 8 cues with their text and timing intact, and \N became a real line break. Dropped: the \pos position, italics and bold, the Sign style, and the speaker names from the Name field. The sign is now an ordinary timed cue with no position. The converter also left the overlaps exactly as they were. Cue 2 still ends at 00:00:06,400, after the sign starts at 00:00:04,000, and the sign runs to 00:00:09,000, past cue 4's start at 00:00:06,800. Those are the overlaps you have to resolve yourself before delivery.

Other formats you'll meet, and how they map to SRT

Projects that pass through Aegisub often arrive in, or have to leave in, other text formats. VideoText's free browser converters cover the common ones. Here's what each looks like, so you can recognise a file before you convert it:

Conversion to SRT always flattens styling and positioning. Make the styled master in ASS or TTML, and treat the SRT as a derived delivery file. After any conversion, re-run the Validator. Overlapping events that were legal in the source format are the most common breakage.

Workflow: draft in VideoText, typeset in Aegisub

For fansub-style or stylised projects where you still want Aegisub's control:

1. Generate the draft. Upload the video to Video to Subtitles, pick the language, generate, and download SRT. Free covers 30 minutes per file. Pro covers 4 hours.
2. Fix mechanics first. Run the SRT through Fix Subtitles to clear overlaps and re-wrap lines to 42 characters. It's easier to typeset a clean file.
3. Open in Aegisub. Aegisub opens SRT. Save as ASS, set your script resolution to the video's (e.g. 1920×1080), and apply your styles.
4. Re-time to the waveform and shot changes. Use Aegisub's audio view for frame-accurate in and out points. Netflix's timing rules are a good discipline even outside streaming: in-times within 1–2 frames of the first audio frame, and at least a 2-frame gap between events (Netflix timing guidelines).
5. Typeset signs on their own style and layer.

Timing discipline to check in any draft

Aegisub users are used to timing by hand to the waveform, so a generated draft can feel loose. These are the checks that matter, using Netflix's published timing rules as the reference (timing guidelines):

• In-times on the first frame of audio, or within 1–2 frames.
• Out-times about half a second past the end of speech when no subtitle follows, unless that would cross a shot change.
• Gaps: at 24 fps, gaps of 3–11 frames between subtitles should be closed to 2 frames ("chaining"). Gaps are either 2 frames or half a second or more.
• Minimum duration of 20 frames, reserved for one- or two-word subtitles.

A draft that gets the words and rough timing right saves the bulk of the work. These frame-level rules are what the Aegisub pass is for.

Workflow: no typesetting needed (most corporate, course and creator video)

If the deliverable is a plain SRT or VTT, you may not need a desktop editor at all:

1. Generate SRT/VTT in Video to Subtitles.
2. Run the check in Fix Subtitles: overlaps, 20 CPS reading speed, 42-character lines, 10-second maximum per cue.
3. Translate if needed with Translate Subtitles, which keeps the timestamps. See translate SRT to Spanish.
4. Burn in, or deliver the file.

The free browser converters and checkers in Subtitle Tools (SRT↔VTT, shift timing, merge, validator, reading speed, line length) cover most of the small jobs people open a desktop editor for.

The "Aegisub on Mac" problem

Aegisub is cross-platform per its site. If you're searching because a build won't run on your macOS version, check the current release and its notes on aegisub.org before you go looking elsewhere. If you want a different desktop editor on a Mac, Subtitle Edit 5 runs on macOS (overview). If you mostly need generation, QC and conversion, a browser tool sidesteps the install entirely. VideoText's own Subtitle Edit alternative page compares that pairing.

Decision table

When VideoText isn't the right fit

Be blunt with yourself about the deliverable. If the subtitles are the art, with moving signs, karaoke timing and per-line fonts, stay in Aegisub. VideoText's Style Studio gives you tested, readable presets for burn-in, not freeform typesetting. If you need output formats beyond SRT and VTT, or broadcast formats, a desktop editor that writes them is the better tool.