# Subtitling & audiovisual localization tools compared

> Compare ten timed-text tools by authoring, timing and reading-speed QC, accessibility, collaboration, automation, and professional delivery formats.

Published: 2026-08-19. Updated: 2026-08-20. Last verified: 2026-08-20. Review interval: 90 days. Disclosure: none.

## Use this to eliminate, not crown

Start with a real subtitlers, accessibility teams, media operations, and localization buyers workflow. Eliminate candidates that fail a deployment, format, locale, accessibility, or exit requirement; then test the survivors with your own content.

- Write three non-negotiable gates before opening the table.
- Choose the view that matches the decision in front of you.
- Open the linked documentation for any field that changes the shortlist.
- Run one representative import, production, review, and export cycle.

## Proof-of-work protocol



```
1. Import a representative source with placeholders, markup, plurals, and right-to-left text.
2. Route it through translation, review, QA, and correction.
3. Exercise automation or integration under realistic permissions.
4. Export every asset and target file needed to leave.
5. Record defects, manual steps, plan dependencies, and owner responses.
```

## Comparison data

[Download the versioned JSON dataset](https://admas.net/resources/data/tools.json).

## Frequently asked questions

### What separates a professional subtitling tool from a text editor?

Frame-accurate timing, waveform and shot context, reading-speed and line rules, positioning, accessibility conventions, format validation, video review, and reliable delivery round-trips.

### Can automatic speech recognition produce release-ready captions?

Not by itself. Names, accents, code-switching, punctuation, speaker changes, sound cues, timing, reading speed, and accessibility conventions still require review against the media.

### Which delivery format should we choose?

Choose from the receiving platform or broadcaster backward. Preserve a rich editable master, then validate every required delivery because styling, positioning, precision, and accessibility metadata do not round-trip equally.

## Methodology

Admas reviewed current first-party product documentation against criteria specific to this tool category. A missing claim is recorded as not established, not scored as a failure. Entries describe documented product capabilities, not plan entitlement, implementation quality, security posture, or suitability for a particular organization. Re-run the proposed proof-of-work and export test before procurement.

## Source register

- [Subtitle Edit repository and documentation](https://github.com/SubtitleEdit/subtitleedit) — Subtitle Edit; verified 2026-08-20.
- [Aegisub manual](https://aegisub.org/docs/latest/) — Aegisub; verified 2026-08-20.
- [OOONA product documentation](https://support.ooona.net/) — OOONA; verified 2026-08-20.
- [EZTitles product documentation](https://www.eztitles.com/index.php?page=products) — EZTitles; verified 2026-08-20.
- [CaptionHub knowledge base](https://support.captionhub.com/) — CaptionHub; verified 2026-08-20.
- [Amara platform and API documentation](https://apidocs.amara.org/) — Amara; verified 2026-08-20.
- [SubtitleNEXT help](https://help.subtitlenext.com/) — SubtitleNEXT; verified 2026-08-20.
- [WinCAPS Q4 help](https://broadstream.com/WebHelp/Getting_started/Introduction.htm) — BroadStream; verified 2026-08-20.
- [FAB Subtitler product documentation](https://www.fab-online.com/subtitling/) — F.A. Bernhardt; verified 2026-08-20.
- [Spot subtitling software documentation](https://www.spotsoftware.eu/) — Spot Software; verified 2026-08-20.