Localization for apps & indie games · Lawrence, NY

You want your game to feel native in three more languages. Here’s how it happens.

en · source menu.play = “Play” shop.buy = “Buy now” settings.title = “Settings” hud.coins = “%d coins” quest.done = “Quest complete!” 5 strings · 1 file ESPTFR JugarJogarJouer Comprar ahoraComprar agoraAcheter AjustesConfiguraçõesParamètres %d monedas%d moedas%d pièces ¡Misión cumplida!Missão cumprida!Quête terminée ! 15 strings · 3 files your English, untouched Spanish · Portuguese · French

Send us your strings. A written quote comes back the next working day, and nothing is billed until you say yes.

The studio

A small studio that reads your strings the way a player will

One job, three languages

Dovetale is a small localization studio in Lawrence, NY. We take apps and indie games from English into Spanish, Portuguese and French, and we hand back files your build can use the same afternoon: translated strings, store pages written for each market, and a play-through that catches what a spreadsheet can’t.

Top-down view of a desk with a marked-up strings printout, a phone showing a translated game menu and a wooden dovetail joint

Languages, each with a named variant. You choose one per file.

One quote, one invoice

Every project gets a written quote listing words, languages and dates. You approve it, we work, you get a single invoice when the files are delivered. Nothing renews itself.

Short strings get a question, not a guess

“Back.” “Charge.” “Draw.” Words like these mean different things on different screens, so we ask you before we choose a word players will see a hundred times.

Spec sheet
SpanishLatin American (es-419) or Spain (es-ES)
PortugueseBrazil (pt-BR) or Portugal (pt-PT)
FrenchFrance (fr-FR) or Canada (fr-CA)
File formats.strings, .xcstrings, .json, .po, .arb, .resx
StoresApp Store Connect and Google Play Console

Deliverables & prices

Three deliverables, each with its price on the page

Rates are in US dollars. You see the total in writing before anything starts.

DeliverableWhat lands in your repoPriceAction
UI strings Translated files in your own format, with placeholders like %@ and {name}, plurals and line breaks left exactly as you wrote them. $0.13per word, per language Quote my strings
Store listings Title, subtitle, description, promo text and keywords for the App Store and Google Play, rewritten for each market and cut to fit every character limit. $385per language, both stores Price my listing
In-context QA A linguist plays your build on a device and logs truncated text, wrong gender, tone slips and missed strings, each with a screenshot. $540per language, per build (up to 6 hours) Book a QA pass
Launch bundle All three languages: up to 3,000 words of UI strings, three store listings and one QA pass on your first build. $3,480one invoice, all three Ask about the bundle

Bigger than 3,000 words, or only one language? Tell us in the form below and we’ll price exactly that.

Before you send anything

Questions people ask before they send a file

Q1

My strings are only half-finished. Is that a problem?

No. Send them as they are. We mark anything that looks likely to change, and the quote covers only the words in the version you approve.

Q2

Will the translation break my screens?

Placeholders, plurals and tags stay untouched. During QA we look at every screen on a device, and if a word won’t fit a button we offer a shorter one rather than changing your layout.

Q3

Which Spanish, which Portuguese?

You pick one variant per file. Latin American Spanish and Brazilian Portuguese are the usual first choices for mobile, and we’ll say so on the first call if your game points somewhere else.

Q4

How long does it take?

For a 3,000-word app, first drafts arrive in 5 working days per language. QA starts the week your build is ready and takes about 2 working days.

Q5

What if I disagree with a choice you made?

Every delivery includes a short note on the tricky calls: jokes, slang, item names. One round of revisions is included in the price, so you can push back without a second invoice.

Q6

Do I have to sign a contract?

You approve a written quote that lists words, languages and dates. That’s the agreement. Then one invoice, sent when the files are delivered.

How a project runs

Five handoffs between your export and the store page

Each handoff has a date and a named deliverable, so you always know what’s next. We write inside the store limits below from the first draft.

App name, characters
30
Google Play short description
80
App Store keywords
100
App Store promo text
170
  1. You send the export

    Drop your strings files and a few screenshots in a shared folder. We read everything and reply with a written quote.

    Day 1 · quote in writing
  2. We settle names and tone

    A 20-minute call to agree on character names, whether players are addressed as tú or usted, tu or vous, and which words stay in English.

    Day 2 · glossary signed off
  3. We translate and adapt

    Strings are translated in your formats. Store listings are written fresh for each market, then checked against every limit.

    Days 3–7 · first drafts
  4. A linguist plays your build

    On a device, in order, the way a new player would. Every problem is logged with a screenshot and a suggested fix.

    Week 2 · QA report
  5. Files back, one invoice

    Final files in your original format, a note on the judgment calls, and one invoice that matches the quote.

    Delivery day · invoice
Three phones from above showing the same app screen in Spanish, Portuguese and French

Get a written quote

Send us what you have. A quote comes back the next working day.

Rough is fine: your game’s name, the languages you want and a ballpark word count. Nothing is billed until you approve the quote.

We reply from contact@joindovetale.com. Your files stay between us and are never used to train anything.

Top-down view of a strings printout, index cards, a ruler and a phone laid out on a dark table

Before the first call

What to have open when we talk

None of this has to be polished. It just saves us both a round of emails.

  • Your strings export. .strings, .xcstrings, .json, .po, .arb or .resx. A half-finished file is fine.
  • Four or five screenshots of the screens with the least room for text.
  • Your store listing today, in English, exactly as it appears.
  • Words that never change: character names, currencies, your title.
  • A TestFlight or APK link, if a build exists, so QA can start the week it’s ready.
Call us Get a quote