Bilingual subtitles for video creators

If you translate, localize or comment on foreign-language video, subtitles are the slowest part. Splitting the work into “the machine drafts” and “a person proofreads and lays it out” puts your time where judgment is actually needed.

A workflow that suits creators

  1. Confirm you may use the footageIf you translate or build on someone else's video, get permission or confirm the licence first. A subtitle tool does not solve copyright, and Twinsub's Terms of Use say responsibility for the content lies with the user.
  2. Produce a bilingual SRT draftDrop the video into Twinsub and get a bilingual file such as .en-zh.srt (the target language is your choice; this is an example). For a batch of footage, drop everything in and let it queue.
  3. ProofreadCheck proper nouns and numbers first, then watch it through; the method is in checking and editing SRT.
  4. Import into your editorCapCut and Final Cut Pro can both import it; the steps are in the import guide.
  5. Style and exportSet the font, outline and position once in the editor, and burn the subtitles into the picture on export.

Why creators choose local subtitling

Honestly, what it does not do

If your workflow is already built around an editor's own caption recognition and you pay for it, you do not have to switch. The trade-offs are on the comparison page.

Coming soon to the Mac App StoremacOS 26 or later, Apple silicon. For early access, write to twinsub@gatheon.com.

Updated 2026-10-11. Back to the Twinsub home page