Browser tools for cleaning and comparing real JSON payloads.

Why the site focuses on JSON work

The strongest workflows in this repo are the ones that help you inspect nested API responses, compare request and response bodies, and turn copied log fragments back into readable structures. That is why the homepage now points first to the JSON tools instead of presenting the site as a generic grab bag of utilities.

Core processing stays in the browser, so the normal cleanup and comparison flow works without an account, without a backend round-trip, and without making ad interaction part of the task.

Worked example: from copied log text to readable JSON

A common debugging path starts with a payload that was encoded once by an API and again by a log pipeline. JSON Utils is for that moment.

{"event":"webhook","payload":"{\"user\":{\"id\":42},\"flags\":\"[\\\"beta\\\"]\"}"}

After unwrapping, the same sample becomes readable structured data that you can inspect in one pass instead of manually removing escapes and reparsing nested values.

{
  "event": "webhook",
  "payload": {
    "user": {
      "id": 42
    },
    "flags": [
      "beta"
    ]
  }
}

Which tool to open first

Open JSON Utils when the payload itself is hard to read because arrays, booleans, or nested objects arrived as escaped strings. Open JSON Diff when both sides are already valid JSON and you want a stable change report.

Both tools are intended for direct debugging workflows: paste the sample, get a deterministic result, then move on.

Why data stays in your browser

This project is deliberately static and browser-only for core transforms. That keeps operating cost low, removes the need for account gates, and makes it easier to trust what the site is doing with copied debugging data.

You should still remove secrets before pasting production material, but the main cleanup and comparison work does not depend on shipping payloads to an application server.

What comes next

The next product work is focused on making JSON Diff more useful for real debugging cases while keeping its output deterministic and easy to trust.

No new non-JSON tools are planned. The site is intentionally narrower now so the existing JSON pages can become sharper instead of broader.