Why video localization belongs in your core workflow

For many localization teams, video still sits outside the system. Text moves through mature workflows, while audio and video rely on separate vendors, tools, and review processes. The next step is not simply localizing more video, but integrating it into the operating model for global content.

Your localization machine hums along nicely. Text in, text out, no drama. You’ve got your workflows dialled in, your translation memories doing the heavy lifting, glossaries keeping everyone honest, vendors who know the drill, and QA gates that catch anything stupid before it ships. It’s a system. It works.

Then video shows up.

A product demo. An onboarding series. Training modules for a new market. Suddenly you’re not in Kansas anymore. Different vendors. Weird file formats. Timelines that refuse to align with anything else you’re managing. What was once a smooth, well-oiled pipeline becomes a patchwork of emails, handoffs, and mild frustration.

That’s the video localization problem in a nutshell. Not a lack of capability  –  you can absolutely do it –  but a lack of defined workflows and integration.

Where the real cost hides

Most organisations have quietly accepted the split. Text goes through the platform. Video gets shipped off to a specialist vendor, or some separate tool that lives in its own little universe. Eventually, the project gets done. A few languages go out the door. Everyone moves on.

The visible costs are easy enough to point at: vendor fees, turnaround times, project management overhead. Tick, tick, tick.

The invisible costs are where things get interesting.

When video sits outside your core workflow, all those lovely linguistic assets you’ve built up over the years? Useless. Translation memories don’t carry over. Glossaries gather dust. Quality standards you take for granted with text have to be rebuilt from scratch every single time. And version control? Fragile at best. Change the source copy and there’s a decent chance the localized video never catches up.

Then there’s the opportunity cost, quietly doing damage in the background. Product demos, training content, marketing campaigns, leadership updates — all that effort, all that budget — stuck in one language, reaching a fraction of the audience it could.

And we already know how this plays out: people engage more, trust more, and convert more in their own language. Leave that gap open, and you’re effectively choosing to grow slower than you could.

A category that’s no longer “nice to have”

For a long time, AV localization got a pass because it was genuinely painful to scale. Transcription, subtitle timing, and voice work are all specialist skills, all expensive, and all awkward to plug into a standard workflow.

That excuse is wearing thin.

The numbers coming out of the NAB Show 2026 tell a pretty clear story. Content supply chain is now the biggest investment area in media operations. Localization is sitting comfortably as the second most active generative AI use case, right behind metadata. About 75% of teams ramped up automation in 2025. 

Businesses are moving beyond the theoretical and into the operational now, but the challenge is how to manage that transition.

The teams building scalable AV workflows today aren’t doing it because they’ve got time and money to burn. They’re doing it because the economics have shifted. Tooling is better. Costs are lower. ROI is easier to prove.

Which matters, because nearly half of teams still point to budget as their main blocker. Integration has to earn its place. Fortunately, it does: fewer vendors, fewer handoffs, faster turnaround, and quality that actually sticks instead of being reinvented every time.

What “integration” actually looks like

Strip away the buzzwords and it’s pretty simple.

Video and audio go through the same system as your text. Same platform. Same linguistic assets. Same workflows.

  • Translation memories? Still working.
  • Glossaries? Still enforced.
  • Review processes? Still intact.

The format changes. The process doesn’t.

In practice, that means a video can move from upload to localized subtitles or voiceover without leaving your ecosystem. No side quests. No rebuilding infrastructure. No extra vendor wrangling.

That’s the idea behind Phrase Studio. It extends the existing Phrase Language Intelligence Platform to handle transcription, subtitling, and dubbing across 100+ languages without introducing a parallel universe of tools and suppliers. Everything you’ve already built  (TMs, glossaries, automation) applies immediately.

Teams already running text through Phrase can have their first localized video out the door in under an hour. Not days. Not after a dozen emails. And crucially, not through an agency detour.

Seeing it, rather than imagining it

On paper, the argument for integrated AV localization is fairly obvious. In practice, people still hesitate… mostly because it’s hard to picture how it actually runs end to end.

So instead of theorising, on June 2, Semih Altinay (VP of AI Solutions) and Alicia Cosh (Principal Solutions Engineer) will show what this looks like in practice. The session covers Phrase Studio end to end, with a live demo of a real video going through transcription, subtitling, and dubbing inside the Phrase workflow, using the same translation memories and glossaries you already apply to text.

Attendees will also get an early look at the Phrase Studio roadmap ahead of wider release. There will be time for questions about how it fits your specific content types and review process.

If video localization has been sitting on the list of things your team will get to eventually, this is a practical hour to understand what bringing it into your existing workflow actually involves.

Localization beyond text: How to bring audio and video into your existing workflow

June 2, 2026 | 4:00 PM CEST / 10:00 AM EDT

Keep exploring

Kevin O'Donnell, founder of Global10x and former VP of International Growth at Dropbox, joined Jason Hemingway on the In Other Words podcast to talk about the reporting gap that's hiding international growth problems in plain sight, and why the teams closest to the data are making it worse.

Blog post

Why most companies don’t have an international dashboard, and what it’s costing them

When you break global revenue down by individual market, patterns emerge that should be driving strategic decisions. Most companies don’t have the reporting infrastructure to see them.

Kevin O'Donnell, founder of Global10x and former VP of International Growth at Dropbox, joined Jason Hemingway on the In Other Words podcast to talk about the accountability gap at the heart of at the center of global expansion strateg

Blog post

Who should own international growth?

When no single leader owns international performance, investment scatters, team priorities diverge, and the signals that would tell leadership where to act never surface in a coherent way.

Blog post

Why the post-editing paradigm is breaking down in the age of LLMs

Progress in translation quality is no longer driven primarily by better models. It’s driven by how those models are orchestrated, and the gap between a well-orchestrated system and a one-shot prompt is only widening.

AI logo surrounded by diverse professional headshots on vibrant blue and purple gradient background

Blog post

Who’s accountable for what AI says to your customers?

When AI generates and adapts messaging across dozens of markets at a scale no human team can review in full, the failures are rarely dramatic. They show up quietly, as declining engagement, higher drop-off, and underperformance in markets leadership thought it had covered.

Kevin O'Donnell, founder of Global10x and former VP of International Growth at Dropbox, joined Jason Hemingway on the In Other Words podcast to talk about why the most common approach to international growth is also the one most likely to fail, and what companies need to change.

Blog post

Why treating international growth as a bolt-on keeps failing, and what shifting left fixes

Shifting left means bringing localization expertise into product and go-to-market decisions at the planning stage, not at launch. Here’s what that looks like in practice.