String Escape Toolkit

JSON unescape tools reverse escape sequences so \n, \", and \\ become real newlines, quotes, and backslashes again. Search intent for "unescape json" and "json unescape" usually comes from logs, API dumps, or ticket paste where a string was serialized twice and is unreadable until you unwind it.

Embedding arbitrary text inside JSON, JavaScript, or SQL string literals requires escaping quotes, backslashes, and control characters. A single unescaped newline breaks JSON.parse in browsers and causes subtle production errors when configs are hand-edited.

Double-escaped JSON is common in observability pipelines: a logger stringifies an object, then a transport wraps that string in another JSON field. The result looks like \"key\":\"value\" with extra backslashes. Unescape once, then parse; if parse still fails, unescape again carefully and stop when the payload is valid JSON.

Unicode escape sequences (\uXXXX) represent characters outside ASCII or characters that break delimiters. Over-escaping produces readable but bloated output; under-escaping yields parse failures. Always round-trip through JSON.parse after unescaping user-supplied content so you catch truncated surrogate pairs early.

Common pitfalls: treating URL-encoded %22 as JSON escapes; copying only the inner quoted fragment without its surrounding quotes; and unescaping HTML entities (") when the source is JSON, not markup. Pick the tool mode that matches the encoding you actually have.

Escape modes remain useful when you need to paste a multi-line secret into a JSON fixture or shell-safe literal. Prefer generating escapes locally instead of hand-editing backslashes in a hurry during an incident.

When should you use these utilities? Debugging double-encoded webhook bodies, cleaning CI log excerpts, and preparing fixture strings for unit tests. Privacy note: unescaped payloads may contain tokens or PII. DevPipe processes them in the browser so raw paste content is not uploaded to a remote beautifier.