UI strings, error messages, onboarding flows, and help documentation — localised for real users.

Software localisation is different from document translation in one critical way: context. A string that says "Save" might mean save a file, save a draft, or save money. Without context, that string becomes a coin flip for the translator. We do not accept context-free string translation as an approach.

We work from annotated string files, screenshots, or live access to the staging environment wherever possible. Translators review strings in context, not as a numbered list. This eliminates the most common class of software localisation errors without requiring a lengthy post-localisation QA cycle.

Supported formats: JSON, XML, XLIFF, PO/POT, RESX, strings (iOS), CSV. We deliver in the same format we receive. No conversion overhead. No manual re-entry.

For mobile apps, we also localise app store listings: titles, short and long descriptions, keyword fields, and screenshots captions. These matter commercially. A well-localised app store listing increases conversion from browse to install in non-English markets significantly more than an accurate but culturally flat description.

In practice

Common questions