How to Translate Subtitles: The Complete 2026 Guide to SRT, VTT & Video Editor Workflows

To translate subtitles, you take a subtitle file (usually SRT or VTT), convert the text from the source language into one or more target languages, and re-sync the translated subtitles to the audio — ideally without breaking timecodes, line length, or reading speed. Sounds simple. In practice, most tools get two out of three right and leave you to clean up the third. This guide walks through the full process, the formats that matter, the video editor workflows (Premiere Pro, DaVinci Resolve, Subtitle Edit), what a subtitle translator actually costs in 2026, and how to translate subtitles for free when free is enough.

I've tested most of the tools on this list over the last year — for clients, for our own YouTube channel, and to see how they hold up against what we build at Dubly. What follows is what actually works.

What It Actually Means to Translate Subtitles

To translate subtitles means converting the spoken dialogue and any relevant on-screen text from one language into another, then timing the translated subtitles to the audio so viewers can read them without losing track of the video. The translated text has three jobs at once: stay faithful to the meaning, fit inside a 42-character-per-line budget, and line up with the audio to within ±200ms. Drop one and the audience notices immediately — the flash of a line that cuts off mid-sentence, the subtitle that still reads "hello" three seconds after the speaker has moved on.

Translating subtitles is not the same thing as writing captions. Subtitles assume the viewer can hear the audio and just needs the words in another language. Captions — and specifically SDH (Subtitles for the Deaf and Hard-of-Hearing) — add non-speech cues like [laughter] or [door slams] and speaker identification. Three subtitle types dominate production: open (burned into the video, permanent), closed (a separate track the viewer toggles on or off), and SDH (closed captions with accessibility cues). Most tools that translate subtitles output closed captions by default; if you need burned-in captions for social media, that's a separate export step. Which type you pick depends on the platform — closed for YouTube, burned-in for TikTok and Instagram Reels — which is how you make video content accessible to international audiences without picking the wrong format.

The practical reason to translate subtitles is simple. Adding subtitles increases views by up to 40%, and viewers watching in their native language complete videos at meaningfully higher rates than viewers reading a second-language track. A Verizon Media and Publicis Media study found 80% of people are more likely to finish a video with captions. One upload, subtitles in multiple target languages, same video reaching global audiences without a reshoot. Search engines read subtitle tracks as well — translated subtitles give the same upload a chance to rank and reach new audiences in new markets you aren't actively creating for. That's why teams ditched manual subtitling. Once you're localizing into five languages, going to eight or ten is just more files in the queue. Any video you've already shot is cheaper to localize than to re-shoot, and translating subtitles is the lowest-cost entry point into that process. For a deeper walkthrough of the category itself, see our subtitle translation guide.

How to Translate Subtitles in 5 Steps (The Universal Workflow)

That covers the why. Now the how. Free tool, AI platform, pro agency — the five steps don't change. Skip one and you ship subtitles that flash by, overrun the line, or drift out of sync with the audio. Each step has its own failure mode, and the fastest tools on the market are the ones that compress the steps into a single upload — not the ones that skip them.

1. 1

   Transcribe or import

   Start from a video or an existing source SRT

   ↓
2. 2

   Translate

   Convert the text into the target language

   ↓
3. 3

   Check timing

   Timecodes to ±200ms and reading speed

   ↓
4. 4

   Format for screen

   42 chars, two lines, 1–6 seconds

   ↓
5. 5

   Review before export

   A human pass on anything public-facing

1. Transcribe or import the source subtitle file

You either start from a video (where the tool transcribes the audio and produces a source-language SRT) or from an existing subtitle file in the source language. Importing is faster when you already have an SRT from your editor; transcribing is unavoidable when you don't. Modern speech recognition clears 95%+ accuracy on clean studio audio and drops to 70–80% once background noise, accents, or overlapping speakers enter the mix. Every mistake at this stage compounds through the translation and into the final subtitle file — which is why the cleanest audio you can provide is the single biggest quality lever before you even pick a tool. Bad transcription means bad translation. Full stop.

2. Translate the text into the target language

