Skip to content
TextArray1.41.0
100% local

SemVer sorter and comparator

Sort a list of version numbers by semantic versioning precedence.

Input
Output
Related tools
Natural sort linesLists & combinations
Sort numbersNumbers
Compare listsLists & combinations
i18n key diffDeveloper tools
TOML to JSON converterDeveloper tools
SQL to JSONDeveloper tools
SemVer sorter and comparator
Paste a list of version numbers and this tool sorts them by semantic versioning (SemVer) precedence, not plain text order. A text sort puts "1.10.0" before "1.9.0" because "1" comes before "9" character by character; this tool compares the major, minor and patch numbers as numbers, so "1.10.0" correctly lands after "1.9.0". Pre-release versions are handled too: "1.0.0-rc.1" sorts before its own release "1.0.0", exactly as the SemVer spec defines, and build metadata after a "+" is read but never affects ordering.
Turn on "Ignore v prefix" to accept git-tag-style versions such as "v1.2.3" alongside bare ones. "Exclude pre-release versions" drops any line with a "-suffix" from the output entirely, handy when you only want shipped releases. "Keep only the highest version per" collapses the list down to one entry per major or per major.minor branch — paste every tag a project ever had and get back just the latest patch of each release line. Lines that are not valid SemVer can be flagged with "Mark lines that are not valid SemVer" so a stray "latest" or malformed tag doesn't silently vanish from a long list; leave it off to drop them instead. Mode switches this to comparing two versions per line, or to inspecting parts, faults and a range such as ^1.2.
This is the kind of check that comes up when triaging a changelog, deciding which of a project's git tags are actual releases, or picking the highest compatible dependency version out of a lockfile or registry listing. The direction option flips between ascending and descending order in one click, so newest-first is just as easy as oldest-first.
Everything runs locally in your browser: the list of versions never leaves your device. Copy the sorted result, download it as a .txt file, or send it straight into another tool to keep working.
FAQ
Why does "1.10.0" sort after "1.9.0" here but not in a plain text sort?
A text sort compares character by character, so "1" beats "9" and "1.10.0" ends up first. This tool compares the major, minor and patch fields as numbers instead, which is how SemVer actually defines version order.
Why does a pre-release version like "1.0.0-rc.1" sort before "1.0.0"?
The SemVer spec gives a pre-release version lower precedence than its final release. "1.0.0-rc.1", "1.0.0-beta" and similar suffixed versions are considered earlier than the plain "1.0.0" they lead up to.
What does "Keep only the highest version per" do?
It collapses the sorted list down to one line per group — either per major version (1.x.x) or per major.minor version (1.2.x) — keeping only the highest-precedence version found in each group and discarding the rest.
What happens to lines that are not valid SemVer?
They cannot be placed in a numeric order, so they are set aside from the sort. Turn on "Mark lines that are not valid SemVer" to keep them, annotated, at the end of the output; leave it off to drop them from the result.
Is my list of versions uploaded anywhere?
No. Sorting and comparison run entirely in your browser — the versions you paste are never sent to a server.