[Comparison] Recording 400 In-Game Voices — Why 'Glossary-First vs Voice-First' Localization Order Shifts Launch Dates by 3 Months

An RPG heading for global launch has over 10,000 lines of in-game voice. You need to dub dialogue for 400 characters into five languages. The first decision a localization PM must make is: "Do we finalize the glossary first, or start recording voices first?" This single choice can move the launch date forward or backward by three months.

Key Takeaways

Why the Glossary Must Come Before Voice in Game Localization

Game localization is not just translating dialogue. Character names, region names, skill names, item names, and world-specific terminology number in the hundreds, and these terms must appear consistently across voice, subtitles, UI, tutorials, and marketing materials. The glossary is the reference point for all of these.

The International Game Developers Association (IGDA) explicitly outlines best practices for game localization: "Glossary and style guide creation → Translation → Voice production → Linguistic quality assurance." In other words, if you start recording before finalizing the glossary, every terminology change afterward requires re-recording already completed voice lines. One mobile RPG changed a major character's name during the translation review phase, forcing a re-record of over 200 voice lines that mentioned that character. The schedule slipped by six weeks, and additional costs reached 40% of the original budget.

By contrast, finalizing the glossary first allows translators, voice actors, and QA teams to work from the same standard. If terminology changes are needed, they happen before recording, eliminating rework costs. Lionbridge Games, a major game audio localization firm, emphasizes that building a character and proper-noun pronunciation glossary first—then linking it to voice casting, recording, and native audio LQA—is essential to prevent schedule delays and quality degradation.

Polita provides glossary-based voice consistency management as a standard process for game publishers. For game content with heavy proper-noun usage, we finalize the glossary, generate AI dubbing, and have experts review terminology consistency—minimizing re-recording risk. In one mobile game project, we processed over 10,000 lines of in-game dialogue using a glossary-based workflow and delivered on the original schedule without a single terminology change.

How "Voice First" Can Delay Launch by Three Months

Some publishers skip glossary finalization and start recording to accelerate timelines. This approach looks fast at first, but creates a critical bottleneck mid-project.

Real Delay Case: The Vicious Cycle of Terminology Changes and Re-Recording

An RPG scheduled for global launch started recording in five languages six months before release. After recording wrapped, internal QA discovered that three major region names and two character names had trademark conflicts and needed to be changed. These terms appeared in 800 voice lines—4,000 audio files across five languages had to be re-recorded.

The re-recording timeline unfolded as follows:

The project ultimately had to postpone launch by one quarter, and re-recording costs reached 2.3 times the original voice production budget. If the glossary had been finalized first—with legal and marketing review completed before recording—all of this delay and additional cost could have been avoided.

How Terminology Changes Ripple Across the Entire Localization

Terminology in games doesn't just appear in voice. It's embedded in subtitles, UI text, tutorials, quest descriptions, marketing materials, and official websites. When terminology changes after voice recording, all of these elements must be revised. Mismatches between subtitles and voice severely damage player experience and directly impact post-launch review scores.

Side, a game audio localization specialist, explains technically that recording before translation, terminology, and scripts are finalized makes re-recording, editing, and in-engine verification inevitable, causing schedule delays. The ripple effect is especially severe when multiple audio requirements—timed voice, lip-sync, sound sync—are intertwined.

How Glossary-Based Localization Shortens Game Dubbing Schedules

Finalizing the glossary first allows all subsequent work to proceed in parallel. Translators translate dialogue based on the glossary, voice actors record with confirmed terminology, and QA teams review against the same standard. This approach reduces rework and minimizes wait time between phases.

Glossary First vs. Voice First: Schedule Comparison

The table below compares timelines for the same game project (10,000 lines, five languages) under two approaches.

The glossary-first approach invests three weeks upfront in terminology finalization but completes in 14 weeks with no rework. The voice-first approach looks faster initially but averages eight weeks of rework when terminology changes, totaling 19 weeks. The glossary-first approach is five weeks (~1.2 months) faster.

Polita's Glossary-Based Game Dubbing Process

Polita places the glossary at the center of game localization. We receive the glossary from the client or, if none exists, build it collaboratively during the initial translation phase. We then generate AI dubbing based on this standard. Experts review terminology consistency, and we deliver the final voice files along with the glossary, ensuring consistency for future updates or seasonal content.

One mobile game publisher processed over 10,000 lines of in-game dialogue through Polita. Thanks to the glossary-based workflow, they completed their global launch on the original schedule without a single terminology change. The project adapted our standard turnaround of approximately five business days (for 10-minute videos) to large-scale game content, finishing the entire project within three months.

Hybrid Localization: A Strategy for Managing Terminology, Voice, and World-Building Simultaneously

Recent game localization trends are shifting toward "hybrid localization," which manages glossary, voice, and world-building as a single integrated process rather than sequential steps. This approach doesn't just translate and record in order—it designs terminology and voice together, considering world-building, character personality, and cultural context.

Why World-Building-Based Terminology Design Matters

