Quick start
-
Enter version
Optional v prefix, e.g. v1.2.3.
-
Read compare
Negative means the first version is lower.
Semver Calculator
Enter x.y.z to see major/minor/patch bumps and compare against another version.
Privacy: processed locally, never uploaded.
↓ Paste in the input area below to see results instantly
Semantic version bump and compare (major/minor/patch).
Version
Compare to
major +1
2.0.0
minor +1
1.3.0
patch +1
1.2.4
compare (a vs b)
-1
Notes
Format
Optional v prefix and x.y.z digits; prerelease tags not supported. Negative if a<b, 0 if equal, positive if a>b
Enter x.y.z to see major/minor/patch bumps and compare against another version.
Limits
No prerelease (-alpha) or build (+build) metadata.
Features and use cases
Compare SemVer strings, handle prerelease ordering, and bump patch/minor/major per npm conventions.
Use before releases, dependency conflict checks, and manual CI version policy review.
Typical Workflow
When developing new features, first increment the minor version (e.g., 1.2.3 → 1.3.0). Before release, check API compatibility: if breaking changes exist, manually switch to major increment (1.2.3 → 2.0.0). Finally, use version comparison to confirm the new version is higher than all released versions.
For critical bug fixes, teams often maintain multiple version lines. After patching 1.2.3 to 1.2.4, compare it with the in-development 1.3.0. The tool instantly validates version tree relationships, preventing release sequence errors.
Examples
Example
Input
1.2.3 patch bump
Output
1.2.4
FAQ
Matches npm?
Core x.y.z compare matches; use npm CLI for complex ranges.
Why can't I compare pre-release versions like 1.0.0-beta?
The tool follows strict Semver 2.0 specs—pre-release versions require specialized tools (like npm's semver library). We focus on core x.y.z formats for reliability in most development scenarios.