Game localization services for UK studios and publishers

Game localization for global player experiences

Localisation for game interfaces, dialogue, subtitles, tutorials, store content and ongoing updates, adapted for the language, culture, platform and players you want to reach.

120+ languages supported across the service
Human localisation with review and QA options
Secure handling for scripts, assets and builds
Fixed project quote confirmed before work begins
What the service includes

Language that works inside the game, not only on a page.

Game text is connected to controls, screens, characters, variables, player choices and visual space. The localisation process therefore considers context and implementation as well as linguistic accuracy.

Game and genre matching

The project is reviewed according to its platform, genre, audience, age range, tone and target market.

Terminology and character consistency

Item names, abilities, locations, characters and repeated gameplay terms are managed consistently across related assets.

Variables and technical elements protected

Placeholders, tags, commands, line breaks and non-translatable identifiers are considered during translation and review.

Delivery prepared for integration

Completed content is returned in the agreed structure so your team can review, import, test or publish it efficiently.

What we localize

Player-facing content across the complete game experience

Submit related assets together where possible so character voices, item names, controls and gameplay terminology remain consistent.

UI

User interface strings

Menus, settings, buttons, labels, tooltips, alerts, prompts and other text players use to navigate the game.

NAR

Dialogue and narrative

Character dialogue, branching conversations, story text, lore, quest descriptions and narrative choices.

SUB

Subtitles and cinematics

Subtitle text, cinematic dialogue, cut-scene scripts and time-sensitive on-screen content.

TUT

Tutorials and help

Onboarding, control instructions, walkthroughs, hints, help screens and gameplay explanations.

ITM

Items, skills and achievements

Item names, descriptions, abilities, upgrades, achievements, rewards and progression content.

STR

Store and platform pages

Store descriptions, feature lists, release notes, platform text, promotional assets and launch content.

SYS

System messages

Notifications, errors, account messages, multiplayer prompts, moderation text and service communications.

UPD

Updates and live content

Patch notes, new seasons, downloadable content, events, support articles and recurring content updates.

Localization routes

Choose the right workflow for each game asset

Interface strings, story dialogue, subtitles and live-service updates need different context, review and delivery arrangements.

Interface and systems

UI and gameplay localization

For menus, settings, controls, prompts, system messages and gameplay strings that must remain concise and functional.

  • Character and space limits considered
  • Variables and tags protected
  • Consistent gameplay terminology
  • Structured file delivery
Narrative and characters

Dialogue and story adaptation

For character dialogue, branching narratives, quests and lore where voice, personality and dramatic intent matter.

  • Character voice considered
  • Context and relationships reviewed
  • Names and lore kept consistent
  • Cultural references assessed
Video and cinematic assets

Subtitle and script localization

For cut-scenes, trailers, cinematics and dialogue-led content where timing, line length and viewing experience are important.

  • Readable subtitle lengths
  • Timing and line-break requirements
  • Speaker and context information
  • Subtitle-file delivery options
Updates and releases

Ongoing localization support

For patches, seasons, events, downloadable content and recurring releases that need consistent terminology over time.

  • Existing glossary reused
  • Previous translations referenced
  • Incremental content batches
  • Versioned delivery structure
Linguistic quality assurance

A correct translation can still fail without game context.

A short string may be a menu label, character command, item name or error message. Screenshots, speaker notes, string IDs and gameplay context help the linguist select the right wording.

Review can also identify inconsistent terminology, damaged placeholders, unsuitable line lengths and wording that does not match the player action.

Context and intent

Wording is reviewed against the screen, character, action or gameplay situation where it appears.

Terminology control

Names, locations, items, abilities and interface terms remain consistent across assets.

Technical integrity

Placeholders, markup, variables, commands and non-translatable elements are checked carefully.

Length and presentation

Character limits, line breaks, subtitle readability and interface space are considered during review.

Files and assets

Localization support for structured game content

Share the most editable and structured source available. Include reference material or screenshots whenever the strings cannot be understood confidently on their own.

Ask about your file format
JSON / XML Structured strings, resource files and interface content
CSV / XLSX String tables, exports, glossaries and review sheets
TXT / DOCX Scripts, narrative documents and supporting notes
SRT / VTT Subtitles, trailers, cut-scenes and timed dialogue
Audio reference Dialogue context, speaker tone and pronunciation guidance
Screenshots / video Interface context, gameplay flow and visual references
How it works

From source assets to integration-ready delivery.

