Question 1

What file formats and engines do you support?

Accepted Answer

We work directly with the formats your engine already exports — JSON, XML, .po/.pot, .resx, .strings, .csv, .xlsx, YAML, Unity/Unreal localization tables, and Godot CSVs. We can plug into your build pipeline, your TMS (Crowdin, Lokalise, Phrase, memoQ), or your GitHub repo so new strings flow to linguists on every commit and return ready to merge — no copy-pasting between spreadsheets.

Question 2

What is LQA and do I really need it?

Accepted Answer

Linguistic Quality Assurance is in-context play-testing on the actual build — native gamer-linguists run through real gameplay in each locale to catch truncated UI, broken variables, untranslated strings, mis-timed subtitles, wrong gender or formality, and culturalization issues that never show up in a spreadsheet. For any game with a serious launch budget, LQA is the difference between a clean release and a wave of one-star reviews about broken localization.

Question 3

How do you handle character limits, UI truncation, and dynamic strings?

Accepted Answer

Linguists work in-context with screenshots, character limits, and variable placeholders visible at all times. We never break {playerName}, %d, or rich-text tags. For tight UI we transcreate rather than translate literally — a short, punchy alternative that fits the button without losing meaning. We also flag any source string that simply can't be localized cleanly so design can adjust before ship.

Question 4

Do you do voiceover? Can you mix human VO with multilingual TTS?

Accepted Answer

Yes. We script and direct fully human VO with native voice talent for hero characters and cinematics, and we use modern multilingual TTS where it makes sense — incidental NPC barks, prototype recordings, or large-scale procedural lines — always under human direction with native-speaker review on the final audio. You decide where each lever lands inside your audio budget.

Question 5

What's the turnaround for typical projects?

Accepted Answer

A 10–20k-word mobile or indie title typically ships into 5 languages in 3–4 weeks including LQA. A 200k-word narrative RPG into 10–12 languages with VO scripts runs 8–12 weeks. We agree milestones and per-language SLAs up front and report progress weekly — and for live-ops titles we ship continuous localization on your release cadence, not in batches.

Question 6

How does pricing work?

Accepted Answer

Text is per word, by language pair and content type (UI, narrative, marketing, legal). LQA is billed hourly per locale with a clear bug-report deliverable. Voiceover is per recorded minute plus studio time. We share a fixed-scope quote before any work starts, and translation memory + glossaries compound discounts over the life of the project — repeat strings and live-ops updates get progressively cheaper.

Bring your game to players worldwide — fully localized, culturally adapted, and ready to launch in 100+ languages.

Everything you need,
end to end.

In-game text & UI

Narrative & dialogue

Subtitles & voiceover scripts

Store listings & ASO

Culturalization

LQA testing

Built for the work you actually do.

Mobile & hyper-casual

Indie & narrative RPGs

Strategy, simulation & MMOs

Console & AAA launches

Simple tiers. Tailored proposals.

Starter

Growth

Studio

Questions, answered.

Recent case studies in this service.

Localizing a narrative RPG into 12 languages

Add MarketReady™ to this project

准备好拓展全球市场了吗？