SubtitleTHE SUBTITLE FIELD GUIDE / 01
Choose a subtitle format.
Keep what matters.
Your export format determines whether you keep just the words, their timing, or their appearance. An AI subtitle generator should help you make that choice before you download.
| Format | Best for | What this export keeps |
|---|---|---|
| SRT | YouTube and most editors | Text and cue timestamps |
| VTT | Web video tracks | Text and cue timestamps |
| ASS | Styled subtitle workflows | Text, timing, font and text color |
| SSA | Legacy subtitle editors | Text, timing and basic default style |
| SBV | Subtitle import workflows | Text and timestamp pairs |
| SMI | SAMI-compatible players | Text and synchronization markers |
| TXT | Notes and transcripts | Text only |
| JSON | Reopening your project | Cues, word timings when available, and style data |
SRT or VTT: start with your destination
SRT is a practical first choice when a publishing platform asks for a subtitle file. VTT is the standard choice for an HTML video text track. The SRT export uses comma-separated milliseconds; VTT starts with a WEBVTT header and uses decimal points. Both formats from this workspace contain plain captions, not the colored preview design.
Styled captions are not the same as burned-in captions
ASS carries styling instructions that compatible software can interpret. A burned-in video instead contains the caption pixels in the video itself. That design stays visible, but viewers cannot switch it off as a separate subtitle track. Always keep a text-based project copy before making a burned-in export.
Check timing before you publish
- Listen to the first and last cue; verify your video and subtitle file are from the same edit.
- Scan for overlapping timestamps and reading-speed warnings.
- Import the downloaded file into your destination player and test it there.
- Keep the original recording and your JSON project backup.