What is the difference between Caret (^) and Tilde (~) in package versions?

Caret (^) allows updates that do not modify the left-most non-zero digit (e.g., ^1.2.3 permits >=1.2.3 and =1.2.3 and <1.3.0).

When should I bump Major, Minor, or Patch according to SemVer?

Bump Major when introducing backwards-incompatible API changes. Bump Minor when adding backwards-compatible functionality. Bump Patch when releasing backwards-compatible bug fixes.

How do prerelease versions compare in precedence?

A normal release has higher precedence than any prerelease for that same version (e.g., 1.0.0 > 1.0.0-rc.1). Prerelease identifiers are compared left to right, with numeric identifiers compared numerically.

Does this SemVer calculator support build metadata?

Yes. Build metadata denoted by a plus sign (e.g., 1.0.0+20130313144700) is parsed correctly, though per SemVer 2.0.0, build metadata does not influence version precedence.

Is any version information sent across the network?

No. The calculator runs completely in your local browser JavaScript environment with zero network calls.

SemVer Checker & Bump Calculator

Q: When should I bump Major, Minor, or Patch according to SemVer?

Bump Major when introducing backwards-incompatible API changes. Bump Minor when adding backwards-compatible functionality. Bump Patch when releasing backwards-compatible bug fixes.

Q: How do prerelease versions compare in precedence?

A normal release has higher precedence than any prerelease for that same version (e.g., 1.0.0 > 1.0.0-rc.1). Prerelease identifiers are compared left to right, with numeric identifiers compared numerically.

Validate Semantic Versioning (SemVer 2.0.0), compare versions, test range matchers (^, ~), and calculate version bumps.

100% free
Private in browser
No signup
No watermarks

Target SemVer Version

Prerelease Tag Identifier

Parsed SemVer Breakdown

Major1

Minor4

Patch2

PrereleaseNone

Next Version Bump Calculations

Patch Bump1.4.3

Minor Bump1.5.0

Major Bump2.0.0

Pre-patch Bump1.4.3-beta.0

Pre-minor Bump1.5.0-beta.0

Next Prerelease1.4.3-beta.0

Range Matching & Comparison Tester

Test against NPM Range (^, ~, >=)

Version 1.4.2 SATISFIES range "^1.4.0"

Compare with another Version

1.4.2 is LESS than 1.5.0

Rate this tool

Be the first to rate — helps others and improves this page.

About SemVer Checker & Bump Calculator

Managing package versions across npm, Cargo, Composer, or Git tags? The SemVer Checker & Bump Calculator parses version strings according to the official SemVer 2.0.0 specification. It automatically calculates the next major, minor, patch, premajor, and prerelease version tags, compares two versions for precedence, and checks if a version satisfies package ranges like ^ and ~. Everything runs instantly in your browser without tracking.

How to use SemVer Checker & Bump Calculator

Enter your current package version string (e.g. 1.4.2 or 2.0.0-rc.1).
Optionally provide a custom prerelease tag (e.g. alpha, beta, rc, canary).
Review the instant breakdown and copy calculated next version bumps (patch, minor, major).
Test range conditions (^1.0.0, ~1.4.0) or compare precedence with another version.

Key features

Strict SemVer 2.0.0 compliant validation and component breakdown
Instant calculation of next patch, minor, major, and prerelease versions
NPM range evaluator supporting caret (^), tilde (~), and comparison operators (>=, <=)
Version precedence comparator accurately resolving prerelease hierarchy
Zero dependencies on external servers — 100% fast client-side computation

Frequently asked questions

What is the difference between Caret (^) and Tilde (~) in package versions?: Caret (^) allows updates that do not modify the left-most non-zero digit (e.g., ^1.2.3 permits >=1.2.3 and <2.0.0). Tilde (~) allows patch-level changes if minor is specified (e.g., ~1.2.3 permits >=1.2.3 and <1.3.0).
When should I bump Major, Minor, or Patch according to SemVer?: Bump Major when introducing backwards-incompatible API changes. Bump Minor when adding backwards-compatible functionality. Bump Patch when releasing backwards-compatible bug fixes.
How do prerelease versions compare in precedence?: A normal release has higher precedence than any prerelease for that same version (e.g., 1.0.0 > 1.0.0-rc.1). Prerelease identifiers are compared left to right, with numeric identifiers compared numerically.
Does this SemVer calculator support build metadata?: Yes. Build metadata denoted by a plus sign (e.g., 1.0.0+20130313144700) is parsed correctly, though per SemVer 2.0.0, build metadata does not influence version precedence.
Is any version information sent across the network?: No. The calculator runs completely in your local browser JavaScript environment with zero network calls.