The files, languages, platform, audience and release plan are reviewed before the final scope, quote and delivery schedule are confirmed.

Upload your game assets
  1. 01

    Send the assets and reference material

    Upload the string files, scripts, subtitles, screenshots, glossaries and any supporting context available.

  2. 02

    Confirm languages, platform and audience

    Include the target markets, game platform, genre, age range, release deadline and required delivery structure.

  3. 03

    Scope and localization planning

    The content is reviewed for volume, repetition, file engineering, context, character limits and required QA.

  4. 04

    Translation and cultural adaptation

    Linguists localize the content while following terminology, character guidance, technical rules and target-market context.

  5. 05

    Review and final delivery

    The files are checked for language, consistency, placeholders and agreed formatting before being returned for integration or test.

Platforms and projects

Game localization for different formats and audiences

The workflow can support a complete release, a specific asset group or recurring content delivered throughout the life of the game.

PC and console games

Interfaces, dialogue, subtitles, store content and player support for desktop and console releases.

Mobile games

Compact UI text, onboarding, notifications, store listings, events and recurring mobile content.

Educational and serious games

Learning instructions, simulations, assessments and specialist subject content for defined audiences.

Live-service and multiplayer games

Seasons, events, patch notes, moderation text, support content and ongoing multilingual updates.

Game localization pricing

A project quote based on content, languages and engineering.

Game localisation is scoped after the source assets have been reviewed. The final quote confirms the language work, file handling, review level, schedule and any additional localisation support.

Languages

Game localization across 120+ languages

Projects are matched according to the source and target language, game genre, platform, audience and intended market.

Browse all languages
FR French
DE German
ES Spanish
IT Italian
JA Japanese
KO Korean
AR Arabic
中文 Chinese
Before you submit

What to include with your game localization project

Complete assets and clear context help the team confirm the correct workflow, quote and delivery structure.

Your game assets

  • String tables, scripts or resource files
  • Subtitles, audio references or cinematic scripts
  • Screenshots, videos or contextual notes
  • Existing glossaries and approved terminology
  • Previous translations that should be followed

Your project instructions

  • The source and target languages
  • The platform, genre and intended players
  • Character limits and protected variables
  • Your release deadline and delivery format
  • Review, testing and confidentiality requirements
Frequently asked questions

Game localization questions

Send the source assets and target markets when you need advice about scope, formats, QA, pricing or delivery.

Ask about your game
What is game localization?

Game localization adapts a game’s interface, dialogue, narrative, subtitles and player-facing content for another language and market while preserving gameplay meaning and creative intent.

What game content can you localize?

Projects can include UI strings, dialogue, quests, tutorials, subtitles, item descriptions, achievements, store pages, system messages, patch notes and player-support content.

Which game platforms can be supported?

The service can support content for PC, console, mobile, educational, simulation and multiplayer game projects. The exact workflow is confirmed after reviewing the files and platform requirements.

What is the difference between game translation and localization?

Translation changes the language while preserving the source meaning. Localization also considers character voice, cultural references, interface space, variables, player expectations and how the content functions inside the game.

Can you localize game subtitles and cinematics?

Yes. Subtitle and cinematic projects can include translated dialogue, timing requirements, readable line lengths, speaker information and delivery in an agreed subtitle format.

Can you work with JSON, XML and spreadsheet files?

Structured game content can be reviewed in formats such as JSON, XML, CSV and XLSX, as well as scripts, documents and subtitle files. Confirm the exact export and required return format before the project starts.

How are variables and placeholders protected?

Provide instructions for variables, tags, commands and text that must not be translated. These elements can then be identified and checked as part of the localization workflow.

How much does game localization cost?

Game localization is quoted after the source files have been reviewed. Pricing depends on content volume, languages, file engineering, repetition, creative complexity, QA requirements and the delivery deadline.

How long does game localization take?

Delivery depends on the word count, number of target languages, file preparation, game complexity, review level and release schedule. A delivery plan is confirmed after the assets have been assessed.

Can you support patches, expansions and ongoing updates?

Ongoing content can be handled in recurring batches using the existing glossary, approved terminology and previous translations to support consistency across releases.

How are unreleased game files handled?

Include any NDA, access, redaction, platform or file-handling requirements when submitting the project so the appropriate workflow can be confirmed before files are shared.

Ready to begin?

Send your game assets for localization review

Upload the source files and include the target languages, platform, audience, required format and release deadline. The team will confirm the workflow, fixed quote and delivery plan before work begins.