Dev
Git Tag Name Generator
Used by developers, writers, and creators worldwide.
A Git tag name generator produces semantic version tag names for releases, like v1.4.0 and v2.0.0-rc.1. Git tags mark release points in a repository's history, and following the semver convention — a leading v, then major, minor, and patch numbers, with optional pre-release suffixes — keeps your releases readable and tooling-friendly. This tool generates valid, conventionally formatted tags, including the occasional alpha, beta, or release candidate, so you can see the patterns or grab examples for documentation. Choose how many you want and copy them. It is ideal for examples in release documentation, testing version-parsing code, and learning the tagging convention. Real release tags should of course reflect your actual version sequence rather than random numbers, so use these as format examples rather than literal versions. The convention is the valuable part: a consistent v-prefixed semver tag makes your release history easy to scan and easy for tools to sort.
Loading usage…
Free forever — no account required
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Choose how many tag names you want.
- Click Generate to produce Git tags.
- Use them as format examples.
- Tag real releases with your real version.
Use Cases
- •Examples for release documentation
- •Testing version-tag parsing
- •Learning the Git tagging convention
- •Filling sample release data
- •Demoing a release workflow
Tips
- →Prefix tags with v by convention.
- →Use -rc, -beta for pre-releases.
- →Follow your real version sequence.
- →Keep tags consistent for tooling.
FAQ
how should i name a Git release tag
The common convention is a leading v followed by a semantic version — v1.4.0 — with optional pre-release suffixes like -beta.1 or -rc.1. This keeps tags readable and lets tooling sort and compare releases reliably.
what does -rc.1 mean in a tag
It marks a release candidate — a build that is potentially the final release, pending testing. Pre-release suffixes like alpha, beta, and rc signal that a version is not yet stable, and semver orders them before the final release.
should real tags use random numbers
No. Real release tags should follow your actual version sequence, bumping major, minor, or patch according to what changed. These generated tags are format examples for documentation and testing, not literal versions to use.