AI localization for Next.js apps
Upload your JSON translation file, pick target languages, pay once, and download ready-to-use locale files.
How it works
Three simple steps to localize your Next.js app. Translations run after payment—we queue jobs and generate the files in minutes.
Upload
Drop your JSON translation file (next-intl, react-i18next, or simple JSON). We detect the format automatically.
Select languages & see price
Choose from 52 languages. See transparent pricing based on your file size and complexity before you pay.
Download translations
Pay once via Stripe. We generate locale files preserving your nested structure, ICU messages, and placeholders.
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
next-intl, react-i18next, or flat JSON. 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 Next.js developers
Purpose-built for Next.js i18n translation files. Not a generic translation tool.
Multi-format support
Supports next-intl, react-i18next, i18next, and simple flat JSON. We auto-detect your format on upload.
ICU message safety
Preserves ICU plural/select syntax like {count, plural, one {# item} other {# items}} across all translations.
Nested JSON aware
Handles deeply nested JSON structures. Your namespace hierarchy is preserved exactly in the output files.
Ready-to-use output
Download translated JSON files per locale. Drop them into your messages/ or locales/ folder and ship.
Parallel processing
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 Next.js i18n works
Next.js apps using next-intl or react-i18next store translations in JSON files per locale. LocalePack generates all of them from your source file.
messages/ folder structure
messages/ ├── en.json ← source locale ├── de.json ├── fr.json ├── ja.json └── ... (52 locales)
next-intl usage
// messages/en.json
{
"HomePage": {
"title": "Welcome to our platform",
"description": "Build amazing apps",
"items": "{count, plural,
=0 {No items}
one {# item}
other {# items}}"
}
}
// In your component
const t = useTranslations('HomePage');
<h1>{t('title')}</h1>
<p>{t('items', { count: 5 })}</p>Runtime API
useTranslations()
Config file
i18n.ts
Placeholders
{variable}
Plurals
ICU format
Why not just use generic tools?
General-purpose translation tools don't understand Next.js i18n format, ICU messages, or nested JSON structures.
LocalePack | Manual translation | Generic TMS | |
|---|---|---|---|
| Setup time | 2 minutes | Hours per language | 30+ minutes |
| Cost transparency | |||
| Nested JSON support | |||
| ICU message safety | |||
| Speed (52 languages) | < 5 min | Weeks | Hours |
| Best for | Next.js apps | Small projects | Enterprise CMS |
Trusted by Next.js developers
“Saved me days of work. Uploaded my next-intl JSON, got back perfectly structured translations with ICU plurals intact.”
Alex R.
Full-stack developer, SaaS app
“Finally a tool that understands nested JSON and doesn't break my ICU messages. The output drops right into my messages/ folder.”
Lisa M.
Next.js developer
“Transparent pricing was the selling point. I knew exactly what I'd pay before uploading anything.”
Dev J.
Open source contributor
52
Locales supported
100%
ICU-safe output
JSON
Ready to ship
Ready to ship your Next.js app globally?
Pay once • Download locale files • Ship globally
Try LocalePack