What is localization?

The short version for a brief

Localization is translation, plus adaptation of format, layout and tone, plus review in context, for named locales. A sentence can be translated correctly and still fail as localization, because it overflows a button, sorts in the wrong place or sounds wrong to the reader.

The localization services page describes how MoniSa runs this work. This guide explains what the word covers, so you can say what you are buying.

What localization changes, layer by layer

Words come first: every string, page and document is translated. This is the obvious layer, and it is usually done.

Length and layout come next. Text grows or shrinks in another language, so buttons, menus and pages are fitted again. For text expansion and flexible layout: W3C Internationalization, Text size in translation (accessed 18 October 2026).

Formats are the third layer: dates, times, numbers, currency, units and sort order follow the market, not the source. For the formats localization adapts: W3C Internationalization, Localization vs. Internationalization (accessed 18 October 2026).

Tone and register cover formality, forms of address and brand voice, so the copy sounds as if it was written for that reader.

Images and references are adapted too: pictures, examples, idioms and colours that work in one market are replaced where they do not carry over.

Regulated text is its own layer. Product labels, packaging and notices have to meet the market's rules before the product ships.

Review in context is the last layer. A native reviewer checks the result on the real screen or page, where the errors that a string file hides become visible.

Translation, localization or transcreation: which one are you buying?

Buy translation when you need the same meaning in another language, in a document that stays as it is: a contract, a manual, a report.

Buy localization when a product, app, site or game has to work in another market: interface strings, a help centre, a checkout, game menus.

Buy transcreation when marketing has to make the same impression even if the words change: a slogan, a campaign, a product launch email.

Most programmes mix all three. A useful brief says which content gets which treatment, instead of buying everything at the most expensive level or the cheapest.

Where localization programmes go wrong: five things from our project records

These are recorded on MoniSa's published case studies. Each paragraph says what happened, then what we take from it.

Terminology drifts from one batch to the next. A German-to-Kazakh automotive programme ran a large volume of manuals and marketing in a language pair with almost no automotive terminology; a domain glossary was built before bulk translation, and a second linguist checked each batch against it. A healthcare SaaS platform was localized into Hindi for five continuous months; the same linguists stayed on the account and a shared glossary held the product terms. A social platform ran for six years across many languages, with two to three linguists per language. What we take from it: consistency is a staffing decision as much as a tooling one. Ask a supplier who will be on your account in month three, not only who does the test.

The text no longer fits the interface. A games programme localized 100+ titles into several languages. Each language expands or contracts text differently, and per-title length handling worked better than one global rule. What we take from it: send screenshots or a build with the strings. A string file alone cannot show a reviewer how much room a word has.

A reviewer's comment is fixed once instead of everywhere. On a 9,007-word low-resource handoff, the case record says the reviewer noted good accuracy on Jamaican Creole plural rules and good readability, and still required corrections to capitalization, punctuation, spelling and grammar. The corrections were applied as global fixes in the client's review workspace, against a confirmed deadline. What we take from it: mixed feedback is normal. Agree in advance that every accepted comment is applied across the whole file and that you get the list of what changed.

Content types arrive one after another when the launch needs them together. A packaged-foods brand entering MENA markets needed food labeling, brochures, marketing and voiceover in Arabic, Kannada and Malayalam for one launch window. They were run as one programme rather than a queue. What we take from it: plan backwards from the launch date and from the content that blocks shipping, labels first.

Work sits idle and gets reassigned. An online retail platform that auto-reassigns idle files was covered on a follow-the-sun model for three and a half years in Dutch, French and Tamil, with a steady team per language. What we take from it: if your platform reassigns work, ask how the supplier covers your time zones, not only its capacity.

Why the effort pays: what research says about buyers

In CSA Research's 2019–2020 consumer survey (8,709 consumers in 29 locales), about 40% of respondents agreed that they buy only from websites or apps in their own language (figures read from the chart in CSA Research, Ensuring Japanese Linguistic Quality, November 2021, page 6). That share is the one a market launch depends on: for those buyers, a page that is not localized is a page they do not buy from.

Before you ask for a localization quote, write down these six things

Each one changes the quote, so having them ready saves a round of questions.

• Locales, not languages. Brazilian or European Portuguese; Simplified or Traditional Chinese. Name the market.
• Surfaces. App, website, help centre, packaging, video, game. Each has its own fitting and review.
• Volume and how it arrives. One launch batch, or a weekly flow. Continuous work is staffed differently.
• Existing glossary and style guide. If none exists, building one is the first task.
• Who reviews on your side, and whether their decision is final.
• The launch date and what blocks it. Labels, legal notices and checkout usually come first.

What goes wrong when a layer is skipped

Each of these is a localization failure in a text that was translated correctly.

• A label that fits in English overflows in another language. "Save changes" (12 characters) becomes "Änderungen speichern" (20 characters) in German.
• A correct translation sorts in the wrong order or shows a date the reader misreads.
• The copy is correct and still sounds as if it was written somewhere else.
• A campaign line that works in one market falls flat word for word in another.
• A regulated label is not ready, and the product cannot ship on the launch date.
• Errors that only show in the product reach the customer.

What to send us for a localization plan

Do not send confidential files in the form; we agree a secure transfer method first. A description is enough to start.

• Target markets or locales
• What needs localizing: app or software, website, help centre or documents, marketing, game, video or audio, labels or packaging
• Approximate volume in words, strings or pages
• Launch date
• Whether a glossary exists, who reviews on your side, and the platform you use