Toolbox Tools

Private JSON debugging toolkit

Extract, unwrap, and compare JSON from real logs and API payloads.

Toolbox Tools helps developers recover structured data from timestamped logs, SSE streams, NDJSON, webhooks, and escaped payloads. Core transformations run locally in the browser without uploading the pasted input.

Built for the awkward JSON around real systems

Debugging input rarely arrives as one clean document. A log line may add a timestamp and level before an object, an SSE response may split records across data: lines, and a queue payload may encode JSON again inside a string field. These tools focus on recovering that structure without guessing or silently repairing invalid data.

Every tool has explicit limits and deterministic behavior so the output can be checked, copied into a ticket, or compared again. No account or ad interaction is required.

JSON Utils

Unwrap escaped JSON inside string fields and inspect the resulting structure as formatted output and a tree.

Open JSON Utils

JSON Log Extractor

Pull valid objects and arrays from mixed logs, SSE streams, NDJSON, and multi-line debugging output.

Extract JSON from logs

JSON Diff

Compare two payloads and get deterministic field-level changes that are easy to scan or paste into tickets.

Open JSON Diff

Worked example: recover a payload from a log line

This line mixes operational metadata with one escaped payload: 

2026-07-22T09:12:04Z INFO request={"id":"req-42","payload":"{\"active\":\"true\",\"items\":\"[1,2]\"}"} duration_ms=8

JSON Log Extractor isolates the object and recursively restores the encoded values: 

[
  {
    "id": "req-42",
    "payload": {
      "active": true,
      "items": [1, 2]
    }
  }
]
Try the example

A three-step debugging workflow

  1. Extract: isolate complete JSON records from log prefixes, SSE lines, or NDJSON.
  2. Unwrap: turn JSON-encoded strings back into objects, arrays, booleans, numbers, and nulls.
  3. Compare: produce stable field paths for additions, removals, and value changes.

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.

Practical guides

Each guide documents behavior the tools actually implement, including failure boundaries and privacy cautions.