Prepare
Analyze the product and audience; prioritize markets; agree on scope, budget and schedule; assess source files and cultural risks.
A dedicated project manager coordinates your release requirements, language teams and acceptance process.

Analyze the product and audience; prioritize markets; agree on scope, budget and schedule; assess source files and cultural risks.
Set up the glossary, style guide and query log; assign specialists; translate, adapt or record; run terminology and formatting QA.
Test in game, review issues, coordinate fixes and regression testing, then hand over the agreed localization files and quality reports.
Review player feedback within the agreed scope, support updates, and maintain glossaries and translation memories.
We offer 24/7 support and fix quality issues caused by our work with no time limit. This covers errors in language, meaning, formatting, consistency, and cultural wording. New source content, changed requirements, and additional test coverage are quoted separately.
Objective error-rate ceilings are 0.5% for Translation and 0.3% for Adaptation. Error categories, counting method, review sample and acceptance criteria are documented in the project brief; these figures are not a blanket accuracy guarantee for every service.
Example schedules for different content volumes and production stages. Multilingual examples cover 16 target language and regional variants.
English: 7 working days; multilingual: 10 working days.
English: 60 calendar days; multilingual: 70 calendar days.
English: 85 calendar days; multilingual: 120 calendar days.
We confirm your schedule after reviewing the language pairs, content volume, review requirements, recording needs, and release plan.
Share the languages, services, and release dates you have in mind. Our team will follow up by email.