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

JSON Diff Checker

Paste two JSON files and get a unified, patch-style diff of the changed lines. Keys are sorted first so reordering does not create noise. All local to your browser.

  • No daily cap
  • Runs in your browser
  • Unified diff output
  • 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: Diff
How was JSON diff?
How it works

JSON diff in three steps

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

  1. STEP 01

    Add both JSON files

    Paste or open the original and the changed version.

  2. STEP 02

    Set the context

    Keep 'Ignore key order' on, and choose how many unchanged lines to show around each change.

  3. STEP 03

    Read or copy the diff

    Lines starting with + were added and lines starting with - were removed. The note shows the totals.

What you get

What JSON diff does, and what it doesn't

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

What you get

  • Familiar diff formatThe output uses the same --- / +++ / @@ layout as git diff, so it feels at home in a review.
  • Consistent layout firstBoth files are re-indented the same way before comparing, so spacing differences never show up.
  • Key order switchSort keys in both files so only real changes appear, or turn it off to see order changes as well.
  • Adjustable contextShow 0 to 50 unchanged lines around each change.
  • Totals at a glanceSee how many lines were added and removed, or a clear message if the files match.

Good to know

  • Line-based viewA changed value shows as one removed line and one added line. For a list of changed paths, use JSON compare.
  • Both inputs must be JSONA parse error names which file is invalid. Fix it with the JSON validator.
  • Arrays keep their orderOnly object keys are sorted. Reordered array items appear as changes.
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 diff

Review a fixture change

Paste before and after versions to see exactly what a code change did to the data.

Spot config drift

Compare environment configs and see only the real differences.

Attach a patch to a ticket

Copy the unified diff into an issue or message.

Check a re-export

Confirm two exports of the same data match, apart from the lines you expect.

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

Reading the output: JSON diff

Each block starts with an @@ line giving the line numbers in the first and second file. Lines starting with a minus exist only in the first. Lines starting with a plus exist only in the second. Lines with a leading space are context.

Because both documents are printed with the same indentation, a diff that shows nothing but a few lines usually points to a real data change.

Making diffs smaller

A few choices keep the review short:

  • Keep key sorting on unless order is part of what you are checking.
  • Reduce context to 0 or 1 when you only need the changed lines.
  • Prefer the path list of JSON compare for deep nesting.
  • For plain text rather than JSON, use the text diff checker.

A diff for code review

Because both inputs are printed with the same indentation and sorted keys, the result works well as a review aid. Paste the generated JSON before and after a code change, and attach the diff to the pull request. Reviewers see only the data that moved, not formatting churn from a different serializer or a reordered object.

FAQ

Questions, answered

Does JSON diff care about key order?

Not by default. Keys are sorted in both files before comparing, so reordering shows no changes. You can turn that off.

Do my config files leave my computer when I diff them?

No. The comparison is done locally in your browser tab, so secrets inside either file are never transmitted.

What do the plus and minus signs mean?

A plus is a line only in the second file, a minus a line only in the first. Unmarked lines are context.

Can I copy the diff into a pull request?

Yes. It is plain text in the standard unified format.

What if the files are identical?

You see a message that both JSON documents are the same.

Is it usable on a small screen?

Yes. It runs on phones and tablets, and the diff is plain text that scrolls sideways when lines are long.