Everything you need for world-class localization

No more translation tasks in your backlog

Push code, translations sync automatically. PM won't bother you anymore.

Better i18n Documentation

Problems we solve

Stop wasting time on translation tasks that shouldn't be yours

Context Switching

No jumping between platforms and JSON files. Everything syncs automatically from your codebase.

Manual Syncing

Auto-sync on push, no export-import cycles. Push to main and translations are automatically updated.

Backlog Debt

AI handles the grunt work, you just approve. No more translation tickets piling up in your sprint.

Developer Pain Points

Real frustrations from the developer community — and how Better i18n solves them.

"YAML configuration hell — 200 lines of config just to add a new language"

Dev.to
Better i18n Solution

Zero-config setup. Run bunx better-i18n init and start translating in under 5 minutes.

"Switching context between code and translation platform kills my flow state"

Hacker News
Better i18n Solution

MCP tools and IDE integration let you manage translations without leaving your editor.

"Missing key errors only caught in production — our users see raw translation keys"

Dev.to
Better i18n Solution

Type-safe SDKs catch missing keys at build time. CLI validates keys before deployment.

5 Minutes, Not 5 Days

Ship i18n in 5 Minutes

One command to initialize. Type-safe keys generated automatically. Deploy translations to a global CDN — no rebuild needed.

  • Auto-detects your framework and configures the SDK
  • Generates TypeScript types for all translation keys
  • Deploys translations to 300+ edge locations instantly
terminal

# Initialize Better i18n in your project

$ bunx better-i18n init

→ Detected: React + TanStack Router

→ Installing @better-i18n/use-intl...

→ Generated i18n.ts config + types

✓ Ready! Run bun dev to start translating.

Why Developers Choose Better i18n

From configuration hell to shipping in minutes.

The Pain

YAML config hell — 200 lines of boilerplate just to add a language, broken keys discovered in production.

The Promise

Ship i18n in 5 minutes, not 5 days. Zero-config, type-safe, and instant CDN delivery.

The Proof

200+ API endpoints, CLI auto-fix, 6 framework SDKs, and build-time key validation.

How it works

From code to production in four simple steps

01

Connect Repository

Link your GitHub repo with one click

02

Keys Auto-Discovered

We scan your code and find all translation keys

03

Translate with AI

Context-aware translations respecting your glossary

04

Publish Automatically

Changes go live to CDN and GitHub instantly

Your i18n workflow, simplified

Ship features faster without the i18n overhead

  1. Add translation key to code
  2. Create JSON entry in source locale
  3. Copy key to all target locale files
  4. Email translator with context
  5. Wait for translations
  6. Import translated files
  7. Push to GitHub
  8. Done
5 stepshandled automatically

Better i18n watches your repo, detects new keys, and handles the rest.

AI Coding Assistants

Manage translations directly from your AI coding assistant. Use natural language to translate, search, and update your i18n files.

Natural Language Commands

Just ask 'translate this' or 'add key' directly in your editor.

Context-Aware Translation

Better AI understands your file structure and variable naming patterns.

Real-time Updates

Translations sync instantly without context switching.

mcp-config.json
1{
2 "mcpServers": {
3 "better-i18n": {
4 "command": "npx",
5 "args": ["@better-i18n/mcp"],
6 "env": {
7 "BETTER_I18N_API_KEY": "your-api-key"
8 }
9 }
10 }
11}

Discover

Explore More

Keep moving through product pages, framework guides, and high-intent localization content.