Semver Calculator & Comparator

Parse, compare, bump, and sort semantic versions. Supports pre-release labels, build metadata, and bulk sorting. Full semver 2.0 spec compliance.

Your data never leaves your browser Available via MCP

Enter a version and click Parse

How to Use

  1. Select a mode: Parse (break down a version), Compare (compare two versions), Bump (calculate next versions), or Sort (sort a list).
  2. Enter a version string like 1.2.3, v2.0.0-beta.1, or 3.1.4+build.42.
  3. Click the action button to see results.
  4. Copy results with the Copy button.

Semver Version Format

A semantic version has the format MAJOR.MINOR.PATCH[-PRERELEASE][+BUILD]. For example, 2.1.3-beta.1+build.456 has major=2, minor=1, patch=3, pre-release=beta.1, and build metadata=build.456.

When to Bump Each Component

  • Major — when you make incompatible API changes (e.g., removing a public method, changing return types)
  • Minor — when you add functionality in a backwards-compatible manner (e.g., new features, new endpoints)
  • Patch — when you make backwards-compatible bug fixes

Related Tools

Generate unique identifiers with the UUID Generator. Format package.json files with the JSON Formatter. Compare text differences with the Diff Checker. Calculate durations between releases with the Duration Calculator.

Frequently Asked Questions

What is semantic versioning?
Semantic versioning (semver) is a versioning scheme using the format MAJOR.MINOR.PATCH. MAJOR changes indicate breaking API changes, MINOR changes add backwards-compatible features, and PATCH changes are backwards-compatible bug fixes.
What do pre-release labels mean?
Pre-release labels like "-alpha.1", "-beta.2", or "-rc.1" indicate versions that are not yet stable. They have lower precedence than the associated release: 1.0.0-alpha < 1.0.0.
What is the build metadata?
Build metadata (after a "+") like "+build.123" provides additional build information but is ignored when determining version precedence. Two versions that differ only in build metadata are considered equal.
How does version comparison work?
Versions are compared left to right: major, then minor, then patch. If all three are equal, a version without a pre-release tag has higher precedence. Pre-release versions are compared lexicographically.

Use this tool from AI agents. The CodeTidy MCP Server lets Claude, Cursor, and other AI agents use this tool and 46 others directly. One command: npx @codetidy/mcp

Drop file to load