Sort JSON keys & arrays
online, free & instant

Sort JSON in three steps

No account. No upload. No nonsense.

Related JSON tools

Common questions answered

What is JSON key sorting?

JSON key sorting reorders object keys alphabetically at every nesting level while preserving all values and array order. This produces deterministic output: the same data always renders identically regardless of original key order. Sorted JSON is essential for meaningful diffs in version control — without it, reordering a key produces a noisy diff that obscures actual changes.

Sorting improves team consistency. When multiple developers edit the same configuration file, each may add keys in different positions. Sorting before committing normalizes the output so git diffs show only actual content changes. This tool sorts keys recursively through all nested objects while leaving array element order untouched, since arrays are ordered by definition.

{
  "zebra": true,
  "apple": 1,
  "mango": {
    "z": 3,
    "a": 1
  }
}

{
  "apple": 1,
  "mango": {
    "a": 1,
    "z": 3
  },
  "zebra": true
}

Get the most out of this tool

• Sort keys before committing JSON configuration files to version control — it produces cleaner, more readable diffs.
• Arrays are order-dependent and never reordered — only object keys are sorted alphabetically.
• Use sorted output as a canonical form when comparing JSON from different sources that serialize keys differently.

JSON key sorting and why it matters

Sorting JSON object keys alphabetically is a simple operation with outsized benefits for developer workflows. The JSON specification explicitly states that object key ordering is not semantically significant — two JSON objects with the same keys and values are equivalent regardless of key order. This means sorting keys is always safe and never changes the meaning of the data, while producing several practical benefits for maintainability and tooling.

Version control diff quality is the primary benefit of consistent key ordering. When a developer adds a new field to a JSON configuration file, the diff shows exactly one added line — the new field. Without sorted keys, each developer might write fields in different orders, causing subsequent commits to produce large, noisy diffs showing many "changed" lines that only reflect reordering, not actual content changes. Teams that enforce alphabetical key ordering as a convention see dramatically cleaner Git histories.

Canonical JSON — a standard form of JSON where object keys are always sorted alphabetically and whitespace is minimized — is used in cryptographic contexts. When computing a hash or digital signature over a JSON document, both parties must produce identical byte sequences. If one party serializes {"b": 1, "a": 2} and the other serializes {"a": 2, "b": 1}, they get different hashes despite identical data. Canonical JSON ensures all parties produce the same serialization.

API schema documentation benefits from sorted keys because developers reading examples and comparing schemas can find fields more quickly when they are in alphabetical order. Long JSON examples with many fields are significantly more navigable when sorted — finding whether a field exists is an O(log n) mental binary search rather than a linear scan. Many API documentation generators sort keys for this reason.

Recursive key sorting applies alphabetical ordering at every nesting level, not just the top level. A JSON document with five levels of nesting has keys at each level sorted independently. This is what the "Sort Keys" option in this tool does — every object at every depth gets its keys sorted. The result is a fully canonical form that is stable across any re-serialization of the same data.

Programmatic key sorting is straightforward in every language. In JavaScript: JSON.parse(JSON.stringify(obj, Object.keys(obj).sort())). In Python: json.dumps(obj, sort_keys=True). In Go: the standard library's JSON encoder sorts keys alphabetically by default. Despite this simplicity, an online tool is useful when you have a JSON document and need to sort it quickly without writing any code.

When developers use this tool

Additional frequently asked questions