LangSync · AI localization

Ship in every language. Let AI do the translating

Manage all your translation strings in one place. AI translates them with your glossary and your own prompt, so brand names and tone stay right in every language. Then pull them into your repo as i18n JSON.

Pay per string, AI included100+ languagesGlossary & custom promptsi18n JSON via CLI and APIYour content never trains AIFree tier
AI translation

Translate your entire product in minutes

Add your terms, pick target languages and let the AI translate everything with your glossary and your namespace's prompt. Every AI translation stays labeled until someone edits it. Edit what you want, then ship.

  • Fill every missing translation in one click
  • Glossary-aware: brand names stay, product terms use your translations
  • A default prompt per namespace for tone, formality and domain
Try LangSync free
Glossary

Consistent terminology, every language, every time

Define your brand terms, technical vocabulary and domain language once, for your whole organization. The glossary goes into every AI translation, so terminology stays consistent across languages and teammates.

  • Part of speech on every term, so translations read naturally
  • Mark a term "don't translate" to keep a brand name as it is
  • Included in every AI translation automatically
Try LangSync free
API & export

From dashboard to production on every build

Pull translations as i18n JSON files with one CLI command, or read them from the REST API with an API key. Add it to your CI so every deploy ships the latest translations, with no manual export and no stale strings.

  • One flat JSON file per language: drop it into any frontend framework
  • REST API with API key authentication
  • Run nrc langsync pull in any CI pipeline
See API docs
CLI

Translations from your terminal

The norcube CLI keeps your local i18n JSON files in sync with the LangSync dashboard, fills the gaps with AI and writes the result back. One command per repo, one install for the whole team. No more copy-pasting between your editor and a web app.

  • Two-way sync with one command
  • Write in your language, AI translates the rest
  • An interrupted sync picks up where it stopped
Read the CLI guide

Built for teams that ship products globally

Product teams · Startups

SaaS products

Manage all your UI strings in namespaces, translate with AI, and pull the latest translations into your build through the API. Ship new languages in hours, not weeks.

namespace: checkout-app342 terms
en-US
100%
es-ES
97%
de-DE
91%
ja-JP
84%
pt-BR
72%
Agencies · Freelancers

Agencies & multi-client

One namespace per client project, each with its own languages, terms and progress. Manage dozens of localization projects from one account.

organization4 projects
acme-webapp6 langs100%
globex-mobile4 langs88%
initech-docs3 langs94%
umbrella-store8 langs76%
Growth · Localization leads

Global expansion

Entering a new market? Add target languages, let AI translate your entire product, review with native speakers, and launch in days, not months.

iOS · Android · React Native

Mobile apps

Manage all your mobile app strings in one place. Export as JSON through the API and integrate into your build pipeline. Ship localized updates without manual file wrangling.

Online stores · Marketplaces

E-commerce & marketplaces

Translate product descriptions, checkout flows, and transactional emails across all your target markets. Glossaries keep brand and product names consistent.

Maintainers · Contributors

Open source projects

Manage community translations with namespace-level access control. Contributors work on their language, you keep full oversight. Export as i18n JSON for any framework.

contributorsi18n
@maria_eses-ES
@kenji_jpja-JP
@pierre_frfr-FR
@alex_dede-DE—

Everything you need to ship in every language you support

Namespace-based projects

Organize translations into isolated namespaces: one per app, module or client. Each namespace tracks its own languages, terms, and translation progress.

Namespace-based projects

Organize translations into isolated namespaces: one per app, module or client. Each namespace tracks its own languages, terms, and translation progress.

Namespaces are isolated translation workspaces. Each has its own default language, set of target languages, terms, and progress tracking. Use them to separate translations by app, feature module, or client project. Progress percentages update in real time as translations are added.

Bulk import & auto-translate

Import thousands of terms from CSV at once. Map columns to fields, choose whether to overwrite existing terms, and optionally auto-translate everything during import.

Bulk import & auto-translate

Import thousands of terms from CSV at once. Map columns to fields, choose whether to overwrite existing terms, and optionally auto-translate everything during import.

Upload a CSV file and LangSync validates it before processing. Map columns to term keys, context and translations. Choose whether to overwrite existing terms or skip duplicates. Turn on auto-translate and AI fills in the missing translations during the import, using the namespace prompt. The whole import runs in the background with status tracking.

Custom translation prompts

Control how AI translates: formal or casual, technical or friendly. Save prompts and set one as the default for a namespace.

Custom translation prompts

