No more translation tasks in your backlog
Push code, translations sync automatically. PM won't bother you anymore.
Manual today
- Add translation key to codeby hand
- Create JSON entry in source locale
- Copy key to all target locale filesonce per locale
- A new key slips through code review
- Email translator with contextdays of waiting
- Wait for translations
- Import translated files
- Resolve merge conflicts in locale files
- Push to GitHub
- Wait for the next deploy to ship the copyevery release
- Write the feature and use the key
- Keys Auto-Discoveredone command
- Translate with AI
- Review and approve in the editorin the editor
- Publish Automaticallyno deploy
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.toZero-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 NewsMCP 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.toType-safe SDKs catch missing keys at build time. CLI validates keys before deployment.
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
# 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.
YAML config hell — 200 lines of boilerplate just to add a language, broken keys discovered in production.
Ship i18n in 5 minutes, not 5 days. Zero-config, type-safe, and instant CDN delivery.
200+ API endpoints, CLI auto-fix, 6 framework SDKs, and build-time key validation.
Pipeline
How it works
From code to production in four simple steps
Your i18n workflow, simplified
Ship features faster without the i18n overhead
- Add translation key to code
- Create JSON entry in source locale
- Copy key to all target locale files
- Email translator with context
- Wait for translations
- Import translated files
- Push to GitHub
- Done
5 handled 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.
{
"mcpServers": {
"better-i18n": {
"command": "npx",
"args": ["@better-i18n/mcp"],
"env": {
"BETTER_I18N_API_KEY": "your-api-key"
}
}
}
}Developer Resources
Everything you need to get started