WORD-COUNT PRICING
Small project
$950 USD
Up to 7,916 English source words
- European Spanish localization
- Human linguistic review
- Glossary & consistency review
- Protected-token checks
- Agreed file format & feedback round
English-to-European-Spanish localization for dialogue, quests, menus and item text. Preserve the voice of your game while making terminology, context and protected tokens work together.
Project minimum $950 USD

01 / European Spanish localization
02 / Human linguistic review
03 / Glossary & consistency review
VISUAL DIRECTIONS / SELECT TO ENLARGE
AI-generated concepts for exploring presentation styles. Illustrative text and data; these are not client projects or evidence of technical validation. Select an image to enlarge it.
$0.12 per English source word, with a $950 project minimum. The examples below show how that rate applies.
WORD-COUNT PRICING
$950 USD
Up to 7,916 English source words
Example project
WORD-COUNT PRICING
$1,200 USD
Example scope: 10,000 English source words
WORD-COUNT PRICING
$3,000 USD
Example scope: 25,000 English source words
The rate is $0.12 per English source word, with a $950 project minimum. The project price is the greater of the word-count total and the minimum.
We agree what counts as translatable text before quoting. IDs, programming keys and protected placeholders are excluded. There is no automatic discount for repeated strings unless it appears in your quote.
Prices in USD. Your written quote confirms the accepted scope, total, applicable taxes and schedule before payment.
Need a different scope? Tell us about your project.01 / THE DETAILS THAT MATTER
01
Speaker notes and narrative context help the Spanish voice fit the character and the situation.
02
A shared glossary keeps items, actions and terminology consistent across dialogue and interface text.
03
Protected variables, tags and IDs stay distinct from translatable content, with export checks for the agreed format.
Send source files, word count, context, screenshots and any character limits.
Agree terminology, tone, European Spanish and the supported file structure.
Translate the agreed source version, review the language and check protected tokens.
Receive the agreed file format, terminology notes and one feedback round.
02 / DELIVERABLES & PREPARATION
CSV, XLSX, JSON, XML and PO files can be assessed. Support is confirmed from a sample; custom engine syntax needs separate review. In-game linguistic testing, engineering, voice-over and additional Spanish variants are quoted separately.
Send screenshots, speaker names, string descriptions, character limits and a playable build when available. A word such as “charge” can refer to an attack, a fee or a battery. Context prevents an apparently fluent translation from describing the wrong action.
We confirm the glossary and unresolved terminology before applying decisions across the project. New source text after the agreed version is locked is scoped as an update.
Before you order
The base service is European Spanish. Tell us if you need a different locale so that it can be scoped explicitly.
File and language checks are included. Testing the imported text in a running build is a separate LQA stage because it needs build access, test coverage and a defined issue workflow.
Protected tokens are identified before translation and checked after export. Your team remains responsible for importing the files and validating the game build.
YOUR NEXT STEP
Send a representative string file, source word count, target locale, screenshots and release schedule.
Tell us about your project →