Software and technology translation services
We translate your app strings, help center, release notes and product videos, then check every screen in each language so nothing is cut off or broken. We work from your JSON, XLIFF or .strings files, or directly in your localization platform.
Settings
Einstellungen
Einstellungen
English source screen.German button text is cut off.Shortened with the translator. The {count} placeholder is kept.
- We translate
- App strings, websites, help centers, release notes and videos
- File formats
- JSON, XLIFF, .strings, .xml, .po, YAML and Markdown
- Platforms
- Your localization platform or your Git repository
- Checked
- On screen, in each language, by a native speaker
What software localization is
Software localization is adapting a product's interface, help content and messages for users in another language and market. It covers translating the strings, but also date and number formats, plural rules, text that runs longer than the English, right-to-left layouts, and testing the result on real screens.
Technology teams ship often, so we work in small, frequent batches that fit your release cycle, rather than one big translation project a year.
What we do for technology companies
Everything a user sees, from the first screen to the help article.
App and web interfaces
Strings translated with placeholders, plurals and character limits intact. More on software localization.
Help centers and docs
Knowledge base articles and developer docs, kept in sync as you update the English.
Screen testing
Native speakers check every screen for cut-off text, wrong context and untranslated strings.
Product videos
Demos and tutorials with subtitles, voice-over and on-screen text in each language. More on video.
Marketing and app store pages
Landing pages, emails and App Store and Google Play listings, written for each market.
AI training data
Labeled data and model evaluation in your users' languages. For AI teams.
How we fit into your release cycle
New strings go out as they're written, not once a quarter.
Connect
We get access to your localization platform or a branch of your repository.
Context
Screenshots, a test build or a style guide, so translators see where each string appears.
Translate
New and changed strings translated in each batch, with your glossary.
Screen check
A native speaker checks the strings on screen in a test build.
Second check QAShip
Translations pushed back to the platform or as a pull request, ready for release.
Formats and tools
- String files
- JSON, XLIFF, iOS .strings and .stringsdict, Android .xml, .po, YAML, .resx
- Docs
- Markdown, HTML, and help center exports from Zendesk or similar
- Platforms
- Your localization platform, or files through Git Platforms to confirm
- Testing
- Test builds through TestFlight, Android test tracks or a staging site
Related services
Questions about software localization
What is software localization?
Software localization is adapting an app or website for users in another language and market. It includes translating the interface and help content, handling date, number and plural formats, adjusting layouts for longer or right-to-left text, and testing every screen in each language.
Can you work in our localization platform?
Yes. Our translators can work directly in the platform you use, or we can take files from your repository and send them back as a pull request.
How do you handle placeholders and plurals?
Translators keep every placeholder, such as {count} or %s, and add the plural forms each language needs. Our checks flag any string where a placeholder is missing or changed before delivery.
How fast can you turn around new strings?
We agree a turnaround for small batches when we set up the project, based on your release schedule, so new strings don't hold up a release.
Send us a string file
Send a string file or a link to your product, or book a call. We reply with a quote and a plan that fits your release cycle.
- Phone
- +44 20 3290 0116
- Phone hours
- Weekdays 9:30 to 16:00, weekends 9:30 to 12:00, UK time