The transcript or imported file is translated into the target language. A classic subtitle translator hands this off to Google Translate or DeepL one segment at a time. A modern AI subtitle translator runs the whole file through a neural model that keeps sentence-level context — noticeably better on idioms, tone, and creative content. The accuracy range runs from 70–85% for classic machine translation up to 90–95% for neural models on common language pairs, and ~99% for professional human subtitling. What you're picking between is accuracy you can live with versus speed and cost you can afford.

3. Check timing and reading speed

Each translated subtitle needs a start and end timecode accurate to ±200ms. Good tools reuse the timecodes from the source SRT and only rebalance where line length forces a change. Reading speed is where this quietly falls apart. Target around three words per second, and never let a subtitle exceed six seconds on screen or drop below one. Spanish and German typically need 10–20% more space than English — which is why cheap translators often overrun the line and cheap-looking subtitles are almost always a timing problem, not a translation problem.

4. Format for screen (42 chars, two lines, 1–6 seconds)

Professional subtitling standards are narrow on purpose: maximum 42 characters per line, no more than two lines on screen at once, display time between 1 and 6 seconds. Break the 42-character rule and mobile viewports — where most of your audience actually watches — clip the end of every line. Break the two-line rule and the subtitles on the screen cover the face of the speaker. Break the timing rule and the subtitle either flashes by unread or breaks the reading rhythm of the video itself.

5. Review before export

Even at 90%+ neural accuracy, branded or public-facing content gets a human pass. A subtitler fixes brand names, cultural references, and the handful of lines where the AI guessed wrong — then exports the translated subtitle file in SRT, VTT, or whichever format the target platform needs. If your target audience is paying customers rather than casual viewers, the review step is not optional — it's the difference between accessible content and content that loses viewers inside the first fifteen seconds. Review is also where you catch the formatting failures the algorithm missed: lines that fit in your native language but overrun after translation, timecodes that drift a few frames after a cut. Open the translated subtitle file, select the lines that look off, fix them before export. One careful pass saves three support tickets later.

Four Ways to Translate Subtitles (Machine, AI, Professional, Hybrid)

The five-step workflow is the same for every tool. The method you pick — and how much it costs — is not. Four methods dominate. They're not interchangeable. Pick based on the accuracy you can live with, the turnaround your deadline survives, and the budget you've actually got.

Classic machine translation is the baseline Google Translate and older DeepL will give you — fine for a personal video, wrong for anything a compliance officer will watch. Modern AI subtitle translation sits in the 90–95% range on high-resource pairs like English↔Spanish, German, or French, and turnaround collapses from days to minutes. Professional human services charge a premium because the liability is theirs; if you're producing broadcast or regulated content, they remain the default. Hybrid is how most agencies now work: AI drafts the translation, a subtitler tightens timing, fixes cultural references, catches brand names. You get 95%+ accuracy in hours instead of weeks. That's the math that flipped the industry: AI draft plus human review is the baseline now, and studio-session translation is the exception.

The gap between classic MT and modern AI is wider than most buyers realize. On a clean English-to-Spanish product demo, a good AI subtitle translator is nearly indistinguishable from a mid-level human subtitler — in minutes instead of days. But the AI still lags on low-resource languages, idioms, and jargon-heavy regulated content. For those, stay with professional subtitle translation services.

How to Translate SRT Files (The Most Common Format)

Whichever method you pick, SRT is the file format every path meets on. SRT is the format 80% of searches for a subtitle translator are actually asking about. SubRip Text is plain text with timecodes — no styling, no metadata, supported by YouTube, Vimeo, Facebook, and essentially every player shipped in the last fifteen years. If a tool can't read and write clean SRT, it's not a serious subtitle translator.

To translate an SRT file, you have three paths:

1. Drop it into an AI subtitle translator (Dubly, Smartcat, Happy Scribe, OpenL, Editingtools.io). Upload the SRT, pick the target language, download the translated subtitle file. Timecodes are preserved by default. This is the fastest path for a single file.
2. Open it in Subtitle Edit and plug in the Google Translate or DeepL API. Subtitle Edit is a free, open-source desktop editor that professional subtitlers have used for years. The UI is utilitarian, but the engine is rock-solid for SRT editing, format conversion, and timing cleanup.
3. Use a translation service like Smartcat, Rev, or Happy Scribe when the project calls for human review on top of the AI draft. These platforms accept SRT uploads and return translated subtitle files with reviewer-edited translations.

