MagicSub Studio Guides
English
Start Subtitling

Subtitle workflow guides

Subtitle Export Formats: SRT, VTT, TXT, XML, and FCPXML

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 general subtitle formats, while TXT is useful for reading and cleanup.
  • Premiere XML and FCPXML exports 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

Format Best for Notes
SRT General subtitles Widely supported and easy to inspect.
VTT Web captions Useful for HTML video and web workflows.
TXT Plain text review Good for reading, quoting, or manual cleanup.
Premiere Pro XML Premiere timeline workflows Designed to preserve subtitle timing as editable timeline material.
DaVinci Resolve FCPXML Resolve import workflows Uses an FCPXML-style file for timeline handoff.
Final Cut Pro FCPXML Final Cut Pro workflows Designed for Apple's FCPXML import path.

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. TXT is useful when the goal is a time-ordered transcript for reading, quoting, or review.

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.

MagicSub Studio separates Premiere Pro XML, 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, and timeline start time 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

1 Finish review first

Exports reflect the current edited subtitle data.

2 Choose a target program

Pick the format that matches the next editing tool, not just the file extension you recognize.

3 Check the ZIP contents

Use the all-speaker file for simple workflows and per-speaker files for speaker-specific styling.

4 Import and verify

Always test the beginning, middle, and end after importing into an editor.

Review checklist

  • You downloaded SRT or TXT as a review-friendly reference.
  • You checked the project frame rate before using XML or FCPXML in an editor.
  • 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.

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.

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.

Official references

Related guides

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.

Start Subtitling