How does audio production outsourcing work for a AAA game title?
A AAA audio pipeline is normally run by an internal audio director with three or four external suppliers underneath. The music vendor writes and records the score, often with a live orchestra. The sound design studio builds the effects library and implements it as Wwise or FMOD events wired to gameplay states. A voice vendor handles casting, direction, recording and editing per language. A localization QA team then checks lip sync, subtitle timing and line context inside the build. Deliverables are milestone-based against vertical slice, alpha, beta and certification, with pickup sessions budgeted after each content lock.
Which studios provide game audio and localization?
Audio and localization are often bought together, because both scale with the dialogue script and both deliver per language. Vendors covering both include Side, part of the PTW group, along with Keywords Studios and Lionbridge Games. In this directory 65 studios list audio, localization or both, and the browse filters can require both tags at once. Bundling suits voice-heavy games, where one script drives translation, recording and QA. Splitting suits text-only games, where translation and audio share almost nothing beyond a glossary and a style guide.
How much does it cost to localize a game?
Game localization is priced per source word, and typical market rates run about $0.08 to $0.20 per word depending on language pair and subject matter, with localization QA billed hourly on top. A 50,000-word RPG script therefore falls roughly between $4,000 and $10,000 per language for translation alone, before voice recording, in-build QA and pickups. Voice is the largest single cost, because it adds casting, studio time, direction and per-language editing. Text-only localization into five European languages is a modest line item; full voice localization into ten languages can rival a mid-size art package.
Which major game publishers work with Side for outsourced services?
Side, written in credits as SIDE, is a game audio and localization services company that forms part of the PTW group. It provides voice casting and direction, dialogue recording and editing, audio production, translation and localization QA for game developers and publishers. Specific publisher relationships are almost always covered by NDA until a title ships, and the reliable public sources are the audio and localization credits of individual games plus Side's own client and credits pages. This directory holds no verified client list for Side, so no publisher relationships are asserted here.
What is the difference between localization and localization QA?
Localization is the translation and cultural adaptation of a game's text, audio and assets. Localization QA, usually shortened to LQA, is the testing of that adapted content inside the running build: text overflowing a button, a line delivered with the wrong emotional context, a date format that breaks a layout, a subtitle that desyncs, a symbol or color that fails in a specific market. LQA is billed hourly and needs native speakers playing the actual game rather than reading a spreadsheet. Skipping it is the most common reason a well-translated game still reads badly in market.
How early should you bring an audio partner onto a project?
Bring an audio partner in at vertical slice, when the core loop is playable but not final. That is early enough for a sound designer to influence how audio hooks into gameplay code, and late enough that the mechanics will not be thrown away. Music can start later, since score is written against tone and level structure rather than code. Voice comes last, after the script locks, because rerecording is expensive. The one decision to make at the very start is middleware: choosing between Wwise and FMOD after implementation has begun means redoing the integration.
Should you use one vendor for audio and localization or two?
Use one vendor when the game is voice-heavy across several languages, because a single script drives translation, casting, recording and LQA, and one owner removes the handoff gaps between them. Use two when the game is text-only, or when audio is a small and stylistically specific job, since a boutique sound studio usually beats a large vendor on character while a translation specialist beats it on price. Either way, keep the glossary and style guide on your side of the contract, so changing vendor never restarts terminology work from zero.