VTT/WebVTT is the second format worth knowing. It adds styling, positioning, and metadata on top of SRT's plain-text core — useful for HTML5 video and modern streaming platforms. Most AI tools export both from the same pass. SSA/ASS is a third format, almost entirely used in anime and fansub communities for karaoke-style effects; skip it unless you know you need it. Choose the format your destination platform supports — YouTube and Vimeo accept SRT and VTT, HTML5 players prefer VTT, and anime-distribution channels stay on SSA/ASS. SUB (MicroDVD) is legacy and rarely needed in 2026.

One practical note for SRT files: some AI subtitle translation tools choke on non-standard SRT formatting — extra blank lines, non-UTF-8 encoding, mixed newline styles exported from older editors. If an upload fails, open the file in Subtitle Edit, save it as clean UTF-8 SRT, and try again. The preparation step takes ten minutes and saves hours of follow-up corrections.

How to Translate Subtitles in Premiere Pro, DaVinci Resolve & Subtitle Edit

That SRT workflow is exactly what every video editor expects. Most video editors ship with subtitle tracks and export to SRT, but none of them translate subtitles natively. The workflow is always the same: generate or import the source-language subtitle file inside the editor, export SRT, translate that file outside the editor with an AI subtitle translator or a manual tool, then re-import the translated SRT as a new subtitle track. Here's how it plays out in the three editors most people are actually cutting in.

Premiere Pro workflow

In Adobe Premiere Pro, open the Captions workspace and use Auto Transcription to generate source-language subtitles from the audio. Edit for accuracy, then export a sidecar SRT file via the Captions panel. According to Adobe's caption translation documentation, Premiere Pro Beta now supports direct caption translation into 17 languages from the Captions panel. For anything beyond that, run the SRT through a subtitle translator — Subtitle Edit, OpenL, or any AI tool that accepts SRT upload — and re-import the translated subtitle file into Premiere as a new caption track. Stack as many target languages as you need; Premiere handles multiple caption tracks per sequence. One gotcha: Premiere's auto-generated SRTs sometimes use non-standard line breaks that trip certain AI translators. See the SRT cleanup note above.

DaVinci Resolve workflow

DaVinci Resolve Studio handles subtitle generation inside the Fairlight and Edit pages via Create Subtitles from Audio. Export the source-language SRT from the Deliver page, translate it externally, then re-import the translated subtitles as a new track. The Studio version supports batch subtitle operations, which matters if you're translating a series. Resolve also renders burned-in captions cleanly if you need to bake subtitles into the final video file for platforms that don't support closed-caption tracks (TikTok, Instagram Reels in some regions).

Subtitle Edit workflow

Subtitle Edit is the power-user tool when the video editor's native features aren't enough. Open an SRT file, select Auto-translate via Google Translate, DeepL, LibreTranslate, or a connected AI API, and the tool translates the whole file segment by segment. Review inline, fix anything the AI got wrong, and export as SRT, VTT, or a dozen other subtitle formats. It also handles timing cleanup, format conversion, spell-check across multiple languages, and merging or splitting subtitle files — the mundane tasks that every serious subtitle translation workflow runs into.

For creators working mostly inside the editor timeline on audio and video edits, the Premiere or Resolve path is usually enough. For anyone editing subtitle files as a recurring task, Subtitle Edit plus a paid DeepL or AI-tool API is the combination that pays for itself within a month.

Best Tools to Translate Subtitles in 2026

Tested most of these for clients or for our own content in the last year. Here's the honest shortlist — what each tool is best for, and one thing worth knowing before you commit.

Dubly — Best for subtitles + dubbed audio in one workflow

We built Dubly to handle the subtitle-plus-dubbed-audio workflow as one run, not three. That's the only reason to pick it over something like Smartcat or OpenL for subtitles-only work. If you just need a translated subtitle file, use one of those and save money. If you need subtitles AND voice-cloned audio AND lip sync from the same upload, this is where that lives.

