Semver Calculator
Parse, compare, and bump semantic versions
Semver Calculator is a free online tool from BrowserUtils that parse, compare, and bump semantic versions. It runs entirely in your browser — your data never leaves your device. No account required.
Major
1
Minor
2
Patch
3
1.2.3 < 1.3.0 (1.3.0 is newer)
How to use Semver Calculator
- 1 Paste or type your input into the editor above.
- 2 The tool processes your data instantly — right in your browser, with nothing sent to a server.
- 3 Copy the result with one click or continue editing your input.
About Semver Calculator
Free online semantic versioning calculator. Parse version strings, bump major/minor/patch versions, and compare two versions to determine which is newer. This tool runs entirely in your browser — your data is never sent to a server. Just paste your input, get instant results, and copy with one click. No sign-up or installation required.
Semver Calculator specs
- Runtime
- 100% client-side (browser)
- Cost
- Free — no account, no rate limits, no usage caps
- Browser support
- Chrome 90+, Firefox 88+, Safari 14+, Edge 90+
- Part of
- 299 developer tools on BrowserUtils (100% client-side)
Questions
What is semantic versioning?
Semantic versioning (semver) uses a MAJOR.MINOR.PATCH format. Increment MAJOR for breaking changes, MINOR for backward-compatible features, and PATCH for backward-compatible bug fixes. Pre-release labels like -beta.1 can be appended.
How do I compare two semantic versions?
Compare major versions first, then minor, then patch. For example, 2.0.0 > 1.9.9 because the major version is higher. Pre-release versions have lower precedence than the normal version (1.0.0-alpha < 1.0.0).
When should I bump the major version?
Bump the major version when you introduce breaking changes that require users to modify their code. Examples include removing a public API, changing function signatures, or altering default behavior in incompatible ways.
What is a pre-release version in semver?
A pre-release version appends a hyphen and identifiers after the patch number, such as 1.0.0-alpha.1 or 2.0.0-rc.3. Pre-release versions have lower precedence than the associated normal version and signal that the release is not yet stable.
Does the semver calculator handle version ranges like npm uses?
This tool focuses on parsing, bumping, and comparing individual version strings. For npm-style range resolution (^, ~, >=), check the npm semver package documentation.
Comments
Related tools
More DevOps & Config
.gitignore GeneratorDockerfile GeneratorDocker Compose GeneratorNginx Config Generator.editorconfig Generator.env File GeneratorGitHub Actions GeneratorREADME Generator
View all DevOps & Config tools
Comments