Clean and compare JSON debugging data
Finish one small debugging task: format two safe JSON responses, find two changed fields and one addition, then download the merged result. No account or prepared file is needed. Tools open in separate tabs; copying between them is manual.
1. Format and save the first response
Open JSON Formatter in a new tab. Return here, copy Example A, paste it into the tool and check that the input is valid. Use Download to save the formatted JSON as before.json.
These are synthetic records. When using your own data later, remove secrets and personal data first. Keep numeric IDs as strings. Start with a small excerpt, not a large production dump.
Example A — before
{"requestId":"demo-001","status":"queued","attempts":1}2. Format the second response
Copy Example B into the formatter tab, replacing the first example yourself. Download the result as after.json. Keep this guide open while you work.
There is no automatic data transfer between tools. You can reopen a saved file in the formatter, or use the two examples here when pasting into the comparison tool.
Example B — after
{"requestId":"demo-001","status":"ready","attempts":2,"region":"test"}3. Compare and take the result with you
Open JSON Diff & Merge in a new tab. Copy Example A above into the left input and Example B into the right input. Wait for the comparison to update.
Expected result: status changes from queued to ready; attempts changes from 1 to 2; region is added with the value test. The requestId is unchanged: two changes, one addition, no removals.
Open Merged JSON, then Copy or Download. The exported result must match Example B. Right-side values override the left; arrays are replaced, not combined. If either input is invalid, fix it before exporting.
Open JSON Diff & Merge in a new tab4. Check completion and repeat safely
You are done when you can identify the three differences and have a copied or downloaded JSON result matching Example B. Keep before.json and after.json if you want to repeat the task.
Next time, return to this guide, open the tools and paste or import your saved JSON again. There is no cloud sync. Browser history and tab drafts can be cleared and do not replace a backup. Clear sensitive drafts before sharing a device.
The diff rejects duplicate keys and numbers it cannot represent without precision loss. The formatter can help inspect the original, but it does not prove the data is trustworthy. Long synchronous computations cannot be interrupted; reduce the input if the page becomes slow.