Translate JSON localization files with Hyperlocalise

​

Source file

{
    "home": {
        "title": "Welcome",
        "greeting": "Hello, {name}!"
    }
}

​

Configure your files

locales:
    source: en-US
    targets:
        - es-ES

buckets:
    messages:
        files:
            - from: locales/en-US/messages.json
              to: locales/{{target}}/messages.json

llm:
    profiles:
        default:
            provider: openai
            model: gpt-5.2

​

Translate

hyperlocalise run --dry-run
hyperlocalise run

​

Behavior and limitations

• Nested objects use dotted keys such as home.title; arrays use indexed paths. Translation leaves must be strings.
• Numbers, booleans, and other non-string leaves are rejected. Keep application settings separate from locale messages.
• Output preserves the JSON data structure, but indentation and object ordering may change.
• Strict FormatJS catalogs are detected automatically: defaultMessage is translated and description supplies context. See FormatJS.

​

Next steps

• Check translations before committing generated files.
• Local translation workflow explains repeat runs.
• Browse all file formats.

​

Related formats

• JSONC localization
• FormatJS and React Intl catalogs
• YAML localization