Lokalise
Manages translating your app, website or help centre across languages, with AI doing the first-pass translation and a reviewer workflow before anything ships.
What it costs
| Tier | Price | For | Includes |
|---|---|---|---|
| Explorer | $149/month | A team that wants the essentials done right and fast. | Collaborative editing, basic AI/machine translation, a glossary, translation memory. |
| Growth | $379/month | A scaling team that needs better automation and control. | Everything in Explorer, plus enhanced automation, advanced seat options, expanded reporting. |
| Advanced | $1,049/month (most popular) | Teams with complex, multi-product translation workflows. | Everything in Growth, plus full workflow customisation and additional enterprise capabilities. |
| Enterprise | Custom pricing, by demo | Global organisations with bespoke security and support needs. | Everything in Advanced, plus dedicated account management, solutions engineering, premium success services, workflow audits. |
Read from Lokalise's own pricing page on 25 Sep 2026. Vendors change prices without notice.
Where it breaks
All four tiers carry a substantial jump from the previous one — Explorer to Growth is roughly 2.5x, Growth to Advanced roughly 2.8x — with no visible middle ground. A team just outgrowing Explorer should check carefully whether Growth's automation actually earns that jump before assuming Advanced is out of reach.
Integrates directly into a development pipeline — CLI, API, and CI/CD connectors push and pull translation strings automatically as code ships, rather than requiring anyone to manually export and re-import files.
First entry in this reference. There is no previous check to compare it against.
Software localisation has a coordination problem underneath the translation problem: a developer adds a new string, a translator needs to see it, a reviewer needs to approve it, and the app needs to ship with the right version in the right language, on a release schedule that doesn’t wait for any of that to happen manually. Lokalise is built to make that coordination automatic rather than a recurring fire drill before each release.
Because it wires directly into CI/CD pipelines, new strings get picked up, sent for AI translation, and routed for human review as code ships — no one has to remember to export a file.
Against Weglot, a genuinely different job
Weglot translates a website’s rendered content with one embed snippet and no developer involvement. Lokalise translates an application’s actual source strings, inside a development workflow, for teams that have engineers and a release process. If you’re translating a marketing site, Weglot is simpler and cheaper. If you’re translating a product’s UI across builds, Lokalise is the tool built for that pipeline.
Where the money goes
The jump between tiers is steep, and it buys automation and workflow control more than it buys translation volume per se. A team should size against how much manual coordination Growth’s automation actually removes, not just the sticker price difference from Explorer.
Get Lokalise
Buying the tool is not the hard part.
The ebook is about what to hand over, in what order, and how you find out when it goes wrong. One payment, no subscription.