Skip to main content
The all-in-one Hyperlocalise localization CLI translates application resources, translation catalogs, documentation, and subtitles. Choose your source format below for a runnable example, configuration, and format-specific limitations.

​
How file detection works

The CLI selects a parser from the file extension. Android XML also requires an Android resource path. You do not need to declare a format for each bucket. Use matching source and target formats unless a workflow explicitly documents a conversion. File support describes local translation with run. Platform uploads, TMS entry sync, and provider-specific file commands have their own contracts; check the relevant integration guide before syncing.

​
Before you translate

  1. Install the CLI and configure provider credentials.
  2. Choose a format below and map its source and target paths in i18n.yml.
  3. Preview with hyperlocalise run --dry-run, then generate with hyperlocalise run.
  4. Review the output diff and run translation checks.
Writers may reuse an existing target as a template when it is compatible with the source. Otherwise they use the source template. Preservation guarantees apply to the selected template; each guide describes format-specific exceptions. For text, CSV, or JSON printed by CLI commands, see Command output.

​
Choose a format

​
Application resources

​
Translation exchange

​
Content and documentation

​
Subtitles and captions

​
Are placeholders, plurals, and comments preserved?

Behavior depends on the parser and selected source or target template. For example, ARB keeps message metadata, SRT retains timestamps, and JSONC writeback does not retain comments. Read each format’s limitations and run translation checks. Use the ICU and placeholder guide for validation failures. Review plural variants in the consuming application.

​
Can I convert between localization formats?

Use matching source and target formats unless a workflow explicitly documents a conversion. Supporting two parsers does not establish lossless conversion between them: context, plural forms, comments, and metadata can differ.

​
Do all formats work with every TMS and Platform?

Local translation, provider file commands, TMS entry sync, and Platform uploads have separate support boundaries. Shared TMS entry sync currently requires flat JSON; provider file commands follow the provider’s import/export contract. Consult TMS integrations or Platform file formats for the destination you use.

App translations

Translate JSON localization files with Hyperlocalise

Translate nested JSON messages while preserving keys and placeholders.

Translate JSONC localization files with Hyperlocalise

Translate JSON with comments and understand canonical JSON writeback.

Translate YAML localization files with Hyperlocalise

Configure YAML locale files, string values, and nested message paths.

Translate JavaScript and TypeScript locale files with Hyperlocalise

Translate static JavaScript and TypeScript locale modules without executing code.

Translate FormatJS and React Intl catalogs with Hyperlocalise

Translate React Intl catalogs with message descriptions and ICU arguments.

Translate Flutter ARB files with Hyperlocalise

Translate Flutter resource bundles while retaining message metadata.

Translate PHP localization files with Hyperlocalise

Translate static PHP locale arrays used by Laravel and other applications.

Translate Fluent localization files with Hyperlocalise

Translate Fluent messages and attributes, with explicit limits on terms.

Translate CSV localization files with Hyperlocalise

Translate key-value CSV files and locale-column tables.

Mobile

Translate Android XML string resources with Hyperlocalise

Translate Android string resources and plural entries in resource directories.

Translate Apple .strings files with Hyperlocalise

Translate Apple strings files while retaining comments and printf placeholders.

Translate Apple .stringsdict files with Hyperlocalise

Translate Apple plural dictionaries while preserving substitution metadata.

Translate Apple String Catalogs with Hyperlocalise

Translate Xcode string catalogs, plural variants, and device-specific messages.

Content

Translate Markdown files with Hyperlocalise

Translate Markdown prose while preserving frontmatter, code, and links.

Translate MDX files with Hyperlocalise

Translate MDX prose while preserving component structure and expressions.

Translate HTML files with Hyperlocalise

Translate visible HTML text while protecting inline markup.

Translate Liquid template files with Hyperlocalise

Translate hardcoded Liquid template text while preserving dynamic expressions.

Interchange

Translate XLIFF files with Hyperlocalise

Translate XLIFF 1.2 and 2.x files with documented target and segment behavior.

Translate gettext PO files with Hyperlocalise

Translate gettext PO messages and understand context and plural limitations.

Translate XML localization files with Hyperlocalise

Translate text-only XML resources with keyed or nested messages.

Translate .NET RESX resource files with Hyperlocalise

Translate text resources in .NET RESX files while preserving XML metadata.

Translate Java .properties files with Hyperlocalise

Translate Java resource bundles with escaped values and comment context.

Subtitles

Translate SRT subtitle files with Hyperlocalise

Translate SubRip cue text while preserving subtitle numbers and timing.

Translate WebVTT subtitle files with Hyperlocalise

Translate WebVTT captions while retaining cue settings and metadata blocks.