The browser needs to preview rules, not just text
An ASS subtitle can contain much more than a cue’s words and start time. Style definitions, inline overrides, margins, alignment, layers, and time-based tags all influence the pixels. A preview that replaces those rules with approximate HTML and CSS may look close until the most important cue.
The mismatch tends to appear in the difficult cases: a long line wraps differently, an outline changes the box, a custom font shifts the width, or a karaoke tag advances on another schedule. A browser editor needs a renderer that understands the output format.
CutCaption uses JASSUB to run libass for high-fidelity subtitle preview in the browser. The generated ASS representation also feeds ASS download and the FFmpeg/libass burned-video path.
Where libass fits in the editing loop
Fast editing feedback and final-output review serve different needs. A lightweight preview can keep text entry responsive. The libass preview is where an editor checks the canonical subtitle program:
- cue timing and layer order;
- font selection, size, outline, shadow, and background;
- line wrapping, margins, alignment, and position;
- per-cue anchors, offsets, rotations, and inline overrides;
- karaoke, active-word, social-line, and supported animation behavior.
That makes libass a review surface, not a technical afterthought at the end of export.
A high-value preview pass
- Save the caption state intended for delivery.
- Open the high-fidelity preview over the source video.
- Check the first cue and the transition into the second.
- Seek to the longest line and confirm wrapping.
- Inspect a bright frame and a visually crowded frame for contrast.
- Review any local position, rotation, or selected-text override.
- Play the fastest time-based effect at normal speed.
- Confirm the final cue clears when expected.
- Export ASS or burned video from that same saved state.
The pass can be short because it targets the cases most likely to expose renderer drift.
Fonts still need a delivery plan
Libass can only use fonts available to the render environment. CutCaption can use built-in fonts and supports custom font upload according to plan entitlements. A burned-in export fixes the selected font into the video. A separate ASS handoff depends on the recipient having the required font and permission to use it.
If the font changes, line wrapping and placement can change too. Package licensed fonts with an ASS delivery when appropriate, or choose a font already available in the target environment.
Libass parity is the practical advantage
The value is not simply that libass runs in a browser. The value is that preview, ASS output, and burned export share the same subtitle model. An editor can make a decision once instead of compensating for one renderer while guessing about another.
A final media check still matters. Video encoding and external playback remain separate from subtitle layout. But the subtitle-specific approval happens against the render family that will ship.
For the broader review model, read why subtitle preview should match export. To deliver the actual script, see export ASS subtitles from video.