AI localization for Chrome extensions
Upload your source messages.json, pick target languages, pay once, and download a ready-to-ship _locales ZIP.
How it works
Three simple steps to localize your Chrome extension. Translations run after payment—we queue jobs and generate the ZIP in minutes.
Upload
Drop your source messages.json file. We parse it instantly and validate the Chrome extension format.
Select languages & see price
Choose from 52 languages. See transparent pricing based on your file size before you pay.
Download ZIP
Pay once via Stripe. We generate all _locales/{lang}/messages.json files and bundle them into a ZIP.
Transparent pricing estimator
See exactly what you'll pay before uploading. Final quote is computed after upload based on string length and languages selected.
1. Upload file
Drop messages.json here
or click to browse
Chrome extension format only. Max 500KB.
2. Select languages
3 of 55 languages selected
3. Your estimate
Final price calculated after file upload on checkout page
One-time payment • No subscription
Built for developers
Purpose-built for Chrome extension locale format. Not a generic translation tool.
Chrome format aware
Built specifically for Chrome extension messages.json structure with message, description, and placeholders support.
Placeholder protection
Preserves $PLACEHOLDER$ syntax exactly as-is. Your variables stay intact across all languages.
Description context
We read your description fields and use them as context hints for more accurate AI translations.
ZIP export ready
Download a ZIP with correct _locales/{lang}/messages.json folder structure. Drop it into your extension.
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 Chrome extension i18n works
Chrome extensions declare "default_locale" in manifest.json to enable i18n. The browser then reads locale strings from _locales/{locale}/messages.json at runtime. Each key has a "message" field, an optional "description" for context, and optional "placeholders" for dynamic values — all of which LocalePack understands natively.
_locales/
├── en/
│ └── messages.json ← default_locale
├── de/
│ └── messages.json
├── fr/
│ └── messages.json
└── ja/
└── messages.json{
"appName": {
"message": "My Extension",
"description": "Extension name"
},
"greeting": {
"message": "Hello, $USER$!",
"placeholders": {
"user": { "content": "$1" }
}
}
}Runtime API
chrome.i18nExample call
chrome.i18n.getMessage("appName")Required in manifest
"default_locale"The Chrome Web Store automatically displays your extension name and description in the visitor's locale when _locales/ contains their language folder.
Why not just use generic tools?
General-purpose translation tools don't understand Chrome extension format.
LocalePack | Manual translation | Generic TMS | |
|---|---|---|---|
| Setup time | 2 minutes | Hours per language | 30+ minutes |
| Cost transparency | |||
| Chrome format safety | |||
| Placeholder protection | |||
| Speed (52 languages) | < 5 min | Weeks | Hours |
| Best for | Chrome extensions | Small projects | Enterprise web apps |
Trusted by extension developers
“Saved me hours of tedious work. Uploaded my messages.json, got back perfect translations in the exact format I needed.”
Sarah K.
Indie dev, AdBlock extension
“Finally a tool that understands Chrome extension format. No more fixing broken placeholders after translation.”
Marcus T.
Extension maintainer
“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%
Placeholder-safe output
ZIP
Ready to ship
Frequently asked questions
Everything you need to know about LocalePack.