Manual
Overview Getting Started Core concepts Quick Start Guide Create an account and sign in Projects Create and manage projects Project settings Languages Workflow and translation lock Translation Keys Key names and groups ICU messages and placeholders Translating The translation editor Keyboard shortcuts Machine translation Review & Reports Review workflow Reports Branches & Merging Branch workflows: create, merge, and delete The Branches page Tags Translation Memory How translation memory works Glossary The glossary Import & Export Import and export files File formats Integrations GitHub GitLab Slack, Mattermost and Microsoft Teams Repository and API keys Tags from Git tags Webhooks Teams & Access Roles and permissions Teams Inviting people Project access Account & Organization Account settings Organization settings Billing & Plans Plans and limits
CLI
Overview Installation Set up a project Configuration File formats Use the CLI in CI Commands ct push ct pull ct status ct translate ct check ct merge ct tag ct init ct snippet
API
Overview Introduction Authentication Languages and time zones Rate limiting Errors Endpoints Authentication routes Account Organisation Teams Projects Project languages Project members and teams Project webhooks Project API keys Branches Tags Keys Translations and review CLI and CI Translation memory Glossary GitHub GitLab Repository link Guides Pull translations for your build MCP server for AI agents
Log in Get started free
Branches & Merging

Tags

Keep the translations of a release as a fixed snapshot of a branch.

2 min read ยท Updated October 2026

A tag is a named snapshot of a branch: its keys, source texts and translations exactly as they were when you made the tag. Unlike a branch, a tag never changes. Use one to keep the translations that shipped with a release, for example v1.4.0, so a build or a hotfix of that release can always get the same texts.

Create a tag #

  1. Open Branches in the project navigation. Each project has a Tags list under its branches.
  2. Choose New tag.
  3. Enter a Tag name. Letters, numbers, ., _, - and / are allowed, starting with a letter or number, at most 60 characters. A name can be used once per project.
  4. Pick the Branch to take the snapshot from (main by default) and choose Create tag.

Each tag in the list shows the branch it came from, how many keys it holds, the percentage of key and language combinations that were published at that moment, and who made it and when.

You need the manager role in the project to create or delete a tag. Creating a tag also works with an API key that has the keys:write scope, so a release pipeline can make one with ct tag create.

What a tag keeps #

  • The tag keeps the keys, source texts and translations of the branch, with their status. Notes, links and screenshots are not part of it.
  • A tag stays when the branch it came from is merged or deleted.
  • Tags don’t count towards the key limit of your plan.

Get the translations of a tag #

Run ct pull --tag v1.4.0 with the CLI, or pass tag when you pull through the API. See Pull translations. Whether a translation counts as published follows the review setting of the project at the time you pull.

Delete a tag #

Open the menu of the tag and choose Delete tag. The branch it was taken from is not affected.

Webhooks #

Creating a tag sends the tag.created event and deleting one sends tag.deleted. See Webhooks.