Data and JSON tools Free · No sign-up · No upload

Compare Two JSON Files

Paste two JSON documents and get a plain list of what was added, removed or changed, each with its path. Key order and formatting do not count as differences.

  • No watermark or limits
  • Client-side only
  • Path for every change
  • Ignores key order
First JSON
Second JSON
  • Runs on your device. Files are never uploaded.
  • Free and unlimited. No sign-up, no watermark.
Private: processed in your browserNo upload waitIN: 2 x JSON → OUT: List
How was JSON compare?
How it works

JSON compare in three steps

No account, no email, no waiting for an upload.

  1. STEP 01

    Add the first JSON

    Paste it or open a file in the first box.

  2. STEP 02

    Add the second JSON

    Paste or open the other version in the second box.

  3. STEP 03

    Read the differences

    You get a list: + added, - removed and ~ changed, each with a path like $.user.roles[1].

What you get

What JSON compare does, and what it doesn't

We'd rather tell you up front than surprise you after the download.

What you get

  • Paths you can followEvery difference starts with where it is, for example $.items[2].price, so you can jump straight to it.
  • Three clear labelsAdded, removed and changed are separate, and a change of type (say a number that became text) is called out.
  • Key order is ignoredTwo objects with the same keys and values in a different order count as the same.
  • A summary lineThe result opens with the total and the split between changed, added and removed values.
  • Errors name the fileIf one input is not valid JSON, the message says whether it is the first or the second.

Good to know

  • Arrays are compared by positionItem 0 is compared with item 0. If an item moves, it shows as changed. Use JSON diff to see a line-by-line view.
  • Values, not wordingLong values are shortened in the list. For text that differs inside a string, try the text diff checker.
  • Valid JSON neededBoth inputs must parse. Check them first with the JSON validator.
Private by design

Your data never leave your device

The tool runs inside your browser instead of on our servers, so there is nothing to upload, store or delete afterwards.

Typical online tool upload

Your device→Their server→Your device

Your file travels over the internet, sits on someone else's computer for a while, and you wait for the upload and the download.

Mediaextractr no upload

Your device does all the work

The tool loads into your browser once, then works on your file locally. Nothing is sent, so nothing can leak.

Made for real work

When people use JSON compare

Review an API change

Compare a response before and after a deploy to see which fields moved.

Check config drift

Compare staging and production settings and list only what differs.

Audit an export

Find which records changed between yesterday's and today's dump.

Verify a migration

Confirm that a converted file holds the same data as the source.

Compare

Mediaextractr vs typical upload tools

MediaextractrPrivateTypical upload tools
Your file is uploadedNeverYes
Sign-up neededNoOften, after a few files
Daily file limitNoneOften 1–2 free files
WatermarkNeverSometimes
Wait for upload & downloadNoYes
Speed on very large filesDepends on your deviceDepends on their servers

How the comparison works

Both documents are parsed first, so spaces, line breaks and key order do not matter. The tool then walks them together. Objects are matched by key and arrays by position.

A key only in the second file is added. A key only in the first is removed. A key in both with different values is changed.

Getting a cleaner result

Differences can look noisy when the data is shaped differently. A few habits help:

  • If the same records appear in a different order, sort them before comparing.
  • Use JSON key sorter when you also want to read the two files side by side.
  • Flatten nested data with JSON flatten if you prefer one-level keys.
  • Use the line view in JSON diff when you want a patch-style output.

Comparing the right things

Differences are only useful when both sides are shaped alike. Before you compare, make sure you are looking at the same endpoint, environment and fields. If one side wraps its data in an extra envelope such as a data key, every path will show as added or removed, and the real changes will be hard to find. Strip the wrapper first.

FAQ

Questions, answered

Does key order matter when comparing JSON?

No. Objects with the same keys and values count as equal whatever order the keys are in.

Are my two documents sent anywhere for comparison?

No. Both files are parsed and walked by script in your browser tab, so internal configs or customer exports are never transmitted.

How are arrays compared?

By position. The first item is compared with the first item, and so on. A longer array shows its extra items as added.

What happens if the two files are the same?

You see a message that the documents are the same, with key order and formatting ignored.

Can I get a line-by-line diff instead?

Yes. Use JSON diff for a unified diff with a few lines of context.

Is there a size limit or a mobile problem?

There is no fixed limit besides your device's memory. It works on phones and tablets, but large documents compare faster on a computer.