How do I use Localazy CLI with Branching?

Branching in Localazy lets you maintain separate translation states for different versions of your software — for example, a feature under active development, a stable release, or a white-labeled variant. Each branch is a copy of the main project, including its glossary, screenshots, and contributor permissions. From the CLI, you create and switch between branches using the --branch flag, which can be added to upload, download, cdn, and tag commands. This means your pipeline for a feature branch uploads strings to that branch’s translation state without affecting main.

# Create a new branch from main
localazy branch create main feature/payments

# Upload source strings to the feature branch
localazy upload --branch feature/payments

# Download translations for the feature branch
localazy download --branch feature/payments

When the feature is ready to ship, you merge it back. If there are conflicts, such as the same key being edited in both branches, the CLI surfaces them through localazy branch conflicts, and you can handle them manually or apply an automatic resolution strategy.

One thing to highlight about pricing: each branch counts against your source key limit, but Localazy only counts the “affected” keys inside the branch, not a full copy of every key.

This workflow maps well to how most teams already use Git. Your Localazy branching structure can mirror your code branches, keeping translation states in sync with development without translators ever needing to know which branch they’re working on — you control that at the CI level.