Day 1
See the full workflow — the problem, three steps, team review, and sync — without legacy TMS onboarding.
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
1 prompt and
1 min to set up
Hour 1
page.tsx
<h1>
Welcome back
</h1>
<button>
Get started
</button>
i18.dev
hero.title
Welcome back
hero.cta
Get started
Hour 2
Welcome back
Get started
Complete order
Hour 3
Ship
Who this is for
Built for developers who ship, translators who refine, and localization teams who need speed without enterprise onboarding.
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.