Spanish game localization for indie studios and publishers.
Bring your game, demo and Steam page to Spanish-speaking players. I translate English store descriptions, dialogue, menus, tutorials and supporting content into Spanish for indie developers, studios and publishers. Work directly with Sebastián Cortés on the voice, terminology and delivery for your release.
Start with a Steam page or demo
Solo developers and small studios can start with a Steam description, feature list and announcement, or translate a demo before the full game. Publishers can also request a defined package of game text and release materials.
Share the actual copy and intended Spanish-speaking audience. A translated store page does not mean the game itself supports Spanish; your publisher or developer controls the language information shown to players.
- Steam or other store descriptions and promotional text.
- Demo text, menus, tutorials, item names and interface strings.
- Dialogue, quest descriptions, character notes and narrative text.
- Patch notes, announcements and updates to approved translations.
Agree on Latin American Spanish or another audience
Steam distinguishes Spanish from Spain and Latin American Spanish. Confirm the intended audience before requesting a quote, including whether you already have a Spanish version that needs review or adaptation.
Character voice, humor, tone, terminology and forms of address need context. A short interface string may have several meanings; screenshots, descriptions and access to reference material help resolve those questions. The project is accepted after the content and language requirements are reviewed.
Dialogue, UI and game terminology in context
Provide stable string identifiers, the source text, character or speaker, screenshots and any length limits. Explain placeholders, variables, markup, plurals and text that must remain unchanged.
A spreadsheet or agreed text export can separate source, translation and questions. File formats, protected tokens and delivery structure are reviewed from a sample before acceptance. Your team receives the agreed language files with the identifiers and protected tokens needed for its import workflow.
Keep terminology consistent through updates
Share approved names, item terminology, character notes and previous translations. Identify the current source version and the strings that changed so new text can be scoped without assuming every line needs translation again.
Language review checks the translation against the source and supplied context. If you need in-context linguistic review, include the build, access requirements and expected issue-report format in the brief so it can be scoped.
Marketing text, trailers and audio
Store copy may need a different tone from dialogue or interface text. Include the trailer script or subtitle files if these are part of the release so the language work can be assessed together.
Voice recording, subtitle timing, audio production and technical implementation have their own requirements and are confirmed separately.
Get a quote for your Steam page, demo or game
Describe the genre, platforms, audience, source word count, file format, release date and text stability. You can begin without attachments and discuss an NDA or other handling requirements before sharing unreleased material.
The proposal confirms the text, delivery format, review and update arrangements, price and timing.
Explore related services and guidance
Official information
Reviewed October 29, 2026. Check current instructions for your procedure.
Before you send your documents
Can I translate only my Steam page first?
Yes. A store-page text package can be assessed separately from the game or demo. Include the description, features, announcements and any image text that you want covered.
Is Latin American Spanish the same option as Spanish on Steam?
Steam lists Spanish-Spain and Spanish-Latin America separately. Tell me which audience you intend to support. Existing Spanish can be assessed for adaptation instead of assuming the same wording fits every release.
Which files should I send for a game translation quote?
Start with a description of the volume and a sample of the text export, preserving identifiers and explaining variables, tags and character limits. The supported delivery format is confirmed after review; engine project files are not required for an initial inquiry.
How do you work with game string files?
Share a sample export with stable identifiers, placeholders, tags and character limits. The quote confirms the accepted format and language checks. Your developers can use the translated files in their integration workflow; in-context review is scoped when requested.
Can you review an existing Spanish game translation?
An assessment can compare the English source, Spanish draft and supplied context. The scope may be revision, adaptation or a new translation. Provide earlier approved terminology and clarify whether in-build review is requested.
Have a document for review?
Describe the documents, readers, purpose and any recipient instructions. Start without attachments if needed. You’ll receive a proposal with scope, timing and price before work begins.
For casino, sportsbook, poker and betting-related eSports text, see iGaming translation into Spanish.