It is not a timeline editor
There is no waveform and no frame-accurate scrubbing. Global shifting, per-cue text editing and formatting are in scope; frame-by-frame retiming belongs to the editor.
Import a subtitle file, check its structure, shift timing, review readability, fix the cues and export SRT or VTT — one flow, one file, nothing uploaded.
Start the workflowEvery step reads the same working copy, so an edit in step five is what step six exports. Going back never resets your text.
Most subtitle problems are found at the wrong moment: the file looks fine until it reaches the platform. This flow puts structure first, then timing, then how the subtitles actually read, so a fix never hides behind another problem.
There is no waveform and no frame-accurate scrubbing. Global shifting, per-cue text editing and formatting are in scope; frame-by-frame retiming belongs to the editor.
Structural errors stop the export button. Readability warnings never do - they are judgement calls about pacing, not broken files.
42 characters per line, 20 per second, seven seconds on screen. These are starting points; your platform's delivery rules win.
Work top-down once, then loop: fix structure, shift timing, read the warnings, edit only the cues that actually need it, export. If the export fails, go back to step two - the flow keeps your text.
Not in this version. Merging and splitting stay in the dedicated subtitle tools; this flow works one file at a time.
No. Parsing, checking and exporting all happen in this tab, with no network request.
Yes. Export, then import the result to confirm the round trip before delivery.