Feels local, not translated
Native speakers make sure your product reads naturally in every market.
[ Why localization testing ]
Translated isn’t the same as ready for the market
Good translations can still go wrong inside a product. A word that fits in English overflows in German. A date reads as the wrong month. A checkout asks for a postcode format that doesn’t exist locally. Users notice straight away, and trust drops. Localization testing checks the real product in each language and market, with people who know how it should feel, before your new customers find the problems.
Building support for many languages into your code? See internationalization testing →
Layouts that hold up
Every screen checked for text that doesn’t fit, in every language.
Local features that work
Payments, addresses, tax and formats tested per market.
Ready for every release
Localisation regression keeps every language working as you ship.
What changes from one locale to the next
Small differences that cause real bugs. We check all of them.
Dates
03/04/2026 is 4 March in the US and 3 April in the UK
Numbers
1,234.56 in English, 1.234,56 in German, 1 234,56 in French
Currency
$10.00 before the number; 10,00 € after it in many European countries
Text length
German and French text is often noticeably longer than English
Direction
Arabic and Hebrew read right to left, so the whole UI mirrors
Addresses
Postcode, region and street order vary widely by country
[ What we test ]
Ten checks for a product that feels local
From the words on the screen to how customers pay. Each one lists what we check, when you need it and the problem it prevents.
Linguistic testing by native speakers
Reads naturallyNative speakers check every translated string in context, on the real screens, so your product sounds like it was written for their market.
What we check
- Accuracy, grammar, spelling and tone
- Terminology consistent with your glossary
- Text checked in context, not just in a spreadsheet
- Untranslated, truncated or placeholder text flagged
When you need it
Before launching in a new language, and for each content update.
The problem it preventsTranslations that are technically correct but sound wrong to local users
UI & layout testing in every language
Looks right everywhereTranslated text is often longer or shorter than English. We check every screen in every language for layout problems.
What we check
- Truncated, overlapping or wrapped text
- Buttons, menus and labels that no longer fit
- Fonts and special characters displayed correctly
- Responsive layouts on desktop and mobile per locale
When you need it
For every new language and every UI change.
The problem it preventsA German button that cuts off halfway through the word
Date, time, number & currency formats
Local conventionsEvery market writes dates, numbers and money differently. We check that your product follows each locale’s conventions.
What we check
- Date and time formats, time zones and calendars
- Decimal and thousands separators
- Currency symbols, placement and rounding
- Phone numbers, postcodes and units of measure
When you need it
For any product showing dates, prices or numbers.
The problem it preventsPrices or dates that confuse or mislead customers
Right-to-left layouts
Arabic, Hebrew and moreRight-to-left languages mirror the whole interface. We check that everything flips correctly, and that what shouldn’t flip doesn’t.
What we check
- Mirrored layouts, navigation and icons
- Mixed right-to-left and left-to-right text
- Numbers, dates and phone numbers in RTL context
- Forms, tables and charts in RTL
When you need it
Before launching in Arabic, Hebrew, Persian or Urdu.
The problem it preventsAn interface that reads backwards to the people it was built for
Cultural & content suitability
Fits the marketNative reviewers check that images, colours, examples, names and humour are appropriate and make sense locally.
What we check
- Images, icons and colours with local meaning
- Names, addresses and examples that feel local
- Humour, idioms and references that translate
- Legal, religious and cultural sensitivities flagged
When you need it
Before entering a new market, and for marketing content.
The problem it preventsContent that confuses or offends the people you want to win
Locale-specific functionality
Works locallyLocal features have to work, not just look right: payments, addresses, tax and regulations differ from market to market.
What we check
- Local payment methods and currencies
- Address, phone and postcode formats and validation
- Taxes, invoices and receipts per country
- Locale-based content, pricing and availability
When you need it
For e-commerce, finance and any transactional product.
The problem it preventsCustomers who can’t pay, ship or sign up in their own country
Translation file & string checks
Before it reaches screensWe check your translation files for missing keys, broken placeholders and hard-coded text before they reach testers or users.
What we check
- Missing, duplicate or unused keys
- Placeholders and variables kept intact
- Plural forms and gender agreement
- Hard-coded strings found in the product
When you need it
For every translation update, ideally in your localisation platform.
The problem it preventsVariables such as {name} showing up on customers’ screens
App store listing checks
First impression abroadYour App Store and Google Play listings are often the first thing users see in a new market. We check them in every language.
What we check
- Titles, descriptions and keywords in each language
- Localised screenshots and preview text
- Release notes and in-app purchase names
- Consistency between listing and app
When you need it
Before each store release in new or existing languages.
The problem it preventsA great localised app hidden behind an English-only listing
Localisation regression
Every releaseNew features and text changes can break existing translations. We re-check every supported language on each release.
What we check
- Changed and new strings checked in every language
- Key screens re-tested per locale
- Screenshots compared release to release
- Issues logged per locale in your tracker
When you need it
For every release once you support more than one language.
The problem it preventsA release that is perfect in English and broken in French
Pseudo-localisation
Before translationFake “translated” text that is longer, accented and wrapped in markers shows layout and code problems before you pay for real translation.
What we check
- Longer text to find truncation early
- Accented characters to test fonts and encoding
- Markers to find hard-coded strings
- Run in your build or localisation tool
When you need it
Early in development, before translation starts.
The problem it preventsPaying for translations, then finding the UI can’t hold them
[ Translation vs localization vs internationalization ]
Three jobs that are often confused
Each answers a different question. And every localisation issue we log looks like the one on the right.
| Question it answers | Who and where | |
|---|---|---|
| Translation | Are the words correct? | Translators, outside the product |
| Localisation testing | Does the product work and feel right in this market? | Native speakers and testers, in the real product |
| Internationalisation testing | Is the product built to support any language and region? | QA and developers, in code and pseudo-locales |
Sample localisation issueHigh
- Locale
- de-DE · iPhone 13 mini · Safari
- Screen
- Checkout · payment step
- Issue
- Button text “Jetzt kostenpflichtig bestellen” cut off after “Jetzt kosten…”
- Also
- Price shown as €1,234.56 instead of 1.234,56 €
- Impact
- High · unclear button wording at the point of purchase
- Evidence
- Screenshots in English and German, side by side
Example only. Real issues are logged per locale in your tracker.
[ How we work ]
Six steps from first locale to every release
We catch string and layout problems early, then test each market in context with native speakers.
-
Step 1 of 6
Agree markets and scope
Languages, locales, platforms and the screens and journeys that matter most.
You getLocale and scope list -
Step 2 of 6
Prepare the ground
Glossary, style guide, test accounts and data for each market.
You getLocale test plan -
Step 3 of 6
Check strings early
Translation files and pseudo-localisation before full testing.
You getString check report -
Step 4 of 6
Test in context
Native speakers and testers on real screens, per locale.
You getIssues logged per localeScreenshots -
Step 5 of 6
Fix and retest
Translators and developers fix; we retest every issue.
You getRetest results -
Step 6 of 6
Keep every language working
Localisation regression on each release.
You getRegression results per locale
- Free one-week POCOne key journey checked in one or two of your target languages.
- Native speakersEnglish and French as standard, with native speakers for other languages.
- Works with your translatorsIssues logged where your translators and developers already work.
[ Tools ]
The tools behind our localization testing
12 tools across three jobs. We work in the localisation platform your team already uses.
Localisation platforms
Where translations live.
- LokaliseTranslation management
- CrowdinLocalisation platform
- PhraseTranslation management
- TransifexLocalisation platform
- SmartlingTranslation management
Checks & evidence
Finding and proving issues.
- Microsoft Pseudo-localesEarly layout & text-expansion checks
- SnagitPer-locale screenshot evidence
- BrowserStackReal devices by region
Design & tracking
Context and follow-up.
- FigmaLayouts in each language
- JiraIssues per locale
- TestRailLocale test runs
- Google Sheets / ExcelGlossaries and checklists
See every tool we use on our technology stack page →
[ Case Studies ]
Products our QA engineers have worked on
Each one links to the full write-up by the engineers who ran it. Bilingual English and French testing was part of our work for Supply Ontario; the others show our wider QA work.
[ Ways to work ]
Six ways to get localization testing done
A launch in a new market, checks every release, or extra native speakers for a busy month.
01Dedicated QA teamChoose it when you release every sprint and want testers who know your product.02Managed testingChoose it when you want every language tested and reported for you.03Fixed-price projectChoose it for a launch or a test cycle with a clear scope and date.04On-demand testingChoose it for a release, a launch week or a device sweep.05Staff augmentationChoose it when your team needs extra manual testers for a while.06QA consultingChoose it for a review of your test process, cases and documentation.
Not sure which fits? Find your model in four questions or compare all six.
[ FAQ ]
Localization testing questions, answered
{{ f.a }}
[ Contact us ]
Get a localization test plan for your markets
✓ Free one-week POC✓ NDA before access✓ A QA lead replies the same day