Exports reflect the current edited subtitle data.
Subtitle Export Formats and File Groups
Different AI subtitle formats solve different problems. A review transcript, a web caption file, and an editing timeline file are not the same thing. MagicSub Studio exports a ZIP so editors receive both an all-speaker file and separate files for each speaker.
Key takeaways
- SRT and VTT are good basic subtitle formats, while ASS, SSA, SBV, SMI, and SUB cover styled, platform, or legacy subtitle workflows.
- TXT, CSV, TSV, JSON, and LRC are useful for transcript review, data handoff, automation, and lyric-style timing checks.
- TTML/DFXP support XML-based Timed Text workflows, while Premiere XML, MOGRT-based PRPROJ, and FCPXML are meant for editor timeline workflows.
- Every export includes an all-speaker file plus per-speaker files when speaker data exists.
At-a-glance comparison
| Group | Formats | Best for |
|---|---|---|
| Basic subtitles | SRT, VTT | Broad compatibility, web captions, and quick review. |
| Styled/platform subtitles | ASS, SSA, SBV, SMI, SUB | Style-aware subtitle workflows, YouTube-style SBV, legacy SAMI/SMI, and frame-based MicroDVD files. |
| Timed Text | TTML, DFXP | XML-based timed text compatibility checks and platform handoff tests. |
| Transcript and data | TXT, CSV, TSV, JSON, LRC | Readable transcripts, spreadsheet review, automation, and lyric-style timing checks. |
| Editor-ready files | Premiere Pro XML, MOGRT-based PRPROJ, DaVinci Resolve FCPXML, Final Cut Pro FCPXML | Timeline handoff and Premiere Pro MOGRT template tests. |
Basic subtitle formats
SRT is the most widely used basic subtitle format. Many players and editing programs can import it, and its structure is focused on timing and text. Apple documentation also treats SRT as a simple caption file that can be imported and exported separately.
VTT is common for web players and online publishing workflows. If you only need one broadly readable caption file, SRT or VTT is usually the safest starting point.
Styled, platform, and Timed Text formats
ASS and SSA can carry style-oriented subtitle information, while SBV is useful for YouTube-style SubViewer workflows. SMI/SAMI and MicroDVD SUB help when older players, archives, or existing subtitle assets need a matching file type.
TTML and DFXP are XML-based Timed Text formats. MagicSub Studio writes timing and text into a basic Timed Text file, but delivery-specific broadcast or platform rules should still be verified separately.
Transcript and data formats
TXT is useful when the goal is a readable review transcript. CSV and TSV are better when an editor, producer, or automation script needs rows with start time, end time, speaker, and text.
JSON is useful for custom tools and downstream automation. LRC uses timestamped lyric-style lines, so it is best treated as a lightweight timing reference rather than a full subtitle format with end times.
Editor-oriented formats
Premiere Pro XML and FCPXML exports are meant to carry more than flat subtitle text. Their purpose is to hand timing and placement information into an editing-program timeline.
MOGRT-based PRPROJ goes one step further by placing a user-selected Premiere Pro .mogrt template on each subtitle timing and generating .prproj files. The download ZIP contains an all-speaker project and per-speaker projects.
MagicSub Studio separates Premiere Pro XML, MOGRT-based PRPROJ, DaVinci Resolve FCPXML, and Final Cut Pro FCPXML exports so editors can choose the path that matches their target program. Even then, program version, project frame rate, timeline start time, and MOGRT template structure can require additional adjustment after import.
All-speaker files and per-speaker files
When downloading, MagicSub Studio packages the file containing all speakers together with separate files for each speaker inside a ZIP.
For interviews or multi-person videos, the all-speaker file is useful for review and basic editing, while per-speaker files can support separate colors, positions, tracks, or styling workflows in the editing program.
Recommended workflow
Pick the group that matches the next step: playback captions, styled subtitles, Timed Text, transcript data, or editor handoff.
Use the all-speaker file for simple workflows and per-speaker files for speaker-specific styling.
Always test the beginning, middle, and end after importing into an editor.
Review checklist
- You downloaded SRT, VTT, or TXT as a review-friendly reference.
- You chose CSV, TSV, or JSON if another tool needs structured subtitle data.
- You confirmed whether the target platform expects TTML, DFXP, SBV, SMI, SUB, ASS, or SSA.
- You checked the project frame rate before using XML, FCPXML, or PRPROJ in an editor.
- You prepared a Premiere Pro-created .mogrt file if you plan to use MOGRT-based PRPROJ.
- You know whether per-speaker files are needed for separate colors or track work.
- You checked the subtitle format required by the final publishing platform.
What editors should check in practice
Automatic subtitles are reviewable drafts, not guaranteed final captions. Results from MagicSub Studio can still need editing when the source audio has background noise, overlapping speech, specialized terms, or fast dialogue, so it is worth checking these items before publishing.
- Compare names, brand terms, places, numbers, and units against the original video.
- If a subtitle line is too long or stays on screen too long, split the sentence and adjust the timing.
- When downloading per-speaker files, confirm that the all-speaker file and speaker-specific files match your editing plan.
- For editor-ready files such as Premiere Pro XML, MOGRT-based PRPROJ, and FCPXML, import a small sample into your actual editing application and project settings before committing to the full workflow.
Frequently asked questions
Why not download only one file?
The ZIP keeps a simple all-speaker file and separate speaker files together, which supports both basic and advanced workflows.
Which new format should I choose first?
Choose SRT or VTT for broad compatibility, CSV/TSV/JSON for structured data, ASS/SSA for style-aware subtitle tools, TTML/DFXP for Timed Text checks, and editor formats when the next step is a timeline import.
How is MOGRT-based PRPROJ different from XML?
MOGRT-based PRPROJ creates .prproj files with a selected .mogrt template placed on subtitle timings. It is a beta workflow focused on Premiere Pro-created MOGRT files.
Do XML and FCPXML files include styling templates?
They primarily carry timeline and subtitle information. Program-specific styling or motion templates may still need to be applied in the editor. If you want to test MOGRT placement, use MOGRT-based PRPROJ.
Official references
Related guides
What to check when choosing a free AI automatic subtitle tool for real editing work.
How local media handling works, what is saved, and what users need to reconnect later.
A feature-by-feature guide to the subtitle review screen and timeline editor.
Which MagicSub Studio AI subtitle export formats match Premiere Pro, DaVinci Resolve, and Final Cut Pro workflows.
How speaker separation helps editing, where it can fail, and how to review it.
Why subtitle files and motion templates are different, and how MOGRT-based PRPROJ can fit into the workflow.
What affects browser AI model setup, transcription speed, diarization speed, and long-video stability.
A final review checklist for text accuracy, timing, line breaks, speaker labels, and import checks.
How to use MOGRT-based PRPROJ export for Premiere Pro subtitle templates.
Try it in MagicSub Studio
Choose a video or audio file, select the video language and expected speaker count, then create a free subtitle draft you can review and export.