# General Translation Knowledge Base: General Translation vs. Lokalise: which should you use?
URL: https://generaltranslation.com/en-US/kb/general-translation-vs-lokalise.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: General Translation is a strong Lokalise alternative for teams that want readable copy in JSX and translation built into development. Lokalise is built around shared keys, design-tool integrations, and mobile over-the-air delivery. General Translation generates translations from the app's marked content and supports review in its Dashboard or in GitHub pull requests.
Category: Workflow Tools
Last updated: 2026-10-16
Authors: Kevin Wu, Jackie Chen
Published: 2026-10-16

Lokalise describes itself as an [AI localization platform](https://lokalise.com/). Its Lokalise Expert workspace, built for apps and software, stores strings as keys in projects, imports and exports them as files for each platform, and translates them with AI, machine translation, or professional translators; a newer [Lokalise Vantage workspace](https://docs.lokalise.com/en/articles/14077324-what-is-lokalise-vantage) covers marketing and long-form content. Its repository workflow synchronizes those keys with your app. General Translation lets developers write readable copy directly in JSX and carry the message's structure into translation.

## What Lokalise does well

- **One key set for every platform.** A project holds [keys for web, iOS, and Android](https://docs.lokalise.com/en/articles/1400489-keys-and-platforms) and exports each platform's file format.
- **AI with context.** [Standard AI/MT](https://docs.lokalise.com/en/articles/11776521-what-is-standard-ai-mt-and-pro-ai) uses Google Translate and DeepL. Pro AI adds model routing, glossaries, style guides, descriptions, and task context. [Custom AI Profiles](https://docs.lokalise.com/en/articles/11894216-ai-profiles) add retrieval from translation memory or existing translations on Advanced and Enterprise.
- **Design workflows.** Figma, Adobe XD, and Sketch plugins, [screenshots whose text is matched to keys automatically](https://docs.lokalise.com/en/articles/2045882-screenshots), and the LiveJS in-context editor for websites.
- **Translator tooling.** Tasks, review steps, automations, branching, and QA checks, with [glossary](https://docs.lokalise.com/en/articles/1400629-glossary) and translation memory from the Growth plan.
- **Professional translation.** Order from Lokalise's translators or Gengo inside a project; Lokalise says [mid-size projects are typically delivered within 24 hours](https://docs.lokalise.com/en/articles/2141000-professional-translation-services).
- **Mobile over-the-air updates.** [iOS, Android, and Flutter SDKs](https://developers.lokalise.com/docs/ota-sdk) update strings without an app release.
- **Security.** SOC 2 Type II, ISO 27001, and ISO 27017, with [data hosted in AWS's EU regions](https://lokalise.com/product/security/).

## What Lokalise still leaves to your engineers

With Lokalise, new copy reaches every language through a round trip:

1. Set up an i18n library and write or extract the keys and resource files it uses.
2. Send the base-language files to Lokalise with [`lokalise2 file upload`](https://github.com/lokalise/lokalise-cli-2-go), the GitHub app (on demand or automatically on push), or Lokalise's push GitHub Action.
3. Run AI translation, machine translation, or translator tasks for the target languages.
4. Bring the translations back by [triggering a download](https://docs.lokalise.com/en/articles/1684090-github), which opens a pull request from a new branch, or with the pull GitHub Action. Then merge, wire each new language into the app, and check every screen.

Pro AI uses the context assigned to those keys and projects; custom profiles can add examples from earlier translations. Engineers still connect the keys to the UI and keep the resource-file workflow aligned with code changes.

Lokalise's paid plans include unlimited translator/reviewer seats. Its [pricing](https://lokalise.com/pricing/) scales through processed words, AI usage, and advanced seats for managers, developers, and content creators, with additional capacity available.

## Lokalise vs. General Translation at a glance

| Feature | Lokalise | General Translation |
| --- | --- | --- |
| Where strings live | Keys in Lokalise projects, synced with your resource files | In your code inside [`<T>`](/docs/react/reference/components/t), or in the resource files you already have |
| How code connects | `lokalise2` CLI, GitHub app, or GitHub Actions | [`npx gt translate`](/docs/cli/reference/commands/translate) in your build, or [Locadex](/docs/platform/locadex/quickstart) pull requests |
| Who translates | Lokalise AI, machine translation, or professional translators | AI with context from your code, Glossary, and Custom Prompts, reviewed by your team in the Dashboard |
| Context for each string | Pro AI uses glossary, style guides, and descriptions; custom profiles add earlier translations; screenshots support review | JSX structure, variable placeholders, context notes, Glossary, and Custom Prompts |
| Pricing | Subscriptions with processed-word, AI, and advanced-seat capacity | [Usage-based, without seat charges](https://generaltranslation.com/pricing) |
| Native mobile apps | Over-the-air SDKs for iOS, Android, and Flutter | CLI translation of iOS and Android string files for app releases |

## Why teams choose General Translation over Lokalise

For a team iterating on app screens, General Translation keeps the source copy beside the UI that uses it. Wrap that content in [`<T>`](/docs/react/reference/components/t), then generate translations as part of development and release.

- **Faster.** Change the copy in a component and run [`npx gt translate`](/docs/cli/reference/commands/translate). General Translation extracts the marked content and generates the target translations. Put that command in CI to translate new copy for the release that introduces it, without creating a separate source key for each edit.
- **Cheaper to run.** General Translation has no seat charges for the developers and managers maintaining localization. Its [usage-based pricing](https://generaltranslation.com/pricing) lets the team grow without buying additional advanced seats. Inline authoring also removes the routine work of naming keys and moving new copy into source dictionaries.
- **Higher quality.** A [`<T>`](/docs/react/reference/components/t) block keeps a complete message together with its markup and variable placeholders. An upgrade prompt can carry its sentence, emphasis, and plan-name placeholder into translation as one unit. Add context notes for intent and your Glossary for product names; your team can [review the result in the Dashboard](/docs/platform/dashboard/guides/reviewing-translations).
- **Lower risk.** Start with the catalogs exported from Lokalise: import your reviewed translations into General Translation and keep the library and keys your app already uses. You can change how translations are generated without rewriting the UI. Adopting inline JSX is a separate step you can take one component at a time.

Ramp localizes its dashboard, landing page, and iOS app into 11+ locales with General Translation. (See [production deployments](https://generaltranslation.com/enterprise).)

## When Lokalise is the better fit

Choose Lokalise when designers and translators work from Figma or screenshots, when you want professional translation ordered inside the same tool, when native mobile apps need over-the-air updates, when you exchange [XLIFF or ARB files](https://docs.lokalise.com/en/collections/2909229-supported-file-formats), when you want an EU-hosted localization platform, or when marketing and long-form content belongs in the same platform through Lokalise Vantage.

## Moving from Lokalise to General Translation

Export your existing source and translated files from Lokalise in a [format the `gt` CLI supports](/docs/cli/reference/config#files), such as JSON or iOS strings. Point `gt.config.json` at them and run [`npx gt upload`](/docs/cli/reference/commands/upload) before [`npx gt translate`](/docs/cli/reference/commands/translate). You can start with translation generation while keeping the library and keys your app already uses.

Import terminology into a [Context Group](/docs/platform/dashboard/guides/defining-context-for-translations). If you later adopt inline JSX, follow the [library migration guide](/docs/react/guides/migrating-i18n-libraries). For the broader TMS comparison, see [Why use General Translation instead of a TMS?](/kb/general-translation-vs-tms).

## Is General Translation an alternative to Lokalise?

Yes, for web apps whose copy lives in code. Lokalise stores keys in projects that sync with your resource files. General Translation translates the content in your code as part of your build. Lokalise remains the better fit for design-led workflows and native mobile apps that need over-the-air updates.

## Key takeaways

- Lokalise suits shared keys across platforms, design-led review, and native mobile over-the-air updates.
- Lokalise's repository tools automate file exchange; Pro AI uses project context, with custom profiles for earlier translation examples.
- General Translation keeps app copy readable in JSX, translates complete messages with their structure, and brings localization changes into builds and pull requests.

## Related questions

- [Why use General Translation instead of a TMS (Smartling, Lokalise, Phrase, Crowdin, or Transifex)?](https://generaltranslation.com/en-US/kb/general-translation-vs-tms.mdx): A translation management system (TMS) such as Smartling, Lokalise, Phrase, Crowdin, or Transifex coordinates translators, but engineers still extract strings, send them out, wait for translations, and wire them back into the product. General Translation translates content in your code with its context, ships every language with each release, and runs on open-source libraries with no lock-in.
- [General Translation vs. Crowdin: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-crowdin.mdx): Choose General Translation to keep copy in your components and generate translations with your build. Crowdin manages translation projects around resource files, translators, and review workflows, which engineers connect to the app and maintain as the product changes. Crowdin remains a strong fit for open-source community translation and vendor-led programs.
- [General Translation vs. Phrase: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-phrase.mdx): General Translation is a strong Phrase Strings alternative when your app and documentation ship together. It generates translations from code and content files, applies shared terminology, and runs in your release workflow. Phrase combines software localization with a document-focused TMS, vendor management, and a broad choice of translation engines.
- [General Translation vs. Smartling: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-smartling.mdx): Choose General Translation when you want app translations generated from code as part of your release. Smartling combines a translation management system, AI and human services, and a website translation proxy. General Translation keeps copy in your components, carries its context into translation, and gives your team a Dashboard for review.
- [General Translation vs. Transifex: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-transifex.mdx): Choose General Translation to translate marked JSX with its structure and developer context, then bundle the results or serve them from its CDN. Transifex Native also keeps strings in code, but publishes them through its content delivery service. Transifex is a strong fit for teams using its translation partners, quality scores, or snippet-based website translation.

## Previous and next questions

- Previous question: [General Translation vs. Locize: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-locize.mdx)
- Next question: [General Translation vs. Mobility: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-mobility.mdx)

## Sitemap

See the [Knowledge Base sitemap](https://generaltranslation.com/kb/sitemap.md) for every article.