Input
Output
Formatted result will be displayed here
Sorting JSON keys alphabetically gives you a deterministic representation, which is useful any time you need to compare two JSON documents, hash them, or commit them to version control without spurious diffs. This tool sorts keys at every level of nesting, leaves arrays in their original order, and preserves all values untouched. The result is the same data in a canonical form.
Normalize JSON fixtures so reordering a field in one service does not produce a noisy diff in unrelated tests.
Sort both sides first, then run a text diff and every real difference jumps out without key-order noise.
Hashing JSON only makes sense over a canonical form; sorting keys is the simplest canonicalization step.
Contributors tend to append new keys at the bottom. A sort pass puts everything back in a predictable order.
No. Array order is semantic, so the tool leaves arrays alone. Only object keys are sorted.
Sort order is lexicographic using the default string comparison, which means uppercase letters come before lowercase. Normalize case beforehand if that matters.
Yes. The JSON spec does not require any particular key order, so sorting is always safe from a parser standpoint.
Duplicate keys are not valid JSON and will be flagged during parse. Only the last occurrence survives most parsers, but you should fix the source.