L

Open-source alternatives to Lokalise

Weblate is the free, open-source Lokalise alternative we recommend for localizing apps and websites, with translation memory, glossaries, quality checks and a review workflow, connected to your Git repository. Lokalise is a hosted, paid service; self-hosted Weblate has no paid features and keeps your translations on your own server.

3 alternatives Free apps Our pick: Weblate

At a glance

App Good for Code Import from Lokalise Ease of use
Weblate Software and website teams translating their product with staff, freelancers or volunteers Code Open source Import from Lokalise Partly Some setup
Ever Traduora Small software teams that want a simple, free place to translate their app's text Code Open source Import from Lokalise Partly Some setup
Tolgee Small product teams translating a web or mobile app, editing text right inside the app Code Open source Import from Lokalise Partly Some setup

Why look for an alternative to Lokalise?

Lokalise is a hosted translation management system that software teams use to localize apps and websites, with an online editor, translation memory, machine translation and integrations with code repositories.

Teams look for an alternative because Lokalise is a paid hosted service, so the cost rises as the team and the project grow, and every string of an unreleased product sits on Lokalise's servers. A self-hosted Weblate does the same job with no paid features in the software, for one fixed server cost, and keeps your translations on your own server. Tolgee is a second choice for product teams that want translators working inside the app itself. Ever Traduora is a simpler choice for small teams that only need one place to keep and translate their app's text files.

The alternatives, compared

Weblate

Our pick

Translate your app, website and docs together, on your own server.

Does the same job for app and website strings: it connects to the Git repository that holds your translation files, picks up new keys, and commits translations back or opens pull requests, with translation memory, glossaries, quality checks and reviews, all in the free self-hosted app. It reads about 50 file formats, including JSON, Android and Apple strings, and machine translation from DeepL, Google Translate, OpenAI, LibreTranslate and others is optional. Lokalise is run for you; with Weblate you look after the server.

Some setup Open source

Keep your app's translations in one place, with your translators.

The simplest choice for Lokalise's core job: keep your app's text as keys in a project, translate them in a plain web editor, and import and export 12 file formats, including JSON, YAML, XLIFF, gettext PO and Android and Apple strings, with Admin, Editor and Viewer roles and a REST API for your build. It has no machine translation, translation memory, glossary, screenshots, review workflow or Git sync, but it has no paid features or seat limit.

What you gain
  • Every feature is free, with no plan, seat limit or price per word
  • Your app's text and translations stay on your own server
  • A short, simple screen list that a new translator learns in minutes
What is different
  • There is no machine translation, translation memory or glossary
  • It does not connect to your Git repository; you import and export files or use the API
  • There are no ready-made kits for app frameworks and no in-app editing
Some setup Open source

App translation, edited right inside your own app.

Does Lokalise's key-based software localization with a different strength: translators can edit text in your running app by holding Alt or Option and clicking it, and one-click screenshots show where each key appears. It imports and exports JSON, XLIFF, gettext, Android, Apple, Flutter and other formats, with machine translation from your own DeepL, Google, AWS or Azure keys. The free self-hosted edition is limited to 10 seats, and glossaries, QA checks, tasks and single sign-on need a paid licence.

What you gain
  • No monthly plan for up to 10 team members, with no limit on keys or languages
  • Your app's text and translations stay on your own server
  • Translators fix text by clicking it in the real app, with screenshots for context
What is different
  • The free self-hosted version is limited to 10 seats
  • Tasks, glossaries, quality checks, branching, webhooks, single sign-on and detailed permissions need a paid Tolgee licence
  • There is no direct importer from Lokalise or Phrase; you export your files and import them
Some setup Open source

Moving from Lokalise

There is no direct import from Lokalise, so you move the translations themselves. Export all your keys and languages from Lokalise with its bulk export, in the file format your app uses, such as JSON, XLIFF or Android and Apple strings, and commit the files to your repository or upload them to Weblate. In Weblate, create a project and add a component for each set of files; it finds the languages and strings already there. Bring translation memory across as a TMX file if you have one. Workflows, permissions and history stay in Lokalise, so set up your team and review rules again in Weblate. In Tolgee, create a project with its languages and import the exported files on its import screen; to translate inside your app, a developer adds Tolgee's code library or CLI once.

For Ever Traduora, export each language from Lokalise as a file, create a project in Traduora with the same languages, and import each file into its language. Invite your team as editors or viewers once an email service is set up, since invitations go out by email, and have your build fetch translations through Traduora's API with a project key. Translation memory and glossaries stay behind, because Traduora has neither.

Questions

What is the best open-source alternative to Lokalise?

Start with Weblate. All 3 are free and open source.

Should I choose Weblate or Tolgee?

Weblate if you want everything free and your translations in a Git repository, including with volunteer translators. Tolgee if a product team of up to 10 people wants to translate a web or mobile app by clicking text in the running app.

Does Weblate support the file formats my app uses?

Most likely. Weblate reads about 50 formats, including gettext PO, XLIFF, JSON (i18next, Format.JS, go-i18n), Android strings.xml, Apple .strings and .stringsdict, Java properties, RESX, YAML and CSV.

Can Weblate open pull requests with new translations?

Yes. It can commit straight to your repository or open pull or merge requests on GitHub, GitLab, Gitea, Bitbucket and Azure DevOps.

Can Ever Traduora replace Lokalise for a small team?

Yes, if your team mainly needs one shared place to keep, translate and export its app's text files. Traduora has no machine translation, translation memory or app framework kits, so a team that relies on those in Lokalise is better served by Weblate or Tolgee.

Are these Lokalise alternatives really free?

Weblate is free, with no paid features in the self-hosted software. Tolgee's open-source core is free for up to 10 seats, with unlimited translation keys; more seats and team features such as tasks, glossaries, quality checks, branching and single sign-on need a licence priced on request. Machine translation services such as DeepL bill you for their own use. Ever Traduora is free too, with no seat limit. To run any of these apps you need Cloudgate and a server: use hosted Cloudgate, which can also provide the server, or install Cloudgate on a server of your own for free. Cloudgate's plans and prices are at cloudgate.octabyte.io/pricing.

Do I need a developer to replace Lokalise?

No. Cloudgate installs the app you choose on your server and gives it a secure web address, and you use it in your browser instead of Lokalise.