AI localization for i18next apps
Upload your namespace JSON files, pick target languages, pay once, and download a ready-to-use locales ZIP.
How it works
Three simple steps to localize your i18next project. Translations run after payment—we queue jobs and generate namespace files in minutes.
Upload namespace files
Drop your JSON namespaces (e.g. locales/en/common.json). We detect i18next structure and plural keys automatically.
Select languages
Choose from 52 languages. See transparent pricing based on your file size and complexity before you pay.
Download
Pay once via Stripe. We return a ZIP mirroring locales/{lang}/ with double-brace placeholders and _one/_other keys preserved.
Transparent pricing estimator
See exactly what you'll pay before uploading. Final quote is computed after upload based on file complexity and languages selected.
1. Upload file
Drop JSON file here
or click to browse
i18next namespace JSON (locales/**). Max 500KB.
2. Select languages
3 of 52 languages selected
3. Your estimate
Final price calculated after file upload on checkout page
One-time payment • No subscription
Built for i18next developers
Purpose-built for i18next JSON namespaces, double-brace placeholders, and plural keys—not a generic translation tool.
Namespace support
Keeps common.json, auth.json, and nested namespaces aligned across every target locale in your ZIP.
{{placeholder}} safety
Preserves i18next interpolation tokens like {{name}} and {{count}} exactly—no broken strings after translation.
Plural-key handling (_one/_other)
Handles i18next-style plural splits such as key_one and key_other so grammars stay correct per language.
Ready output (namespace ZIP)
Download a locales/ tree ready for i18next.init() or react-i18next—same paths, translated values.
Parallel translation
All languages are translated simultaneously. Most jobs complete in under 5 minutes.
One-time payment
No subscriptions, no monthly fees. Pay once per job, download forever.
How i18next JSON fits together
i18next projects often split strings by namespace under locales/{lang}/. LocalePack generates the same structure for every language you pick.
locales/ folder structure
locales/ ├── en/ │ ├── common.json ← source namespace │ └── auth.json ├── de/ │ ├── common.json │ └── auth.json ├── fr/ │ └── ... └── ... (52 locales)
i18next.t() usage
// locales/en/common.json
{
"welcome": "Hello {{name}}",
"items_one": "{{count}} item",
"items_other": "{{count}} items"
}
// After i18next.init({ ns: ['common'] })
i18next.t('common:welcome', { name: 'Ada' });
i18next.t('common:items', { count: 5 });Runtime API
t()
Config file
i18next.init()
Placeholders
{{variable}}
Plurals
_one/_other
Why not just use generic tools?
General-purpose translation tools often break i18next namespaces, double-brace placeholders, and _one/_other plural conventions.
LocalePack | Manual translation | Generic TMS | |
|---|---|---|---|
| Setup time | 2 minutes | Hours per language | 30+ minutes |
| Cost transparency | |||
| Namespace JSON support | |||
| {{placeholder}} & plural safety | |||
| Speed (52 languages) | < 5 min | Weeks | Hours |
| Best for | i18next & React apps | Small projects | Enterprise CMS |
Trusted by i18next developers
“Our locales/en folder went to 12 languages in one afternoon. {{variables}} and plural keys came back intact.”
Alex R.
Full-stack developer, SaaS app
“Finally a pipeline that respects namespaces. The ZIP drops straight into our repo—no manual merging.”
Lisa M.
Frontend engineer
“Transparent pricing sold me. I saw the estimate before uploading a single common.json.”
Dev J.
Open source contributor
52
Locales supported
100%
Mustache-style & plural-safe
ZIP
Namespace ZIP
Ready to ship your i18next app globally?
Pay once • Download namespace ZIP • Ship globally
Try LocalePack