Minify + escape
Produces one line you can embed in another string—for example a JSON field inside another JSON document, or a shell variable.
Make sure the source is valid JSON before escaping, so you do not embed syntax errors.
You can also load data via #data={"name":"Ada"} or #url=... It is cleared from the address bar after it is read.
Minify and handle escaping: put JSON into a string literal, or restore already-escaped text. Common when writing code snippets and config templates. Logs often show \" nested layers. This page switches between parseable JSON and text embedded in a string.
Produces one line you can embed in another string—for example a JSON field inside another JSON document, or a shell variable.
Make sure the source is valid JSON before escaping, so you do not embed syntax errors.
Copy content with \" from logs and restore parseable JSON. Useful when a gateway or SDK logged the body as a string.
After restoring, format immediately to inspect structure.
Non-JSON source raises an error so you do not get an even harder-to-debug string. The wrong mode (escape when you meant unescape) also surprises—compare against the sample.
If you only need whitespace removed and do not embed in code, use the minify page.
{"msg":"hello"}
{\"msg\":\"hello\"}
Minify only removes whitespace. This page also handles quotes and backslashes so you can embed in code.
Minified output has no newlines. Escaping mainly targets quotes and backslashes.
Each escape adds a layer of backslashes. If the result looks like all \\ , switch to “Unescape” and peel back.
It can be a starting point, but HTML still has its own quote rules. Try it in the target environment before shipping.
Multi-layer escaping is common in logs. If you are unsure how many layers, Unescape until a standard parser accepts it.