Day 1
The only translation management system that extracts strings from your codebase, converts them to i18n-ready code, and syncs keys back — automatically.
No more grepping through files. No missed placeholders. No back-and-forth on missing keys. Paste one prompt, let your agent do the extraction, review translations in the dashboard, ship.
The problem
Sprint lost
Day 1
// page component
export function Page() {
return (<h1>"Welcome back"</h1>);
}
// page component
export function Page() {
return (<p>"Contact us"</p>);
}
// page component
export function Page() {
return (<button>"Place order"</button>);
}
47 files left…
Day 2–4
<<<<<<< HEAD
<h1>{t('home.title')}</h1>
=======
<h1>"Welcome back"</h1>
>>>>>>> feat/i18n-home
missed hardcoded string
Day 5–7
checkout.title
{amount}
Place order
I'm on the German site — checkout is completely broken.
Week 3
Shipped
Setting up project…
my-app/
├── i18n.config.ts
└── locales/
en · de · fr · es · jp
Ready for localization
Hour 1
Scan codebase, group namespaces, convert to t(), sync i18.dev, auto-translate.
Scanning codebase…
Grouping namespaces…
Welcome back
Get startedLive in 5 languages
Hour 2
EN · Get started
Los geht's
$ i18dev pull --confirmed
→ locales/de.json updated
staging ✓
Synced on every update
Hour 3
More outreach with new locales
Time
3 weeks→1 day
Cost
$$ saved
Shipped worldwide
Ship
Who this is for
Built for engineering teams shipping to multiple markets . The fastest way for a startup to go multilingual and keep moving.
Empower your team to manage localization without slowing down development.

Agent-ready product system
Simplified UI
Review namespaces, languages, strings, notes, and confirmation state after your coding agent extracts or updates copy.
Setup prompts
Choose your library, copy the setup prompt, and let your AI editor wire the safest project structure.
AI-editor CLI
Pull, push, validate, and inspect localization state from the terminal so agents work with real project context.
Context-aware translation
Enable every market your roadmap calls for, from your first few regions to a full global list. Notes, tone, namespace, and UI intent travel with each key so widening your audience never means diluting how the product reads.
100+ languages
Add every locale your product needs to serve the audience you want—one pipeline, no duplicate setup per market.
Automation API
Integrate extraction, translation, string sync, AI usage checks, and locale delivery into CI, scripts, internal tools, or your own admin panel.
Teams & versioning
Invite editors, review updates, track history, and keep release-ready translations separated from drafts and experiments.
Coming soon
Create translation branches for feature work, compare changes, merge confirmed copy, and avoid blocking one release on another.
Compare, merge, and ship copy without blocking parallel releases.
Why agents need i18.dev
Full localization
Internationalization (i18n) is the engineering work that prepares your app for multiple languages — locale files, keys, and t() wiring. Localization (l10n) is adapting the product for each market: copy, layout, currency, dates, and cultural tone.
Translation changes words. Localization adapts the product identity: copy, layout, images, dates, currency, legal requirements, payment methods, and cultural signals.
Get started
Works with Next.js, React, Vue, Angular, and Svelte. No migration needed.
locales confirmed and waiting for your next deploy.