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
Commands

ct tag

Save a snapshot of a branch for a release, and list the snapshots.

1 min read ยท Updated October 2026

A tag is a named snapshot of the keys and translations of a branch, for example when you release. See Tags.

ct tag create #

SH 
ct tag create v1.4.0                       # a snapshot of main
ct tag create v1.4.0 --branch release/1.x

ct tag create takes the default branch unless you pass --branch, because a release job often runs on a Git tag, which has no branch. It fails with a clear message when the name is already used.

TEXT 
Created tag v1.4.0 from main: 128 keys, 97% published.

It needs an API key with the keys:write scope, made by a project manager. See Create a tag.

ct tag list #

SH 
ct tag list

Shows each tag with its branch, key count, how much was published, the date it was made and who made it. Deleting a tag is done in the web app. It needs the projects:read scope.

Use a tag #

Build an old version again with exactly the texts it shipped with:

SH 
ct pull --tag v1.4.0

See ct pull.