MagicSub Studio Guides
English
Start Subtitling

Subtitle workflow guides

Export Premiere Pro PRPROJ With a MOGRT Subtitle Template

If you already use Premiere Pro subtitle templates, retyping every AI subtitle into a MOGRT can be the slowest part of the workflow. MagicSub Studio's MOGRT-based PRPROJ export is a beta workflow that places reviewed subtitles into a user-selected Premiere Pro .mogrt template and creates a Premiere Pro project (.prproj) ZIP.

Key takeaways

  • MOGRT-based PRPROJ creates a Premiere Pro project ZIP, not a rendered video with burned-in subtitles.
  • The ZIP contains one all-speaker project and per-speaker projects when speaker data exists.
  • MOGRT internals vary by template, so this is a beta workflow and the result must be checked in Premiere Pro.

At-a-glance comparison

Path Output Best for
SRT A general subtitle file with timing and text Broad compatibility and quick review
Premiere Pro XML An XML timeline handoff for Premiere Pro Working with subtitle blocks as timeline material
MOGRT-based PRPROJ .prproj ZIP with a MOGRT template placed on subtitle timings Testing a Premiere Pro subtitle template directly with reviewed AI subtitles
Manual template work in the editor Templates placed and filled by the editor Complex motion, multiple text fields, or custom template controls

What this export does

When you choose MOGRT-based PRPROJ on the download page, MagicSub Studio asks for a MOGRT file. It reads the Premiere Pro-created .mogrt in the browser and places that template on the current subtitle timings inside generated .prproj files.

The downloaded ZIP contains an all-speaker project and per-speaker projects. This is useful when each speaker needs separate styling, a separate review pass, or a separate template treatment.

How it differs from SRT or XML

SRT and VTT carry text and timing in a simple caption format. Premiere Pro XML is closer to an editing-program handoff, but it does not automatically apply your motion graphics subtitle template.

MOGRT-based PRPROJ is intended to reduce manual template typing by creating a Premiere Pro project that already contains subtitle text placed into a selected MOGRT template workflow.

Why it is beta

MOGRT files can differ in internal structure, text fields, effect controls, fonts, and motion settings. A simple text template may work well, while a complex template with several controls may not update exactly as expected.

For that reason, MagicSub Studio treats this as a beta workflow focused on Premiere Pro-created MOGRT files. Always open the generated project in Premiere Pro and check text, line breaks, placement, motion, and timing before delivery.

Where the MOGRT file is handled

The selected MOGRT file is read only in the browser and is not uploaded to the server. This follows the same local-first direction as MagicSub Studio's video and audio handling.

The result is a PRPROJ ZIP for Premiere Pro review. It does not render an MP4 and it does not burn subtitles into the original video.

Recommended workflow

1 Review the subtitle draft

Use the review screen to check text, speakers, start times, and end times before applying a template.

2 Choose the export format

On the download page, choose MOGRT-based PRPROJ. The MOGRT panel will appear below the format card.

3 Select a MOGRT file

Choose a Premiere Pro-created .mogrt subtitle template. The file is read in the browser and is not uploaded to the server.

4 Download the PRPROJ ZIP

Use the regular download button to receive an all-speaker project plus per-speaker projects.

5 Check in Premiere Pro

Open the generated .prproj files in Premiere Pro and verify template text fields, line breaks, placement, motion, and timing.

Review checklist

  • You prepared a Premiere Pro-created .mogrt file.
  • Subtitle text and timing were reviewed before download.
  • You know the difference between the all-speaker project and per-speaker projects.
  • The MOGRT text fields were replaced with the actual subtitles in Premiere Pro.
  • Start, middle, and end sections were checked for timing and line breaks.
  • You also downloaded SRT or Premiere Pro XML as a reference file.

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

Does every MOGRT subtitle template work?

No guarantee. MOGRT internals vary by template, so some templates may not update or place text exactly as expected. That is why this is presented as a beta feature.

Is my MOGRT file uploaded to the server?

No. The MOGRT file is read in your browser and is not uploaded to the server.

Does this create a rendered video file?

No. It creates a Premiere Pro .prproj ZIP. Final rendering still happens inside Premiere Pro.

Should I still download SRT or XML?

Yes, that is often safer. SRT or Premiere Pro XML can act as a reference if a MOGRT template needs manual adjustment.

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