UUID Studio

UUID Studio

JSON Compare

Structural JSON diff plus UUID and byte-level comparison.

  • đź”’ 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

  • Side A (config v1) 
    { "env": "dev", "replicas": 1 }
  • Side B (config v2) 
    { "env": "prod", "replicas": 3 }

About JSON Compare

Two JSON blobs that 'should' be identical rarely are - a reordered key, a stringified number, a field that quietly vanished after a migration. Scrolling both side by side and hoping to spot the difference is a losing game.

Drop two values in and get a structural diff: keys only in A, keys only in B, values that changed, and everything that stayed the same - compared by JSON semantics, not raw text, so key order and whitespace never produce false positives.

If either side isn't valid JSON, the tool falls back to comparing them as UUIDs or raw bytes instead, which is useful when you're not sure if two identifiers or binary blobs actually match.

FAQ

Is key order ignored?
JSON objects are compared by key semantics, not source key order. Arrays are compared by index.
Can I compare UUID strings?
Yes. Two valid UUIDs in the same format are compared as 16-byte values.