Semantic Version Comparator
Compare two strict SemVer 2.0.0 versions with correct prerelease ordering and build metadata handling.
Start with your input
Edit the example or replace it with your own text.
How to use Semantic Version Comparator
- Paste the example or your own input.
- Choose the options that match your task.
- Run the tool, review the result, then copy or download it.
When to use Semantic Version Comparator
Lexical sorting puts some version numbers in the wrong order. Compare two semantic versions to evaluate major, minor and patch components numerically, then apply prerelease precedence when required. The report includes each parsed component and the relationship between the inputs. Use it while checking package releases or preparing update tests with versions such as beta.2 and beta.11.
How to interpret the result
This comparator accepts strict major.minor.patch versions with optional prerelease and build metadata. Numeric identifiers cannot contain leading zeroes. Build metadata is shown but ignored for precedence, so two differently built artifacts can compare equal. Large numeric components are compared exactly without conversion to JavaScript Number. Package ranges, caret constraints, wildcards, leading v prefixes and ecosystem-specific version conventions are outside this tool.
Example input
1.10.0-beta.2
What should I check before using the output?
This comparator accepts strict major.minor.patch versions with optional prerelease and build metadata.
Is input uploaded?
Processing takes place in your browser. This tool does not send your input or selected files to a conversion API.