Semver Checker
Semantic versioning, or semver, is the MAJOR.
- Runs in your browser No upload — everything runs on your device.
- No sign-up, no watermark Free to use, no account needed.
- Files never uploaded Nothing leaves your device.
- 5,400+ tools, one site File, unit and currency tools in one place.
Semantic versioning, or semver, is the MAJOR.MINOR.PATCH scheme used by npm, Rust crates, and many other package ecosystems. This tool checks whether a version string follows the rules and breaks it into its parts: the major, minor, and patch numbers, plus any prerelease tag and build metadata. A leading v is accepted and stripped, since many projects write v1.2.3. Numbers must not have leading zeroes, and prerelease identifiers follow strict rules of their own. The meaning matters as much as the shape: a major bump signals breaking changes, a minor bump adds features compatibly, and a patch bump fixes bugs. Prerelease versions such as 2.0.0-rc.1 sort before the release they lead up to. Use it to validate version strings in configuration files, release scripts, and dependency lists. The check runs entirely in your browser.
How to use Semver Checker
- Paste your text type, paste (Ctrl+V) or drop a .txt file into the box above.
- Click Convert the tool runs entirely in your browser — nothing is uploaded.
- Read your results they appear below the tool as soon as the conversion finishes.
- Download the result save it for your records.
- Convert another clear the box and paste new text — no sign-up, no limits.
Format facts
| Input | Any plain text, or a .txt file (dropped or browsed). |
|---|---|
| Engine | Built-in browser engine |
| Category | Developer Tools |
Limits
- Browser processing has practical limits: files over 200 MB (or very long media) may be too large for your device. You will get an honest “too large” message, never a fake result.
- Pasted content is handled as plain text — formatting from documents is not preserved.
Frequently asked questions
What do the three numbers mean?
Major for breaking changes, minor for new features that stay compatible, and patch for bug fixes.
Is v1.2.3 valid semver?
Strictly the spec has no v, but this tool accepts and strips a leading v because many projects write versions that way.
Why are leading zeroes forbidden?
To avoid ambiguity: 01.2.3 could be read as either version 1 or as something else, so the spec bans it outright.
How do prereleases sort?
Before the release they lead up to, so 2.0.0-rc.1 comes before 2.0.0, and rc.1 comes before rc.2.
Was this tool helpful?
Thanks — your feedback helps us improve this tool.
Sorry it didn’t help — tell us what went wrong and we’ll fix it.