Lokalise
Localization platform for apps, games and websites that syncs translation keys with code repositories and design tools.
- Developer API
- Glossary or termbase support
Software and app localization is translation that has to keep up with code. The text in an app lives as keys in resource files, such as JSON, YAML, XLIFF, Android XML or iOS strings files, and those keys change with every release. A localization platform for software pulls new and changed keys from the code base, gets them translated, and pushes the translations back, ideally without a developer copying files by hand.
The tools in this category share that loop but differ in where they fit. Lokalise, Crowdin, Transifex, Lingohub and Phrase's software product connect to GitHub, GitLab and other code hosts and open pull requests with finished translations. Localazy and SimpleLocalize lean on a command line tool that developers run in their build. Tolgee and Weblate are open source and can be self-hosted, which suits teams that want localization inside their own infrastructure. POEditor is a lighter online editor for string files. Gridly organizes content in a spreadsheet-like grid, which fits games and apps with a lot of dialogue and asset text.
Context is the biggest quality problem in software translation. A translator who sees the string "Open" alone cannot know whether it is a verb on a button or an adjective describing a ticket. Good platforms attach screenshots, descriptions and character limits to keys, and some offer in-context editing, where translators change text inside a running copy of the app. Machine translation and AI suggestions have the same blind spot, so context helps both people and models.
Check how the platform handles placeholders, plurals and gender. Strings like "{count} files selected" need different forms in many languages, and a translation that breaks a placeholder can crash a screen. Look for QA checks that catch broken variables, missing plural forms and text that is too long for its space.
What a featured listing costs ยท from $99 a month
Localization platform for apps, games and websites that syncs translation keys with code repositories and design tools.
Localization platform for software and content teams, with repository sync, in-context editing and an app marketplace.
Localization platform for software and web content, with a native SDK that can deliver translations over the air.
Online localization tool for app strings in formats such as PO, JSON and XLIFF, with machine translation and team roles.
Localization platform for developers that automates string upload and download through a CLI and shares translations across projects.
Open source localization platform with in-context editing inside your running web app and a self-hosted option.
Open source web-based localization tool tied closely to Git, which you can host yourself or use as a hosted service.
Translation management for developers with a CLI, translation hosting and automatic translation of missing keys.
Localization platform for software and marketing content with repository integrations and machine translation.
Spreadsheet-style content management for game and app localization, with branching, version history and machine translation.
Think about release flow. Continuous localization means translations arrive as code is merged, so a feature can ship in every language at once. That requires branching support that matches how your team works, and a decision about what happens when a translation is not ready: fall back to English, block the release, or ship and update later. Some platforms can deliver translations over the air to mobile apps, so text can be fixed without a new app store release.
Finally, look at who translates. Some teams hire agencies, some use in-house linguists, and open source and gaming projects often rely on volunteer communities. Crowdin and Weblate are common choices for community translation. Check how each platform handles permissions, reviews and credit for volunteers.
Machine translation has become a normal first step in this category. Many platforms can fill missing keys automatically so a build never ships with blank text, then flag those strings for a linguist to review. That keeps releases moving, but it also means untranslated or unchecked text can reach users quietly. Decide which languages and which screens can ship with machine output and which must wait for review, and use the platform's status labels so everyone can see the difference.
Keep an eye on cost drivers as well. Plans are often priced by the number of keys, seats, projects or AI characters, and a product with many apps and languages can grow past a limit quickly. Cleaning up unused keys before you import them keeps both cost and translator workload down.
Most handle the common ones: JSON, YAML, XLIFF, gettext PO, Android XML, iOS strings and stringsdict, and resource files for .NET and Java. Check your exact formats, especially custom JSON structures, before you commit, since import rules can differ.
It is a setup where new source strings are sent for translation as soon as code is merged, and finished translations flow back automatically. The goal is to ship each release in every language at the same time, instead of translating in a batch after the English version is done.
Through screenshots attached to keys, descriptions written by developers, character limits and in-context editors that show the string inside the running app. The more context a key carries, the fewer wrong translations reach users.