In a fantasy RPG, how do you translate "mana"? Do you keep it as "mana," or adapt it to the fantasy conventions of the target language—"magic power" or another term? This decision isn't just a translation choice—it's about how players in that culture will receive the game's world.

One global RPG translated "mana" as "法力" (fǎlì, "magic power") in Chinese. This was a strategic choice aligned with Chinese wuxia and xianxia genre conventions, making the world-building feel more natural to players. Such decisions can't be made by translators alone—they require collaboration among the game director, localization PM, and cultural consultants, finalized at the glossary stage.

Polita supports hybrid localization by building terminology and tone guides collaboratively with clients, generating AI dubbing based on these standards, and having experts review world-building consistency. For unreleased content (pre-launch games), we use NDA-based secure workflows to proceed without information leaks.

Balancing Speed and Quality by Combining AI Dubbing with Expert Review

In game localization, speed and quality often seem at odds. But combining AI dubbing with expert review secures both. AI converts 10,000 lines of dialogue into voice in one to two days, while experts review terminology consistency, emotional expression, and cultural appropriateness to guarantee final quality.

Polita's Pro plan (12–15 per minute per language) uses script-based voice generation and core review to process large volumes of in-game dialogue quickly. Both plans include glossary-based consistency management and up to two free revision rounds.

What Game Localization PMs Must Do Now to Meet Launch Schedules

If you're a game localization PM facing a global launch, the action is clear: finalize the glossary first. Compile character names, region names, skill names, item names, and world-specific terminology. Review trademark and cultural appropriateness with legal and marketing teams. Make this the shared standard for translators, voice actors, and QA teams.

Glossary Construction Checklist

In game localization, a glossary is not just a spreadsheet. It must include:

Polita can collaborate with game publishers from the glossary construction phase. If a glossary already exists, we generate AI dubbing based on it and have experts review consistency. We provide quote responses within one business day, and free samples allow you to verify terminology consistency and voice quality in advance.

The Trap of Reverse-Engineering Localization Schedules

Many PMs set the launch date first, then reverse-engineer the localization schedule. But game localization experts don't recommend this. Practical guides on game audio localization point out that nearly every project underestimates schedules when terminology finalization and re-recording risk aren't factored in.

Instead, estimate the localization schedule realistically first, then adjust the launch date. If the launch date is already fixed, you need a strategy that combines the glossary-first approach with AI dubbing to minimize rework risk and shorten timelines.

Game localization is not just changing languages—it's transplanting world-building and characters into a new culture. The glossary is the compass for that journey, and voice is the result of following that compass. Reverse the order, and you lose your way—and the launch date recedes. Finalizing the glossary now is the surest way to meet the launch date three months from now.

---

Polita provides multilingual dubbing for games, animation, broadcast, education, and more, combining AI dubbing with expert polishing. With support for over 70 languages, glossary-based consistency management, and experience processing over 45,000 videos annually, we support global launch schedules. Request a free sample and quote at [polita.ai](https://polita.ai).

Frequently Asked Questions

Q. When should a glossary be created in game localization?

The glossary must be finalized at the project's initial stage, before voice recording or translation work begins. Compile proper nouns and world-building terminology first, complete legal and marketing review, then proceed with translation and voice work in parallel based on this standard—shortening schedules without rework.

Q. What problems arise if voice recording starts without a glossary?

If terminology changes are needed, all recorded voice must be re-recorded, delaying schedules by an average of eight weeks or more and increasing costs to over twice the original budget. Terminology mismatches between voice and subtitles degrade player experience and negatively impact post-launch review scores.

Q. Is AI dubbing quality acceptable for game dubbing?

AI dubbing can generate large volumes of dialogue quickly, but expert review is essential for terminology consistency, emotional expression, and cultural appropriateness. Polita uses a hybrid approach—generating AI dubbing, then having experts review against the glossary—and has successfully processed over 10,000 lines of in-game dialogue quickly and accurately.

Q. What's the most effective way to shorten game localization schedules?

Finalize the glossary first, proceed with translation and voice work in parallel, and combine AI dubbing with expert review. This approach minimizes rework and reduces wait time between phases, shortening schedules by an average of five weeks (~1.2 months) compared to the voice-first approach.

Q. What support does Polita provide for game localization?

Polita provides glossary-based voice consistency management, processing of 10,000+ lines of in-game dialogue, NDA-based secure workflows (for unreleased games), support for over 70 languages, and a standard turnaround of approximately five business days (for 10-minute videos). Choose between the Standard plan (20–25 per minute per language), both including up to two free revision rounds.

References

- IGDA Best Practices for Game Localization — States that glossary and style guide creation must precede translation and voice production in game localization stages, and that pre-finalized terminology reduces re-recording risk.

- Lionbridge Games Audio Process — Explains that glossary and pronunciation guide construction must link to voice casting and LQA (linguistic quality assurance) to prevent schedule delays and quality degradation in game voice production.

- Side Audio Localization Optimization — Points out that recording before translation, terminology, and scripts are finalized makes rework and schedule delays inevitable, and the ripple effect grows as audio requirements like timed voice and lip-sync become intertwined.