About this tool
Bump, compare, and parse semantic version numbers. Saves time when logs, design specs, or infra configs use a different format than your code expects.
Paste a semantic version such as 1.2.3 or 2.0.0-beta.1. Choose bump (major, minor, patch) or compare two versions. Example — Minor bump for a feature release: try `1.2.3 → bump minor` and expect something like `1.3.0`.
Build metadata (+build.5) handling is limited compared to a full SemVer library. See also: Gitignore Generator, and Cron Expression Parser. Runs in your browser — nothing you paste gets uploaded.
How to use
- Paste a semantic version such as 1.2.3 or 2.0.0-beta.1.
- Choose bump (major, minor, patch) or compare two versions.
- Use parse mode when you need the structured major/minor/patch parts.
- Copy the resulting version into package.json, tags, or release notes.
Example
Minor bump for a feature release
Input
1.2.3 → bump minor
Output
1.3.0
Limitations
- Build metadata (+build.5) handling is limited compared to a full SemVer library.
- Does not resolve npm range operators (^, ~, ||) or lockfile constraints.
- Pre-release ordering follows simple parse rules; edge cases may differ from npm’s comparator.
Related guides
1Related tools
2Frequently asked questions
What does the SemVer Calculator do?
Bump, compare, and parse semantic version numbers. Runs in your browser — no install, no account.
How do I use the SemVer Calculator?
Paste a semantic version such as 1.2.3 or 2.0.0-beta.1. Choose bump (major, minor, patch) or compare two versions. Use parse mode when you need the structured major/minor/patch parts. Copy the resulting version into package.json, tags, or release notes.
Is the SemVer Calculator free?
Yes. No signup, no usage limits, no paywall.
Does the SemVer Calculator upload my data?
No. Processing happens locally in JavaScript. Your input is not uploaded, stored, or logged.
What are the limitations of the SemVer Calculator?
Build metadata (+build.5) handling is limited compared to a full SemVer library. Does not resolve npm range operators (^, ~, ||) or lockfile constraints. Pre-release ordering follows simple parse rules; edge cases may differ from npm’s comparator.