Control how AI translates: formal or casual, technical or friendly. Save prompts and set one as the default for a namespace.

Write prompts that shape the AI output: tone of voice, formality, domain-specific instructions or anything else. Prompts can be private or shared with your organization. A shared prompt can be a namespace default, used by every automatic translation there: translate missing, auto-translate on import and CLI sync. You can also pick a prompt for a single translation.

100+ languages

Standard IETF BCP 47 locales, including regional variants like en-US, pt-BR and zh-TW. Add your own custom languages per organization.

POEditor migration

Bring your POEditor projects over in a few clicks: paste your API token, pick the projects, done. Terms, languages and translations move across automatically.

Team collaboration

Manage namespace-level access with roles and permissions. Invite contributors for specific languages. API keys for third-party integrations.

Pay for strings. Nothing else

We built LangSync the way we'd want a localization tool to work.

Empty translations are free

You pay for your keys and the translations that have content. An empty translation never counts toward your usage.

AI translation is included

You pay for the strings you store, not for AI words or machine-translation credits. Invite your whole team too: there are no seat fees.

Your content never trains AI

We don't train models on your strings, and OpenAI, which runs the AI translation, doesn't use API data for training.

How we handle your data

No vendor lock-in

Pull everything with the CLI or the API at any time. Your translations are yours. Cancel and take your data with you.

The comparison

Localization platforms weren't built for developers. LangSync is

The established TMS platforms price for enterprise procurement: seat classes, tier gates, sales calls. LangSync bills one thing: the strings you store.

What you pay3

Getting started

LangSyncFirst 1,000 strings free, no credit card, every feature included.
Established TMSPaid plans start around $144/month (Lokalise Explorer) and key features only unlock at $999/month or above.

Seats

LangSyncNo per-seat pricing. Unlimited collaborators on every plan.
Established TMSAdmin and advanced seats are paid and capped per tier, so adding a teammate can mean upgrading the whole plan.

Talking to sales

LangSyncNever required. Everything is self-serve, including the biggest volume tiers.
Established TMSTop tiers and features like SAML SSO and audit logs are sales-gated: demo call first, custom quote after.
What you get2

AI translation

LangSyncLLM translation with your glossary and custom prompts, on every plan.
Established TMSAI words are metered separately and premium AI features sit in higher tiers.

Where your data lives

LangSyncStored in AWS Frankfurt (eu-central-1), on every plan. Text you translate goes to OpenAI under SCCs and is never used for training.
Established TMSEU hosting is common, but the specific region is rarely published and residency can be tier-dependent.
SectionFeatureLangSyncEstablished TMS
Getting startedFirst 1,000 strings free, no credit card, every feature included.Paid plans start around $144/month (Lokalise Explorer) and key features only unlock at $999/month or above.
SeatsNo per-seat pricing. Unlimited collaborators on every plan.Admin and advanced seats are paid and capped per tier, so adding a teammate can mean upgrading the whole plan.
Talking to salesNever required. Everything is self-serve, including the biggest volume tiers.Top tiers and features like SAML SSO and audit logs are sales-gated: demo call first, custom quote after.
AI translationLLM translation with your glossary and custom prompts, on every plan.AI words are metered separately and premium AI features sit in higher tiers.
Where your data livesStored in AWS Frankfurt (eu-central-1), on every plan. Text you translate goes to OpenAI under SCCs and is never used for training.EU hosting is common, but the specific region is rarely published and residency can be tier-dependent.

Verified July 10, 2026 against the public sources listed with this comparison. Spot an inaccuracy? Email [email protected] and we'll update it within two business days.

Head-to-head detail, including where each tool wins: POEditor, Lokalise, Crowdin, Phrase, and Tolgee.

Pay per string. AI translation included

Your first 1,000 strings are free, forever. Above that you pay per 1,000 strings, AI translation included, and the price drops as you grow: 10,000 strings cost $11.25 a month and 100,000 cost $91.25. POEditor's matching plans cost $60 and $260 (comparison, checked October 28, 2026). No seat fees.

Free tier: 1,000 strings

A "string" is one term key plus each of its translations. For example, one term with its source text translated into 5 languages = 7 strings (1 key + the source text + 5 translations). Empty translations don't count. Pricing is based on the total across all namespaces.

