Skip to content

subtitle translation workbench

Translate subtitles without breaking the subtitle file.

Upload one SRT, VTT, ASS, SSA, or SUB file, choose the next language, preview translated cues, and export the same format with timing and styling still intact for YouTube, Resolve, or review handoff.

FormatsSRT, VTT, ASS, SSA, SUB
ExportSame subtitle format
Next routeFile QA or YouTube

Subtitle translation workbench

Translate subtitles in the live workbench

Upload a real subtitle delivery file, inspect the changed cues before export, and keep the same format when the output still needs YouTube, Resolve, or QA review.

Source Language
Target Language

Public demo limit: 15,000 source chars.

Preview sample
Download sample file
TimecodeSource TextTranslation
00:00:12,400 → 00:00:15,900Upload one subtitle file and choose the next language.Chargez un fichier de sous-titres et choisissez la langue cible.
00:00:16,200 → 00:00:19,400The demo only translates the spoken text.La démo traduit uniquement le texte parlé.
00:00:20,000 → 00:00:23,000Timing and subtitle structure remain intact.Le minutage et la structure des sous-titres restent intacts.
Source chars15,0003 sample cues
Usage modePublic demoGoogle sign-in unlocks quota
Output formatSRTReady to export

Timestamp-safe workflow

Copy the QA steps that preserve timing and subtitle structure.

Use this snippet when a creator needs a repeatable handoff: translate text, keep timecodes intact, export the same format, then spot-check in the playback target.

The 3-step precision pipeline

01

Upload the delivery file

Start with a real subtitle file so timecodes, cue order, and format constraints stay visible from the first click.

02

Translate the cue text

Run translation on the subtitle text while preserving the structure around each cue.

03

Review before export

Check translated cues in the preview surface before you export the same format back to your editor.

Format Integrity

Format integrity, guaranteed.

The first screen should answer the task with a visible tool. The supporting facts come right after it: format-safe export, review visibility, and the routes creators use after translation.

  • Timing integrity
  • Same-format export
  • Route-ready review

Japanese · VTT

Web tutorial subtitles for browser-first playback

00:00:12.400 --> 00:00:15.900

字幕ファイルを 1 つアップロードして、次の言語を選択します。

00:00:16.200 --> 00:00:19.400

デモでは話し言葉の部分だけを翻訳します。

Route focus

Pick the route that matches the subtitle handoff

Export the translated file first. The next page depends on where that same-format subtitle file goes after translation.

File-first review

Use the file translator route when the buyer cares most about cue order, file identity, same-format export, and preview-before-export trust.

YouTube subtitle uploads

Use the YouTube workflow when the translated file still needs creator release checks, upload cadence, or multilingual rollout context after export.

Repeat subtitle volume

Use pricing only after the quality check is done and the question becomes repeat usage, not first-file trust.

Translate subtitles online: what matters before you upload?

The online use case adds new questions around file upload, privacy, limits, and whether a browser tool can still preserve format integrity.

Can I translate subtitles online without creating an account?

Yes. The public demo still runs without sign-in. Accounts are used for paid checkout, billing history, and tracked quota after you decide to keep using the workflow.

Does the online demo preserve subtitle formatting?

Yes. The workflow preserves format structure and timing blocks, then replaces translatable text inside each cue.

What is the online demo limit?

The public demo is capped at the free-trial char allowance so the workflow can stay publicly usable without unpriced cost exposure.

Why is there pricing copy if sign-in is required before checkout?

Because the product still needs public pricing, refund, privacy, and file-handling rules before a signed-in user starts a paid checkout flow.

Next step

Open the translator when the file is ready.

Use the live workbench first, then move into the route that matches the delivery job: YouTube uploads, file-first review, or repeat subtitle volume.