Compare two JSON documents to find differences, added keys, and changed values.
Format, indent, validate, and beautify JSON with custom spacing.
Edit JSON files with a real code editor, tree view, validation, and syntax highlighting.
Validate JSON syntax and view exact error line, column, and diagnostic tips.
Minify JSON by stripping whitespace and formatting for production.
Visualize JSON hierarchy with collapsible outline tree view.
JSON objects are unordered by specification, but the text on your screen is not — and that mismatch causes real friction. Two documents holding identical data can produce a diff full of changes purely because the keys came out in a different order, and a config file whose keys grew organically over time is hard to scan for the setting you want. Sorting the keys fixes both. This tool reorders every object's keys alphabetically, ascending or descending, at every level of nesting, leaving arrays in their original order because array order is meaningful in JSON. The result is a canonical form: sort both documents the same way and a text diff finally shows only genuine changes. It is also just easier to read a long settings file when the keys are in a predictable order. Everything runs client-side, so nothing is uploaded.
No. JSON objects are unordered by specification, so reordering keys produces an equivalent document. Every key and value is preserved exactly.
No. Array order is meaningful in JSON, so elements are left exactly where they are. Only object keys are reordered.
Mainly to make two documents comparable: sorting both gives a canonical order, so a text diff shows only real changes rather than reordering noise. It also makes long config files easier to scan.
Yes. Sorting is applied recursively, so objects nested inside other objects or inside arrays are sorted too.
Keys are compared as strings, so ordering follows standard string comparison — digits and most symbols sort before letters.
No. Sorting runs entirely in your browser and the document is never transmitted or stored.