AI localization for Vue.js apps
Upload your vue-i18n JSON or YAML, pick target languages, pay once, and download ready-to-use locale files.
How it works
Three simple steps to localize your Vue.js project. Translations run after payment—we queue jobs and generate locale files in minutes.
Upload locale file
Drop your vue-i18n JSON or YAML file (e.g. locales/en.json). We detect pipe plurals and {placeholder} tokens automatically.
Select languages
Choose from 52 languages. See transparent pricing based on your file size and complexity before you pay.
Download
Pay once via Stripe. We return locale files with pipe-separated plurals and {variable} placeholders preserved.
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 or YAML here
or click to browse
vue-i18n locale files (JSON or YAML). 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 vue-i18n developers
Purpose-built for vue-i18n pipe plurals, {placeholder} tokens, and nested message objects—not a generic translation tool.
Pipe plural handling
Handles vue-i18n pipe-separated plurals like "car | cars" and "no items | one item | {n} items" correctly per target language.
{placeholder} safety
Preserves vue-i18n interpolation tokens like {name}, {count}, and named formatting exactly—no broken strings after translation.
JSON & YAML support
Upload either JSON or YAML locale files. We detect the format and return translations in the same format you uploaded.
Ready output
Download locale files ready for vue-i18n's createI18n()—same structure, translated values, drop into your project.
Parallel translation
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 vue-i18n locale files fit together
vue-i18n projects keep locale messages in JSON or YAML files under locales/. LocalePack generates the same structure for every language you pick.
locales/ folder structure
locales/ ├── en.json ← source locale ├── de.json ├── fr.json ├── ja.json └── ... (52 locales)
$t() usage in templates
// locales/en.json
{
"greeting": "Hello {name}",
"items": "no items | one item
| {n} items"
}
// In your Vue component
<template>
{{ $t('greeting', { name: 'Ada' }) }}
{{ $t('items', 5) }}
</template>Template API
$t()
Config
createI18n()
Placeholders
{variable}
Plurals
pipe syntax
Why not just use generic tools?
General-purpose translation tools often break vue-i18n pipe plurals, {placeholder} tokens, and nested message structures.
LocalePack | Manual translation | Generic TMS | |
|---|---|---|---|
| Setup time | 2 minutes | Hours per language | 30+ minutes |
| Cost transparency | |||
| Nested JSON/YAML support | |||
| {placeholder} & plural safety | |||
| Speed (52 languages) | < 5 min | Weeks | Hours |
| Best for | Vue.js & Nuxt apps | Small projects | Enterprise CMS |
Trusted by Vue.js developers
“Our Vue app went from English-only to 12 languages in one afternoon. Pipe plurals and {name} placeholders came back intact.”
Marco S.
Full-stack developer, Vue SPA
“Finally a tool that understands vue-i18n format. The output dropped straight into our locales/ folder—no manual fixing.”
Claire D.
Frontend engineer, Nuxt app
“Transparent pricing sold me. I saw the estimate before uploading a single locale file.”
Jin K.
Open source contributor
52
Locales supported
100%
Placeholder & plural-safe
ZIP
Ready output
Ready to ship your Vue.js app globally?
Pay once • Download locale files • Ship globally
Try LocalePack