UUID Studio

UUID Studio

JSON Sort Keys

Recursively sort object keys for deterministic output.

  • đź”’ No data stored or uploaded
  • ⚡ 100% client-side
  • 🆓 Free, no account
Click Convert when ready

Override only when Auto cannot parse your paste. Changing this loads a matching sample into Input — click Convert to run. Use Load sample to cycle every format example.

All conversions

Read-only representations of the same 16 bytes. Every textual form is listed here, not in “Prefer format”.

Paste two values: if both sides are valid JSON, a structural diff appears; otherwise UUID / bytes are compared when both decode to the same format.

A
B

Create or edit JSON here (syntax colors), then format, validate, or convert - same as MongoDB $binary UUID blobs on the Convert tab once detected.

New document

Hash, HMAC, AES-GCM/CBC + RSA-OAEP, codecs, JWT decoding, UUID v4, and secure random - all client-side. JWTs use Base64URL (three segments), not a single MIME Base64 block - use Decode JWT below, not raw Base64 decode.

Examples

  • Unsorted 
    {"z":1,"a":{"y":2,"b":3}}

About JSON Sort Keys

Two JSON documents with identical data but different key order will show up as a full diff in git, a failing snapshot test, or a mismatched checksum - even though nothing meaningful changed.

Sorting keys recursively (alphabetically, at every nesting level) gives you a canonical form so diffs, hashes, and fixtures stay stable across runs and machines. Array element order is left untouched, since reordering arrays would actually change the data.

FAQ

Are arrays reordered?
Array element order is preserved; only object keys are sorted.