String storage : Per-string monthly storage. Volume discounts applied automatically.
First 1,000 Free
1,001 – 10,000 $1.25 / 1K strings
10,001 – 50,000 $1.00 / 1K strings
50,001 – 150,000 $0.80 / 1K strings
150,001 – 500,000 $0.65 / 1K strings
500,001 – 1,000,000 $0.55 / 1K strings
1,000,001 – 2,500,000 $0.50 / 1K strings
Over 2,500,000 $0.45 / 1K strings

Estimate your monthly cost

Set your keys and languages. The estimate uses the same graduated brackets as your invoice, bracket by bracket.

Translation keys
Target languages plus your source language
Translated share of keys filled per language
  • You pay for stored strings: each key, its source text and every filled translation. Empty translations are free.
  • AI translation is included. There's no separate AI meter and no per-seat fee.
  • Billed monthly on your average string count. Glossary entries aren't part of this estimate.
Estimated monthly cost

Estimated monthly cost $31.25

$1.042 per 1,000 strings on average
Billable strings 30,000
3,000 keys + 3,000 source texts + 3,000 × 8 languages
Price by bracket
StringsRate / 1KIn bracketCost
First 1K Free1,000$0.00
1K to 10K $1.259,000$11.25
10K to 50K $1.0020,000$20.00
50K to 150K $0.800$0.00
150K to 500K $0.650$0.00
500K to 1M $0.550$0.00
1M to 2.5M $0.500$0.00
Over 2.5M $0.450$0.00
Total per month$31.25
Start free
First 1,000 strings free every month. No credit card.

Questions, answered

Quick answers to what teams ask us most about LangSync. Need something else? Email [email protected].

Which languages does LangSync support?
LangSync comes with a shared list of 100+ standard locales, including regional variants like pt-BR and zh-TW. If you need something else, such as a dialect or a pseudo-locale, add it as a custom language for your organization.
Can I bring my own glossary?
Yes. Your organization's glossary holds source terms, their translation per language, a part of speech and an optional don't-translate flag. The AI uses it on every translation, so brand terminology stays consistent across your product. LangSync has no separate translation memory.
How does LangSync handle context for translations?
You write a prompt in plain language: tone, audience, formality, product rules, anything the AI should know. Set a shared prompt as a namespace's default and every automatic translation there uses it, together with the source text and your glossary. Prompts can be private or shared with your organization.
How do I move translations in and out of LangSync?
Import existing translations from a CSV file and, if you want, auto-translate everything during the import, so a single upload bootstraps the whole product. To get them out, the norcube CLI keeps your local i18n JSON files in sync with the dashboard, and the REST API returns each language's translations as key and value pairs.
Do you store or train on our content?
We store your strings so you can edit and re-export them; that's the product. Your content never trains AI models: we don't train models on it, and OpenAI, which runs the AI translation, doesn't use API data for training. OpenAI may keep requests for up to 30 days to monitor abuse. Everything is encrypted in transit and at rest and stored in AWS Frankfurt, and text sent for AI translation goes to OpenAI under Standard Contractual Clauses.
How does pricing work?
There's a free tier, so you can start without a credit card. Above it, you pay per 1,000 strings (keys plus filled translations), and the price drops at higher volumes. See the pricing table above for the full schedule.

Translate your first project in under five minutes

Five steps, the last two for shipping to production. No SDK install, no schema migration, no language enum updates. Just a glossary, a prompt and JSON.

About 5 min
  1. Create a namespace

    A namespace is one isolated translation workspace: one per app, module or client project. Pick a source language and the target languages you want to ship in.

  2. Add your terms

    Type them in, paste them, or bulk-import a CSV file. Imports can auto-translate every missing language at once, so a single upload bootstraps the whole product.

  3. Define glossary entries (optional, recommended)

    Lock down brand names, technical vocabulary and anything where a literal translation breaks meaning. The glossary goes into every AI translation, so terminology stays consistent across languages and teammates.

  4. Translate

    Fill every missing translation with AI in one click, or edit translations by hand in the dashboard. If the namespace has a default prompt (tone, audience, formality), the AI follows it. AI translations stay labeled until someone edits them.

  5. Pull your translations

    Run nrc langsync pull at build time to write one i18n JSON file per language, or create an API key in the dashboard and read translations from the REST API at runtime.

Start translating in 60 seconds

Free tier included. No credit card required. Add your first terms and let AI do the rest.

  • Free tier
  • No credit card
  • AI included
  • Never trains AI
// tick. tick. tick.
0 ticks since founding
Coming soon

Join the PromptHub waitlist

PromptHub is in active development. Leave your email and we'll invite you as soon as it opens, with a free tier and no credit card.

One email when access opens. No newsletter, no spam.