Account

What new tool do you want?

Developer Tools

Semantic Version Calculator

Compare two semantic versions, check whether a version satisfies an npm range like ^1.2.0 or ~2.3, and see the next major, minor and patch versions.

How to use

  1. 1Enter a version, and optionally a second version and a range.
  2. 2See which version is newer, whether the range matches, and the bumped versions.

How it's calculated

Precedence follows SemVer 2.0: MAJOR, MINOR and PATCH compare numerically; a pre-release (1.0.0-beta) is lower than its release; build metadata (+sha) is ignored. Ranges follow npm rules.

Frequently asked questions

What does ^1.2.3 allow?

Any version from 1.2.3 up to but not including 2.0.0 — compatible changes only. For 0.x versions it's stricter: ^0.2.3 means <0.3.0.

What does ~1.2.3 allow?

Patch updates only: from 1.2.3 up to but not including 1.3.0.

Why doesn't ^1.0.0 match 1.1.0-beta?

npm excludes pre-releases from ranges unless the range itself names a pre-release of the same MAJOR.MINOR.PATCH.

A worked example of caret's asymmetry below 1.0.0

^1.2.0 allows anything from 1.2.0 up to (but not including) 2.0.0 — any minor or patch bump is considered backward-compatible once you're past major version 1, which is the whole point of semantic versioning's promise. But 0.2.5 satisfying ^0.2.3 is true, while 0.3.0 satisfying that same ^0.2.3 is false — below 1.0.0, npm tightens the caret to only allow patch-level changes within the same minor version, treating the entire 0.x line as unstable where even a minor bump might break things. This asymmetry is a frequent source of confusion: ^ means "don't change the leftmost non-zero digit," not "don't change the major version" specifically.

Why 1.0.0-rc.1 sorts below 1.0.0 — the pre-release rule

Comparing 1.0.0 against 1.0.0-rc.1 reports 1.0.0 as newer, even though rc.1 was presumably published first in a real release process — semver's rule is that any pre-release identifier (-alpha, -beta, -rc.1) sorts strictly lower than the release version it's attached to, regardless of publish order, because a release candidate is explicitly less finished than the final release it precedes. This is also why ^1.0.0 doesn't match a version like 1.3.0-beta by default — npm deliberately excludes all pre-releases from a normal range unless the range itself names a pre-release of that exact major.minor.patch, which prevents your production dependency resolution from silently picking up an unstable beta you never asked for.

Why the next major/minor/patch outputs aren't just +1 to a number

For a pre-release version like 1.0.0-alpha.1, the "next patch" output is just 1.0.0, not 1.0.1 — because the pre-release tag itself represents an in-progress version of 1.0.0, so the very next meaningful version is the release that drops the pre-release tag, not a patch bump past it. This reflects how real release workflows actually work: alpha and beta tags are stepping stones toward a specific target version, and treating them as already-patched would skip over the version they were building toward.

Blank compare and range lines are simply left out

Version opens on 1.4.2, compare with opens on 1.10.0, and the range opens on ^1.2.0. Both of those extra boxes are optional. If I clear the compare box, the comparison line disappears. If I clear the range, the satisfies line disappears. When both are filled, the comparison is the main result and the range answer sits beside it. Next major is the first number plus one, with the rest reset. I clear one box when I only want a single answer and do not want a second line arguing with it.

Related tools

More: Developer Tools