Features that matter: 40+ languages, editable translations with live preview, glossary control for brand vocabulary, multi-speaker detection, and frame-accurate Lip Sync 2.0. Voice cloning preserves the original speaker's tone, audio tracks export separately, and every project exports SRT/VTT/WebVTT. European company, German servers, GDPR by default — matters if you sell into the EU, irrelevant if you don't.

Best for creators and businesses with a subtitles-plus-dubbing workflow. Paid plans start at entry-level; the free trial gives you 1 minute with everything unlocked, no credit card. See current pricing.

Smartcat — Best for SRT file translation at volume

Smartcat is a pure-play subtitle translator with a dedicated SRT translation workflow designed for teams. Upload an SRT file, pick the target language, download the translated subtitle file — the pipeline is built for throughput. The platform handles 280+ languages and supports translation memory, glossaries, and team review, which makes it a strong fit for agencies translating series or libraries. The subtitle translation service is available online in-browser with no install step, and it's easy to hook into an existing post-production workflow.

Best for: post-production teams and agencies with recurring SRT translation volume.

Happy Scribe — Best for accuracy-first subtitle translation

Happy Scribe is transcription-first with subtitle translation support across 120+ languages. Accuracy on common pairs is among the best I've tested, and the interface offers both AI and human-made subtitle options in the same workflow — useful when a project needs professional human translation on a few critical languages and AI on the rest. Team collaboration is more mature than most competitors.

Best for: media teams, podcasters, and anyone who wants human review on the same platform.

Rev — Best for hybrid AI-plus-human subtitle translation

Rev positions itself as the hybrid option: AI generates the first draft, a subtitler cleans it up, the translated subtitle file ships within 24 hours. The ~99% accuracy claim holds up on common pairs and clean audio, and the per-minute pricing sits in the professional range. If accuracy is critical and you want a review workflow without managing the subtitlers yourself, Rev.ai plays in the same space Happy Scribe does.

Best for: branded content where the AI draft is not enough on its own.

Maestra — Best for high-volume batch processing

Maestra is built for throughput. 125+ languages, batch upload, multilingual export, and an integrated subtitle editor. For series, libraries, or agencies running content localization across dozens of video projects a week, Maestra pulls ahead — the batch workflows are fast and the subtitle editor gets out of your way. Voice synthesis is functional but noticeably synthetic; for subtitles-only workflows that's irrelevant.

Best for: teams translating large subtitle-file libraries.

Subtitle Edit + DeepL — Best free desktop stack

Subtitle Edit is free, open-source, and the tool every professional subtitler I know has on their machine. It's not AI-native, but it plugs into Google Translate, DeepL, LibreTranslate, and several AI APIs for the translation step. Unmatched for manually editing SRT files, converting subtitle formats, and tightening timing — 100+ built-in editing tools cover almost every cleanup task you'll ever hit. The UI hasn't changed much in a decade. That's fine — the engine is what you're here for. Advanced features like auto-sync, waveform editing, and batch format conversion are designed for teams who work with subtitle files every day.

Best for: solo creators on a zero budget and anyone editing subtitle files as a daily task.

OpenL / Editingtools.io — Best for pure SRT file translation

OpenL and Editingtools.io are pure file translators designed for one task. Paste or upload an SRT file, pick the target language, download the translated file. They don't transcribe from audio and they don't generate voice, but for translating existing subtitle files across 100+ languages, they're fast, clean, and preserve timecodes. Editingtools.io is pay-per-use with batch support up to 1,000 files per ZIP, which is useful when you need to convert subtitle formats in bulk between SRT, VTT, and SBV for different destinations.

Best for: post-production workflows where the source subtitle file already exists.

CapCut — Best free mobile-first option

CapCut is free and genuinely useful for what it does. The built-in AI subtitle translator handles short-form content across dozens of languages with auto-timing and on-device export. For social clips, UGC, and quick-turn content, the price is hard to beat. Not suited for long-form, regulated, or multi-speaker video.

Best for: creators publishing short-form content on a mobile-first workflow.

Rask AI — Best for broad language coverage with dubbing

Rask AI supports 130+ languages for subtitle translation and AI dubbing. Good for creator-volume work where language breadth matters more than the last 5% of translation accuracy. US-based data processing is the reason I don't recommend it to EU clients with procurement reviews; if that matters, see our Dubly vs. Rask comparison.

