Unescaping Double-Stringified JSON and Escaped Log Payloads
If you have ever pulled a JSON payload out of a PostgreSQL text column, CloudWatch log, or Kafka dead-letter queue, you have probably seen strings packed with backslashes like {\"id\":123}. Reading or editing escaped JSON by eye is nearly impossible.
Why does this error occur?
Escaped JSON happens when an already serialized JSON object is serialized a second time as a plain string—often called double-stringification. Logging libraries, webhook queues, and legacy APIs frequently wrap JSON payloads inside string fields, escaping every double quote as \" and every newline as \n.
When you paste that string into a standard formatter, it treats the whole block as a single opaque string literal rather than a structured JSON object.
How is it solved?
Paste your escaped JSON string into DataPurge above with the Unescape (\") option enabled. The sanitizer unwraps outer string quotes, decodes \", \\, \n, and \t escape sequences, and then parses and pretty-prints the underlying JSON structure.
In one step, a wall of unreadable backslash-heavy log text turns into a cleanly indented, syntax-verified JSON document.
Why should you use 100% Client-Side (Zero-Telemetry)?
Database dumps, webhook logs, and queue payloads are the exact places where customer names, payment metadata, and authentication headers live. Pasting production logs into an ad-supported online unescaper risks exposing sensitive user records.
DataPurge performs all string unescaping and JSON parsing locally inside your browser tab with zero server requests.