Cut localization from your backlog

Lokalise connects to GitHub, GitLab, Bitbucket, and your CI/CD pipeline so translation runs in parallel with every build, no manual file management, no localization tickets blocking releases. Teams at IBM, Bosch, and JP Morgan use Lokalise to localize at the same cadence they deploy code.

Try it free Get a demo

Trusted by 1 million users across 3,000+ companies. 10% of global Fortune 500 companies run localization with Lokalise.

“The extensive CLI tooling also makes it easy to implement the localisation process into your development pipeline.”

Solutions Architect, IT & Services (1,001–5,000 employees), Capterra, January 2025

“Where it took us around three weeks for a developer’s flow to implement changes in Germany, launching our services in new European markets with Lokalise took us only 1 to 1.5 weeks.”

Tech Lead, Lemonade

“Before Lokalise, it took developers at least half a day to manage translations and add new keys, whereas, with Lokalise in place, they spend about 80–90% less time on the same tasks.”

Senior Product Manager, Indeavor

“The extensive CLI tooling also makes it easy to implement the localisation process into your development pipeline.”

Solutions Architect, IT & Services (1,001–5,000 employees), Capterra, January 2025

“Where it took us around three weeks for a developer’s flow to implement changes in Germany, launching our services in new European markets with Lokalise took us only 1 to 1.5 weeks.”

Tech Lead, Lemonade

“Before Lokalise, it took developers at least half a day to manage translations and add new keys, whereas, with Lokalise in place, they spend about 80–90% less time on the same tasks.”

Senior Product Manager, Indeavor

The translation tool designed for developers

Code repositories

Sync translation projects with the most popular code repositories — GitHub, GitLab, Bitbucket, and Azure Repos. Integrations are available on all plans.

Branching

Work on multiple branches of your project at the same time. Merge in any direction when ready.

Over-the-air SDKs

Use our over-the-air (OTA) SDKs to send translation updates to iOS, Android, and Flutter apps, or create your own OTA SDK using our public OTA API.

Webhooks

Automatically notify third party apps, in real-time, about events happening in Lokalise.

Custom processors

Automate your pre- and post-translation workflows by running them as part of the upload and download process with Lokalise.

Custom ISO codes

Configure a custom language code and name for each file format exported.

S3 and GCS integration

Export language files to Amazon S3 or Google Cloud Storage or to a content distribution network directly from Lokalise.

Plurals

Complete support for plurals. Lokalise adds plural forms to every language automatically. The number and naming of the plural forms follow the Unicode guidelines. Alter them if needed.

Key referencing

Link one key to another by using referencing placeholders. Update a translation in one key and all referenced keys will also be updated.

Tags

Organize keys in groups. Manage, review, filter, and export keys.

Project snapshots

Create and retrieve backups of any translation project. Set up automatic snapshots and make data recovery quick and easy.

CLI

Lokalise CLI v2 allows you to manipulate any object or data in your Lokalise workspace.

MCP server

Give Cursor, Claude, ChatGPT, and any MCP-compatible tool direct access to your Lokalise project.

Import and export your files in any format

iOS

.strings, .stringsdict, .plist, .xliff, .arb, .xcloc

Android

.arb, .xml

Web

.po, .pot, .properties, .js, .json, .resx, .php, .ini, .yml, .xlf, .csv, .ts

Other

.xls, .xlsx, .stf, .doc, .docx, .html, .srt, .pptx, .idml

iOS

.strings, .stringsdict, .plist, .xliff, .arb, .xcloc

Android

.arb, .xml

Web

.po, .pot, .properties, .js, .json, .resx, .php, .ini, .yml, .xlf, .csv, .ts

Other

.xls, .xlsx, .stf, .doc, .docx, .html, .srt, .pptx, .idml

AI translation built into the pipeline

Lokalise AI translates new strings automatically as they are committed to a project. Custom AI profiles use translation memory and glossaries to produce output consistent with your existing terminology — no prompt engineering required. AI Scoring evaluates every translation against MQM quality criteria in real time and routes high-confidence strings to publish automatically, flagging only what needs human review. For development teams, this means the localization step in the pipeline requires less manual oversight without trading off quality. Teams using Custom AI profiles reach 90%+ acceptance rates, reducing the review queue to under 20% of output.

See Lokalise AI

Frequently asked questions

How does Lokalise integrate with GitHub, GitLab, and CI/CD pipelines?

Lokalise integrates natively with GitHub, GitLab, Bitbucket, and Azure Repos. When new strings are pushed to a branch, translation tasks are created automatically in Lokalise. The CLI integrates into build scripts and CI/CD pipelines for shell-based automation. Webhooks trigger workflow events on translation status changes, enabling event-driven localization without polling the API.

What are Lokalise's over-the-air (OTA) SDKs?

Lokalise OTA SDKs for iOS, Android, and Flutter allow translation updates to be delivered to live apps without submitting a new app version to the app store. When translations are approved in Lokalise, the SDK fetches the latest strings on the next app launch. Copy fixes, new language launches, and terminology updates can ship between development releases — without a developer sprint for each change.

Does Lokalise have a public REST API?

Yes. The Lokalise REST API provides full programmatic access to projects, keys, translations, contributors, files, and workflow management. Developers can import and export translation files in parallel, trigger localization tasks programmatically, and build custom integrations for any tool not covered by native connectors. Full API reference, SDKs, and code samples at developers.lokalise.com.

How does Lokalise help development teams reduce localization bottlenecks?

Lokalise removes localization from the development critical path by automating file sync, context sharing, and workflow triggers. Translators and localization managers work in Lokalise directly — no developer involvement needed for file exports or copy changes. OTA SDKs mean minor copy changes in production apps do not require a new release. Teams using Lokalise report 37% shorter release cycles.

What security and access controls does Lokalise offer for development teams?

Lokalise supports RBAC, SAML SSO (Google, Microsoft Azure AD, Okta, OneLogin, PingFederate, and others), and audit logs with 12-month retention. API access is managed via scoped tokens. Lokalise is SOC 2 Type II assessed and ISO 27001 and ISO 27017 certified. GDPR-compliant, with EU data routing available for teams with data residency requirements.