AI localization for Edge 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 Edge 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 Edge 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
Edge 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 Edge extension locale format. Not a generic translation tool.
Edge format aware
Built specifically for Edge 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 Edge extension i18n works
Microsoft Edge extensions use the identical Chromium i18n format — the same _locales/{locale}/messages.json structure as Chrome. If your extension already targets Chrome, the LocalePack output works for Edge without any modification.
_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"Edge is built on Chromium. Any _locales ZIP that works for Chrome will work for Edge as-is.
The Microsoft Edge Add-ons store reads _locales/ to display localized extension names and descriptions to users browsing the store in their language.
Why not just use generic tools?
General-purpose translation tools don't understand Edge extension format.
LocalePack | Manual translation | Generic TMS | |
|---|---|---|---|
| Setup time | 2 minutes | Hours per language | 30+ minutes |
| Cost transparency | |||
| Edge format safety | |||
| Placeholder protection | |||
| Speed (52 languages) | < 5 min | Weeks | Hours |
| Best for | Edge 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 Edge 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.