Tool

JSON Utils

Recursively unwrap values that are JSON-encoded inside string fields.

Result

Detected format details will appear after unwrap.

No transformed output yet.

Tree preview appears after unwrap. Unwrap JSON to enable tree folding controls.

What JSON Utils is for

Use this tool when API responses, logs, or message payloads contain JSON that has been encoded again inside string fields. It unwraps those layers so you can inspect the real structure more quickly.

It is especially useful for debugging nested webhook payloads, queue messages, and copied log samples where arrays, booleans, or objects arrive as escaped strings.

Typical input and expected output

A representative input is a copied payload where one field contains another JSON document as a quoted string.

{"payload":"{\"flag\":\"true\",\"items\":\"[1,2,3]\"}","source":"queue"}

After unwrapping, booleans, arrays, and nested objects become normal JSON values that are easier to inspect or diff.

{
  "payload": {
    "flag": true,
    "items": [
      1,
      2,
      3
    ]
  },
  "source": "queue"
}

How it behaves

Processing stays in the browser. The tool attempts deterministic recursive unwrapping, preserves plain strings when they are not valid JSON, and shows a tree view so you can inspect keys, values, and paths after parsing.

Good fits and non-goals

This tool is a good fit for webhook payloads, queue messages, copied browser logs, and test fixtures that contain valid JSON wrapped inside more JSON. It helps when the structure is real but hard to read.

It is not a schema validator, and it does not try to repair arbitrarily broken text. If a field is not valid JSON, the tool leaves that plain string alone instead of guessing how to rewrite it.

Common misunderstandings

Unwrapping is not the same as flattening. The goal is to recover the original nested structure, not to transform the payload into a new schema.

If you paste mixed text that is only partly JSON, the tool will only unwrap the parts that parse cleanly. That conservative behavior is intentional because over-transforming debugging data is harder to trust.

Privacy and usage notes

Input is handled client-side for the core transformation flow. You should still remove secrets before pasting production data into any browser tool, especially when working with logs or customer payloads.