Loading page content
Generate the locale file scaffolding an internationalization workflow needs: key structure, placeholder handling, and per-locale files ready to hand to translators.
Generate i18n translation file scaffolds from English JSON key-value pairs. Supports React-Intl, next-intl, i18next, and Vue-i18n. Outputs proper file structures with placeholder markers for each target language. Detects interpolation placeholders and warns about missing keys.
Paste English i18n JSON on the left to generate translation scaffolds...
The decision that determines whether an i18n setup survives is key naming. Keys derived from the English text break the moment the English changes; semantic keys like checkout.payment.declined_error survive rewording and tell a translator where the string appears, which is context they otherwise lack entirely.
The two things that break in translation are pluralization and interpolation. Languages have between one and six plural forms. English has two, Arabic has six, so any string with a count needs plural-form support rather than string concatenation. And word order changes between languages, which is why placeholders must be named rather than positional.