What is semantic versioning?

Semantic versioning (semver) is a versioning scheme where a version number takes the form MAJOR.MINOR.PATCH. MAJOR increments when you make incompatible API changes, MINOR when you add backwards-compatible functionality, and PATCH when you make backwards-compatible bug fixes.

What happens to minor and patch when I bump major?

Bumping MAJOR resets both MINOR and PATCH to 0. For example, 1.4.7 → 2.0.0. Bumping MINOR resets only PATCH to 0: 1.4.7 → 1.5.0. Bumping PATCH increments only the last segment: 1.4.7 → 1.4.8.

How are prerelease labels handled?

A prerelease suffix is appended after the bumped core version with a hyphen: e.g. 2.0.0-rc.1. When a prerelease is present the core bump rules still apply first; the prerelease identifier is then appended to the result.

What version strings are accepted?

The tool accepts standard semver strings: MAJOR.MINOR.PATCH, optionally followed by a prerelease identifier (-alpha.1, -beta.2, -rc.3, or any dot-separated alphanumeric token) and optional build metadata (+build.20240101). Leading "v" or "V" is stripped automatically.

Is anything sent to a server?

No. All validation and computation runs entirely in your browser via JavaScript. Nothing is transmitted.

Semantic Version Bumper

Name: Semantic Version Bumper
Availability: InStock
Author: Nham Vu

Enter a semver version, choose Bump Major / Minor / Patch, and get the new version with optional prerelease label instantly.

Current Version

Version String

Accepts MAJOR.MINOR.PATCH, optional prerelease & build metadata. Leading “v” is stripped.

Prerelease Label (optional)

Bump Rules

MAJORIncrement major, reset minor & patch to 0
MINORIncrement minor, reset patch to 0, keep major
PATCHIncrement patch only, keep major & minor

Enter a version and click a bump button to see the result.

Copied!

Summary

Enter a semver version, choose Bump Major / Minor / Patch, and get the new version with optional prerelease label instantly.

How it works

Enter your current version string (e.g. 1.2.3 or 2.0.0-beta.1) in the input field.
The tool validates the version against the semver specification and shows the parsed MAJOR.MINOR.PATCH breakdown.
Optionally select a prerelease type (alpha, beta, rc, or custom) and a numeric build index.
Click Bump Major, Bump Minor, or Bump Patch to compute the new version following semver rules.
The result appears instantly in large monospace text. Click Copy to copy it to your clipboard.
Bump rules are shown inline: major resets minor and patch to 0, minor resets patch to 0, patch increments only.

Use cases

Compute the next release version before tagging a Git repository.
Verify semver bump rules when onboarding new contributors to a project.
Generate prerelease identifiers (alpha, beta, rc) for staged release pipelines.
Quickly sanity-check a version string from a package.json or build script.
Create versioned API endpoint strings without doing the arithmetic by hand.
Automate mental bookkeeping during sprint planning by pre-computing the next set of version numbers.
Teach semver semantics interactively during code reviews or onboarding sessions.
Validate that a proposed version bump follows breaking-change conventions.

Frequently Asked Questions

Last updated: 2026-06-09 · Reviewed by Nham Vu