Semver Compare
Compare two semantic version numbers.
Try it with this example
Enter 1.2.3 and 1.2.4 to see which is newer. Try 2.0.0 vs 1.9.9.
What is this tool?
Semantic Versioning (semver) uses three numbers: major.minor.patch (e.g. 1.2.3). Major means breaking changes; minor means new features that stay backward compatible; patch means bug fixes. The Semver Compare tool takes two version strings and tells you which is newer, which is older, or whether they're equal. Enter 1.2.3 and 1.2.4—it reports that 1.2.4 is newer. Enter 2.0.0 and 1.9.9—it correctly identifies 2.0.0 as newer despite the smaller-looking minor and patch.
Comparing versions by string doesn't work: "1.10" should be greater than "1.9," but a naive string comparison might say otherwise. Semver comparison follows the spec: parse major, minor, and patch, then compare numerically. Pre-release tags (e.g. 1.0.0-alpha) and build metadata (1.0.0+build) are handled according to semver rules. This tool does the parsing and comparison so you don't have to.
Use it for dependency management: "Can I upgrade to this version?" For release notes: "What's new between 2.1.0 and 2.2.0?" For CI/CD: "Is the deployed version newer than the built one?" For any decision that depends on version ordering. The tool runs in your browser. No API, no server.
It expects valid semver strings. Nonstandard formats (e.g. "v1.2.3" or "1.2") may work if the tool normalizes them, but the spec is strict. For well-formed semver, results are reliable. Bookmark it for quick version checks during development and releases.
Simple, fast, and accurate for semver-compliant versions.