JSON Compare: Free Online JSON Comparison Tool — How-To Guide

When two JSON documents look almost the same, spotting the difference by eye is slow and error-prone. A missing field, a changed number, or a renamed key can hide in hundreds of lines. ToolsFam's JSON Compare tool does that work for you: paste two JSON documents, and it shows you exactly what was added, removed, or changed, with a side-by-side formatted view you can read at a glance.

Try it free: JSON Compare

What the Tool Does

JSON Compare takes two JSON documents and produces a change summary plus a side-by-side formatted output. Instead of scrolling through two files trying to remember what you saw, you get a clear breakdown of the paths that differ, so you can focus on the changes that matter.

It is built for everyday debugging and review work, such as:

• Comparing an expected API response with the actual response you received.
• Checking what changed between two versions of a configuration file.
• Reviewing a before-and-after snapshot of data before you deploy or share it.
• Finding out why two systems disagree about the same record.

The tool formats both documents, so even messy, single-line JSON becomes readable. No account, install, or upload is needed.

How to Use It Step by Step

1. Open the tool

Go to the JSON Compare page and you will see a single workspace for your two documents. There is nothing to install and no sign-in screen standing between you and the comparison.

2. Paste your first JSON document

Paste the original, expected, or "before" version of your JSON into the first area. This is the baseline the tool compares against.

3. Add the separator

On its own line between the two documents, type three hyphens:

---

This split marker tells the tool where the first document ends and the second one begins. Keep it on a line by itself, with nothing else on that line, so the tool can split the input cleanly.

4. Paste your second JSON document

Paste the new, actual, or "after" version of your JSON after the separator.

5. Review the change summary

The tool inspects both documents and summarizes the added, removed, and changed paths. Start with this summary: it tells you where to look, rather than forcing you to scan the whole output. A changed value, a new key, and a deleted entry each show up as a distinct kind of change.

6. Read the side-by-side formatted output

Next, look at the formatted side-by-side view. Both documents are neatly formatted, so structure, nesting, and values are easy to follow. Work through the highlighted differences one by one, and check each against what you expected to change. If a difference surprises you, that is usually the bug, the typo, or the unexpected edit you were looking for.

7. Copy or download the result

When you have finished reviewing, copy the result or download it for your records, a bug report, or a code review. You can then clear the workspace and start a fresh comparison.

3 Practical Tips

Compare in the right direction. Put the older or expected document first and the newer or actual document second. The added and removed labels only make sense relative to that order, so swapping the two will flip the summary.

Format before you compare when JSON is minified. Long single-line JSON is hard to read even with a diff. Let the tool format both sides first, then read the differences in the structured view — indentation makes nested changes far easier to spot.

Check the repair label if your JSON is not strict. The tool's primary parser follows strict JSON. If repair is available for a document that does not quite parse, the tool labels the repaired output clearly. Review that repaired output before you trust the comparison, because a repair can change how a value is interpreted.

Frequently Asked Questions

How do I separate the two JSON documents?

Put --- on its own line between the left and right JSON documents. The tool formats both sides and summarizes the changed paths.

Is my JSON uploaded to a server?

No. This tool runs in your browser and does not send your input to a backend service. Your documents stay on your own device.

What JSON syntax is supported?

The primary parser follows strict JSON. When repair is available, the tool labels repaired output clearly so you can review it first.

Can I compare API responses with this tool?

Yes. Comparing an expected response with an actual response is one of the tool's main uses. Paste the expected response first and the actual response second, then read the added, removed, and changed paths to see exactly where they differ.

Privacy Note

JSON Compare runs 100% in your browser. Your files and pasted text never leave your device, and there is no account or upload step. That makes it a safe choice for configuration files and API responses that you would rather not send to an outside service — though, as always, avoid pasting live secrets or passwords into any browser tool.

Try It Free

Ready to find the difference? Try it free: JSON Compare