LocalePack

The problem: Every time I built a browser extension that needed to work globally, the same workflow wasted hours — manually copying messages.json into a translation tool, losing placeholders, reformatting output, and copy-pasting 50 files into the right _locales/ folder structure. The same story repeated with Next.js i18n files and i18next namespaces.

Full translation platforms (Crowdin, Lokalise, Phrase) solve this for large teams — but they require project setup, a subscription, and 20 minutes of configuration before you can do anything. For a solo developer or a small team shipping one extension, that overhead is pure friction.

What LocalePack does:

- Upload your messages.json, i18next namespace JSON, vue-i18n YAML, or Next.js locale file

- Choose up to 52 target languages

- Pay once (from $9.99) — no subscription, no recurring charges

- Download a ready-to-ship ZIP with the correct folder structure

Placeholder syntax (`$PLACEHOLDER$`, $1, {{variable}}, {name}, pipe plurals) is preserved exactly. The output is correct for Chrome, Firefox, Edge, Safari, and Opera — or drop-in ready for next-intl, react-i18next, and createI18n().

Payments via Stripe. No account required.

I'd love to hear: what localization format is most painful in your current workflow? Happy to answer anything in the comments. 🙏