Skip to main content
For a shared team workflow, start with Hyperlocalise Platform. Keep source files and delivery in your repository while your team manages translation and review in Platform. Install the CLI, then connect your project. Local translation and existing TMS integrations are also available. Each path uses its own configuration and credentials.

​
Use Hyperlocalise Platform

Use hyperlocalise sync push to upload sources and hyperlocalise sync pull to retrieve project translations. Generation and human approval happen separately in Platform. A successful push does not mean translations were generated. Follow Connect the CLI for the project ID, credentials, and a complete configuration.

​
Translate locally

Use hyperlocalise run --dry-run to preview, hyperlocalise run to generate, and hyperlocalise check to check the result. Review the target diff before committing it with the lockfile. See Translate changed strings for later updates.

​
Keep your existing TMS

Use hyperlocalise crowdin, lokalise, phrase, or smartling for the documented provider file workflows. Each has its own configuration and supported operations. The separate experimental entry-sync workflow uses sync with storage.adapter and flat JSON translation entries. It is not interchangeable with provider file commands. If a hyperlocalise block is also present, sync chooses Platform.

​
Next

Follow the guide for your chosen path with one file and one locale. Verify the output before adding CI automation.