Routara
LOCALIZATION · JSON / PRACTICAL GUIDE

Translate JSON values without breaking keys or nesting

A translated JSON file is useful only if your application can still load it. Keys, nesting, interpolation placeholders, and product names often need to remain unchanged while user-facing values change. Treat AI output as a draft and validate it before shipping.

01

Separate structure from copy

Identify user-facing string values and mark identifiers, placeholders, URLs, and keys that must remain stable. In the example, greeting and save_button may change; the keys and {name} placeholder must not.

{
  "greeting": "Hello, {name}!",
  "save_button": "Save changes",
  "help_url": "https://example.com/help"
}
02

Translate in Routara

Open the JSON translation tool, paste a small representative file, choose the target language, and ask it to preserve keys, nesting, placeholders, and URLs. Review a sample manually before processing a larger resource bundle.

03

Validate before deployment

Parse the output with your application’s JSON parser. Compare source and target key paths, confirm placeholders and URLs are identical, and check pluralization and tone in context. A syntactically valid file can still be a poor translation.

Before you ship

  • Same key paths and JSON types as the source.
  • No translated interpolation placeholders or URLs.
  • Human review for high-visibility strings and locale-specific phrasing.