Data & Requests · LOCAL TOOL

JSON Shape Diff

Compare two representative JSON documents to find added paths, removed paths, and value-type changes before a client or service contract drifts.

Runs in this page
No API call

WORKSPACEINPUT → RESULT

Your input

LOCAL

Result

Run the tool to see a result.

Your result will appear here. Input is not saved.

Browser-side processingNothing is sent to a tool API.

WHY THIS TOOL EXISTS

A focused job, not a black box.

The report compares structure, not values. Arrays are summarized by their observed item shapes, which helps distinguish a harmless value change from a field that disappeared or changed type.

How to use it

Paste the earlier sample and newer sample.
Run the comparison.
Review each path and decide whether the change is intentional.

TRY A WORKING EXAMPLE

Start with known input.

Load this sample into the workspace, run the tool, and compare the result shown below.

Show sample input

{
  "before": "{\"id\":12,\"profile\":{\"name\":\"Rin\",\"team\":\"blue\"},\"labels\":[\"new\"]}",
  "after": "{\"id\":\"12\",\"profile\":{\"name\":\"Rin\"},\"active\":true,\"labels\":[\"ready\"]}"
}

Expected sample result from the local tool

3 structural difference(s) found.

Change	Path	Earlier	Newer
Added	$["active"]	—	boolean
Type or shape changed	$["id"]	number	string
Removed	$["profile"]["team"]	string	—

LIMITS AND INTERPRETATION

What the result cannot tell you.

A sample can only reveal fields present in that sample. This is not a formal JSON Schema validator and cannot prove that a field is always present in production.

Inputs are processed in this page and are not written to local storage.