AstrologerAI: an AI astrology app localized into 52 languages
How the AstrologerAI app translated its entire experience into 52 languages with LocalePack — 6.3M tokens for $58.73 — to reach a worldwide audience in their own language.
Purpose-built for Edge extensions
AI localization for Edge extensions
Upload your source messages.json, pick target languages, pay once, and download a ready-to-ship _locales ZIP.
Placeholder-safe translations
Edge messages.json compliant
Transparent pricing
How it works
Three simple steps to localize your Edge extension. Translations run after payment—we queue jobs and generate the ZIP in minutes.
01
Upload
Drop your source messages.json file. We parse it instantly and validate the Edge extension format.
02
Select languages & see price
Choose from 52 languages. See transparent pricing based on your file size before you pay.
03
Download ZIP
Pay once via Stripe. We generate all _locales/{lang}/messages.json files and bundle them into a ZIP.
Live pricing demo
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
Languages selected3
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/ folder structure
_locales/
├── en/
│ └── messages.json ← default_locale
├── de/
│ └── messages.json
├── fr/
│ └── messages.json
└── ja/
└── messages.jsonmessages.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.
Edge is Chromium, so Chrome's rules apply
Edge extensions use the identical Chromium i18n format. That means the compatibility is total — and so are Chrome's constraints.
- Byte-identical file format
- Edge reads the same _locales/{locale}/messages.json structure as Chrome. A package that already works in Chrome works in Edge with no modification.
- The same locale-code rules carry over
- Because Edge inherits Chromium's locale resolution, the underscore convention (pt_BR, not pt-BR) and the supported-code list apply exactly as they do in Chrome.
- One ZIP, two stores
- The same LocalePack output can be submitted to both the Microsoft Edge Add-ons store and the Chrome Web Store without rebuilding the locale files.
- chrome.i18n, not edge.i18n
- There is no Edge-specific namespace. Extension code calls chrome.i18n.getMessage() exactly as it does on Chrome.
Because Edge inherits Chromium's behaviour, it also inherits the silent failure: an unsupported locale folder is ignored rather than reported.
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 |
Success Cases
Real projects that used LocalePack to reach a global audience in up to 52 languages.
DevToys.pro: 400% international traffic growth across 52 languages
How the DevToys.pro web app translated its entire UI into 52 languages with LocalePack — 5.8M tokens for $58.44 — and quadrupled its international organic traffic.
DevToys New Tab: a Chrome extension localized UI + store listing in 52 languages
How the DevToys New Tab Chrome extension localized both its in-extension UI and its Chrome Web Store listing into 52 languages to reach a global audience.
LocalePack localized itself into 52 languages — with LocalePack
We used our own tool to translate the entire LocalePack site into 52 languages — 2.9M tokens for $27.37 — so developers worldwide find us in their own language.
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.
Related developer guides
Deep dives on the formats, APIs and errors behind this page — written for developers, not translators.
Chrome extension i18n: _locales structure and default_locale
How to set up the _locales folder, what default_locale does in manifest.json, and how Chrome picks the right messages.json at runtime.
Localizing your Edge Add-ons listing
Why Partner Center shows only one listing language even when your package ships twenty, how __MSG_ manifest references drive language detection, and which listing fields Edge requires for every language versus just one.
chrome.i18n: the complete API reference
All four chrome.i18n methods with exact signatures and return types: which are synchronous, which return promises, what getMessage() returns when it fails, and how browser.i18n differs in Firefox and Safari.
Chrome extension locale codes: all 55
Every locale code Chrome accepts as a _locales folder name, with language and native names, the underscore-vs-hyphen trap that makes pt-BR silently ignored, and how Chrome picks a locale at runtime.
Validate messages.json before shipping
How to catch every class of messages.json error before your users do: JSON syntax, missing required fields, missing keys across locales, malformed placeholder syntax, and manifest key mismatches.