Question 1

Does any data leave my machine?

Accepted Answer

No. If you use the on-device engines (Apple Intelligence or local LLMs), no data ever leaves your computer. If you choose to use DeepL or OpenAI API, data is sent to their servers for translation only.

Question 2

Are API costs (DeepL/OpenAI) included in the subscription?

Accepted Answer

No. LocaleKit is a 'Bring Your Own Key' (BYOK) tool. We provide the automation platform, but if you choose to use 3rd-party engines like DeepL, OpenAI, or Claude, you will need to use your own API keys and pay those providers directly for their usage.

Question 3

Which frameworks do you support?

Accepted Answer

We support native iOS (Swift/Obj-C), Android (Kotlin/Java), Flutter, React/Web (JSON, YAML, PO), and backend files. We are constantly adding more formats.

Question 4

Do you support CI?

Accepted Answer

Yes! The MAX plan includes a CLI tool that runs in GitHub Actions, GitLab CI, Bitrise, and CircleCI to validate and translate strings automatically.

Question 5

Do I need English as base language?

Accepted Answer

Not necessarily, but it is recommended. You can configure any language as your source of truth in the workspace settings.

Question 6

Do you preserve ICU messages?

Accepted Answer

Absolutely. We have specialized parsers that detect ICU syntax ({count, plural, ...}) and protect it from being mangled by translation engines.

Question 7

How is the translation quality?

Accepted Answer

European languages are typically very good. Asian languages are accurate but can be too formal. This is why we provide a way to BYOK (Bring Your Own Key) with remote LLMs or DeepL, ensuring you can always choose the best engine for your specific needs.

	LocaleKit	DeepL (manual)	Google (manual)	In-house scripts
Multi-stack (iOS/Android/Flutter/Web) Native support for Xcode, Android Studio, Flutter, React, Vue, Angular, and more.				Depends
Auto-detects localization files Drop your project folder and LocaleKit identifies .xcstrings, .arb, strings.xml, JSON, and more.
Privacy-first, on-device translation Your code and strings never touch external servers when using local engines.
Protects placeholders / plurals Format strings like %@, {name}, {{count}}, and ICU plural rules are detected and locked.
Git & CI friendly Deterministic key ordering, consistent formatting, and CLI commands for GitHub Actions & GitLab CI.
No copy-paste Translations are written directly to your localization files — no spreadsheets, no manual transfers.
Single tool for whole org One app handles iOS, Android, Flutter, and Web projects — no separate tools per platform.
Bring Your Own Key (OpenAI, DeepL) Connect your OpenAI or DeepL API keys directly. You pay providers at their rate — we add zero markup.				Manual

	LocaleKit	DeepL (manual)	Google (manual)	In-house scripts
Multi-stack (iOS/Android/Flutter/Web) Native support for Xcode, Android Studio, Flutter, React, Vue, Angular, and more.				Depends
Auto-detects localization files Drop your project folder and LocaleKit identifies .xcstrings, .arb, strings.xml, JSON, and more.
Privacy-first, on-device translation Your code and strings never touch external servers when using local engines.
Protects placeholders / plurals Format strings like %@, {name}, {{count}}, and ICU plural rules are detected and locked.
Git & CI friendly Deterministic key ordering, consistent formatting, and CLI commands for GitHub Actions & GitLab CI.
No copy-paste Translations are written directly to your localization files — no spreadsheets, no manual transfers.
Single tool for whole org One app handles iOS, Android, Flutter, and Web projects — no separate tools per platform.
Bring Your Own Key (OpenAI, DeepL) Connect your OpenAI or DeepL API keys directly. You pay providers at their rate — we add zero markup.				Manual

All Features

Why LocaleKit?

Compare plans in detail

All Features

Why LocaleKit?

Compare plans in detail