A calmer place to localize your product. Bring source strings, translators, AI, QA, file updates and delivery into one beautifully focused workspace.
Welcome back, {FIRST_NAME}!
Bon retour, {FIRST_NAME} !
Your balance is {BALANCE} {CURRENCY_NAME}.
Votre solde est de {BALANCE} {CURRENCY_NAME}.
Less copy-pasting. Less context switching. Less shipping the wrong string. Bring every contributor into one understandable workflow.
Compare files before applying anything. See new, changed, unchanged and unmatched keys. Keep history and skip work that's already done.
checkout.confirmAddedaccount.balanceNeeds reviewnav.settingsPreservedSource and target messages side by side. Edit exactly where you read, with autosave and a view across all languages.
300 rows per page by default · up to 1,000Use machine providers or AI translation where configured. Translation memory helps avoid repeating previously completed work.
Usage-based credits · optional AI planCatch missing and broken placeholders, unbalanced braces and configured terminology issues before text reaches production.
Free checks · no AI tokens requiredInvite contributors by email, assign target languages and protect source editing and approvals with role-based permissions.
Owners control the sourceWork through API tokens, incremental sync, background jobs and a change feed that connected applications can poll.
Documented REST API · JSON responsesA workflow designed for how software actually changes, not how spreadsheets were meant to work.
Create a project and upload your existing localization files. Preview additions and edits before applying.
Set target locales, invite translators and assign the languages each person can edit.
Work by hand, use connected providers, then catch placeholder problems with free QA.
Export updated locale files or let integrated applications retrieve approved translations and changes.
Release after release, your strings evolve. LangKit compares imports against what's already saved, helping you avoid wiping translations or spending credits on unchanged text.
profile.greetingModifiedprofile.signoutNewLanguage work is collaborative. Invite human or community translators with email, limit their access to the locales they need and keep original text protected from accidental changes.
Localize from your editor or CI pipeline. Import and retrieve translations through APIs, without manual copy-and-paste.
Preview a source or translation update before applying it. No needless rewrites.
Queue missing/outdated translations via API and check job progress independently of your browser.
Read a cursor-based change feed or embed the published translation SDK in an integrated website.
# Preview localization changes in CI
curl -X POST \
https://langkit.xyz/api/v1/projects/42/sync \
-H "Authorization: Bearer $LANGKIT_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"locale": "fr",
"dry_run": true,
"strings": {
"home.title": "Bienvenue",
"home.cta": "Commencer"
}
}'Localization projects are rarely one format. LangKit handles common language-resource formats and gives you a consistent place to review them.
Advanced plural or rich-format round-trip fidelity varies by format. Test exports before using them in production.
Tokens like {CURRENCY_NAME} should stay intact across languages. LangKit checks common placeholders before translations are saved or returned by providers.
Balance: {CURRENCY_NAME}
TranslationSolde : {CURRENCY_NAME}
Balance: {CURRENCY_NAME}
TranslationSolde : {CURRENCY_NAM}
Free QA focuses on common placeholder and syntax errors. It does not replace full linguistic review.
Translate missing or outdated content with an AI workflow, preserve recognized placeholders, and keep every result ready for human review. AI Studio includes developer automation and a measured token budget.
AI requires an active paid subscription. Included tokens are measured from provider usage; purchased top-ups are separate.
Use the editor without paying for an AI plan. Upgrade when you want automated API workflows or an included AI token allowance.
For early projects and human translation.
Automate your multilingual release workflow.
Bring AI translation to your localization team.
Annual billing is prepaid: Developer API $204/year and AI Studio $690/year. Actual translation provider charges and available payment methods depend on configured services. Automated API limits count each project source key once for each configured language, including the source language.
Use scoped API tokens and team permissions to keep translation work organized. Only project owners can modify original source text; published website translations are restricted to approved content.
Project permissions and language assignments restrict editing.
Revisions and project activity help teams track updates.
Keep drafts out of publicly delivered translations.
Admins configure connected translation engines and credentials.
Technical guides, formats and real examples for teams shipping multilingual software.
Clear answers before you create a project.
Read API documentation ↗Yes. You can create projects, import/export supported files, edit translations and run free placeholder QA without an AI subscription. Automated API jobs have a free allowance.
The allowance is shared across projects you own. Each source key counts once for every configured language, including the source. For example, 250 source keys in English plus French, German and Spanish count as 1,000 combined key-language entries.
No. Incremental imports compare values first, preserve absent keys, and do not rewrite unchanged entries. Changed source text can invalidate an earlier approval so it can be reviewed.
Yes. You can invite translators and community contributors by email, then assign languages and permissions. Only the owner can edit the original source language.
Connected applications can retrieve translations through the API or use the approved website SDK. Your app must integrate with LangKit; merely uploading a file here cannot rewrite an unrelated application.
Yes. The workspace supports Light, Dark and System appearance modes, and authenticated preferences can follow your account.
Common formats include JSON, ARB, YAML, CSV, TSV, PO, Apple strings, Java properties, Android XML, XLIFF, RESX, Qt TS, INI and TOML. Exact round-trip behavior may differ for advanced constructs.
The platform supports Stripe subscriptions and optional NOWPayments token purchases when those gateways are configured and enabled by the platform operator. Disabled methods are not offered at checkout.
Bring your current strings. Invite your people. Build a workflow that stays useful as your product grows.