Best for: creators publishing in 10+ languages where coverage beats polish.

Google Translate / DeepL — The free baseline

Google Translate and DeepL are the baseline every other tool measures against. DeepL is noticeably better on European pairs; Google wins on coverage across 100+ languages. Neither is built specifically for subtitle files, but both plug into Subtitle Edit as a translation backend. Fine for drafts, not for final output on public-facing content.

Best for: first-pass machine translation inside a subtitle editor.

For deeper AI-specific tool analysis, see our AI subtitle translator deep-dive.

How to Translate Subtitles for Free — When Free Actually Works

"Free" shows up in almost every search that ends in "translate subtitles" because there's real demand to avoid paying for a tool on a simple subtitling job. Sometimes the free stack is the right call. Sometimes it's the most expensive option in disguise — you save the subscription and spend the savings three times over in review time.

Free works when: the video is personal, internal, or user-generated; translation quality isn't brand-critical; the language pair is common (EN↔ES/DE/FR/IT); and you have time to review and fix the machine output. For a creator making one video a month, the free stack gets the job done.

The three free options that actually work:

1. Subtitle Edit + Google Translate (or DeepL free). Open the SRT in Subtitle Edit, select Auto-translate, pick your engine. Review for line length and cultural nuance. Export. Total cost: zero. Total time: an hour per ten-minute video if you actually review the output.
2. CapCut. Free, mobile-first, handles Short-form content well. Built-in AI subtitle translator covers dozens of languages with auto-timing. Not meant for long-form.
3. YouTube's auto-translate feature. Upload the video, let YouTube generate captions and auto-translate to any supported target language. Quality is lower than a dedicated subtitle translator — YouTube's ASR is solid, the translation layer is not — but free is free, and for a channel owner producing for YouTube anyway, no extra tool is needed.

Free falls short when: it's public-facing brand content; you need compliance with WCAG 2.1 AA or FCC closed-captioning rules; you're producing instant localized content across webinars, live streams, or broadcast events; the target language is low-resource; or timing needs to be precise. The free version of many subtitle tools caps you at 10 minutes of video, watermarks the output, or strips the ability to export certain subtitle formats — the limits show up the moment you're trying to ship.

One pattern we see consistently: the buyer who insists on a free workflow ends up paying more in review hours than a paid tool would have cost within the first month. The real question isn't free vs. paid. It's whether an hour of your time is worth more than a month of a paid subscription.

How Much Does It Cost to Translate Subtitles?

Pricing has shifted substantially in the last 18 months, and the models are not comparable with each other: software charges per minute of video and stays roughly flat as you add languages, human subtitlers charge per word or minute and scale linearly, and free tools charge you in hours.

Which model wins comes down to two questions — how many languages, and how public the video is. Both worked through, including the line in the small print that moves a four-language budget by 4×: what subtitle translation costs.

Best Practices for Translating Subtitles That Don't Flash By

The rules below aren't theoretical. They're the ones I see teams break first, and the ones that quietly cost the most time in rework when the translated subtitles go live and viewers complain.

The single biggest quality lever, honestly, is the glossary. Every serious subtitle translation workflow at scale starts with one. For creators with a recurring cast, product lineup, or brand vocabulary, the glossary is what keeps translated subtitles consistent across videos, seasons, and languages.

Where Translating Subtitles Falls Short

None of the above works perfectly. Here's where it breaks — the limitations we see in customer conversations, and the patterns teams use to work around them.

For anything that will air under your name, treat subtitles the way professional TV studios do: AI drafts the translation, a human catches what the AI missed, and nothing ships without a review pass.

Conclusion

Translating subtitles comes down to the same five steps no matter which tool you use: transcribe or import, translate, time, format, review. Pick the method that matches the stakes — free machine translation for personal clips, AI subtitle translation for most commercial video, professional or hybrid for regulated and flagship content. SRT is the format every path meets on, and a human review pass is the one step worth keeping on anything public-facing.

Back to the complete guide: Subtitles — the complete guide

Translate Your First Video

• Results in just a few minutes

• No credit card required

• Best translation quality worldwide

Upload Your Video Now