The hard part is not opening a text file
An ASS subtitle file is more than dialogue and timestamps. It is also a render recipe: fonts, colors, outlines, positioning, local overrides, and time-based effects can all affect the result. A plain textarea can change the words, but it does not answer the question an editor actually has: what will this look like over the video?
That is where browser ASS workflows often break down. One tool edits cues, another previews a simplified version, and a desktop render step reveals that a line wraps differently or an effect does not survive. The handoff creates avoidable review work.
CutCaption approaches ASS from the video outward. You prepare the caption track against the source, shape the visual result, and generate the ASS file from the same project used for preview and burned export.
What the online workflow looks like
- Create a project from a video and generate captions, or import an existing SRT/VTT track.
- Correct the caption text and line-level timing against playback.
- Use the word timing strip when a cue needs word-level correction.
- Set the global font, size, colors, outline, shadow, background, margins, and position.
- Add per-cue or selected-text overrides only where the base style needs an exception.
- Preview representative scenes through the JASSUB/libass render path.
- Download ASS on Creator or a higher plan, or use the same subtitle state for a burned-in video export.
The global-first approach matters. A stable base style keeps a long track consistent; local exceptions remain deliberate instead of becoming hundreds of disconnected settings.
What the ASS export can carry
CutCaption’s ASS path is designed for the parts of subtitle delivery that SRT cannot express:
- global typography, outline, shadow, background, opacity, margins, and placement;
- per-cue spatial overrides such as anchors, offsets, and rotation;
- selected-text or single-word visual overrides;
- five karaoke and active-word modes when word timing is available;
- social active-line treatments and supported entrance or emphasis effects.
If the destination only needs selectable accessibility captions, SRT or VTT may be the simpler deliverable. If a client needs the styled subtitle program, ASS is the useful handoff.
An important input limitation
CutCaption is not currently an online editor for opening arbitrary existing .ass files. Manual subtitle import supports SRT and VTT. The ASS workflow starts with generated captions or those supported subtitle inputs, then produces ASS as an output.
That distinction prevents a misleading promise. Use CutCaption when the job is to create and finish styled subtitles from a video project. Keep a specialist ASS text editor in the loop when the job is to preserve and modify an existing hand-authored ASS script byte for byte.
Preview before you hand off
Check the scenes most likely to expose problems: bright footage, lower thirds, fast speech, long names, and a change in aspect ratio. Confirm font availability on the playback system that will open the ASS file. If exact delivery does not depend on the viewer’s subtitle setup, a burned-in export removes that dependency.
For a deeper look at the render path, read the libass subtitle preview guide. If the deliverable starts from raw video, continue with exporting ASS subtitles from video.