On this page
The milestonesWhat changed in practiceWhat did not changeWhat it meant for Korean translation workHow quality measurement changedLessons to carry forwardAt the start of 2025, a company's question about AI translation was usually "should we use it?" By the end of the year the question had become "our people already use it in meetings, in email and in the product; how do we control it?" That shift, from adoption to governance, is the real story behind the year's translation technology trends, more than any single product launch.
This is a retrospective, written with the benefit of hindsight from late 2026. It covers what changed in translation technology around 2025, what it meant for work involving Korean, and what stayed stubbornly the same. For a forward-looking overview, see translation trends in the AI-driven economy.
The milestones
| When | What happened | Why it mattered |
|---|---|---|
| July 2024 | DeepL launched what it called its next-generation language model | Set up the move to LLM-based engines in dedicated translation tools |
| Late 2024 | WMT24 findings: "the LLM era is here but MT is not solved yet" | A sober benchmark for everything that followed |
| August 2025 | Google said new live translation features in Translate use its Gemini models | Live conversation translation became a mainstream consumer feature |
| August 2025 | Korea's privacy regulator published guidelines on generative AI and personal information | Sending personal data to AI tools became a compliance question |
| Late 2025 | Google brought live translation to headphones; Apple expanded Live Translation on AirPods to the EU | Speech translation moved into everyday business meetings |
| 22 January 2026 | Korea's AI Framework Act took effect, according to law-firm summaries | New user-facing AI notices, often needed in Korean |
| 2 August 2026 | EU AI Act Article 50 transparency obligations became applicable | Disclosure and marking questions for AI-generated content |
What changed in practice
1. Engines became steerable
Translation engines stopped being black boxes. DeepL added style rules for formatting and stylistic preferences on top of glossaries. Google Cloud Translation's adaptive translation uses a set of your own example translations to steer output toward your style. LLM prompts carry glossaries, style sheets and examples directly. The practical effect: a team's Korean glossary and style sheet became inputs to the engine, not just documents for human translators. Teams that had them saw the benefit immediately; teams without them discovered they needed them. See building a termbase step by step.
2. Speech translation went mainstream
Live translation in earbuds and meeting captions moved from demos to daily use. For Korean, this was most useful in informational settings: site visits, training, internal calls. It was least reliable where Korean business speech is most indirect, in negotiations and sensitive conversations. We compare the options in speech translation tools versus professional interpreting.
3. Governance became the main job
Once every employee had capable AI translation on their phone, the risk moved from "bad translation" to "translation nobody approved, through a tool nobody vetted". Korea's 2025 guidelines on generative AI and personal information, and the new AI laws in Korea and the EU, turned questions about which tool, which account and which data into compliance questions. Companies started writing one-page policies for AI translation the way they once wrote policies for cloud storage. See the governance playbook for real-time translation.
What did not change
Fluent is not faithful
Better enginesErrors that read well and are harder to spotAs output became more natural, reviewers had to read against the source more carefully, not less.Korean structure is hard
Omitted subjects, verb-final sentences, honorific levelsThe same failure points as before, now hidden in smoother proseWho does what, whether a sentence is negated, and which speech level applies still need a person.Binding text needs people
Contracts, labels, patent claimsQualified translation and revisionNo engine changed who is responsible when a translated obligation is wrong.What it meant for Korean translation work
The work moved rather than disappeared. Less translating from scratch on high-volume, low-risk content; more post-editing, terminology, prompt and glossary maintenance, sampling and in-context review. More demand for Korean writing that machines handle poorly: marketing, UX copy, brand stories going from Korean into English. And steady demand for the parts where accountability matters: legal, regulatory, patent and safety text. Our post on the hybrid human-AI operating model describes the roles that emerged.
How quality measurement changed
As engines improved, the question "is this translation good?" got harder to answer at scale. Automatic metrics such as COMET, introduced by researchers at Unbabel in 2020 and trained on human quality judgments, became common for comparing engines and routing content, while research on their pitfalls warned against treating a score as a verdict. Translation management systems added quality estimation scores to decide which segments need human editing. In practice, the teams that got the most from these tools used them to choose where human reviewers should look, and kept a human sample to check that the scores still meant something on their Korean content. We describe that approach in sampling-based and risk-based translation QA.
Lessons to carry forward
- Test engines on your own Korean content, and repeat the test when they update.
- Treat glossaries, style sheets and example sets as engine inputs, and maintain them.
- Write down which tools and accounts are approved for which content, including speech tools.
- Route by risk; keep qualified humans on binding and regulated text.
- Watch the regulatory calendar: AI notices and labels are translation work too.
Updating your Korean workflow after the AI shift?
We help teams decide what to automate, maintain the Korean glossary and style inputs engines now use, and review what still needs a person. See our services →
Read next: Localization trends you can verify