Hide JSON Strings (Escape Codes)

Sometimes a string needs to travel where its characters are not welcome. A JSON payload nested inside another JSON document needs every inner quote escaped. A log line must stay on one line even when the value contains newlines. An old mainframe interface only accepts ASCII, and your payload contains emoji and Chinese text. Leave those strings as they are and the transport breaks, the parser fails, or the log ruins itself.

Hide JSON Strings rewrites the strings for you. Escape mode turns control characters into \n, \t, \r, \" and \\ sequences, and — optionally — every non-ASCII character into a \uXXXX code, producing a document that is pure ASCII and still valid JSON. Apply it to values only or to keys as well. Unescape mode performs the exact reverse, restoring readable text byte for byte. For the common case where your JSON is valid but the browser output already looks escaped, the pretty-print step keeps the result tidy. All client-side, nothing uploaded.

• Escape (hide) direction: Control characters become \n, \t, \r, \" and \\ sequences inside string values.
• Unescape (reveal) direction: Escape codes convert back to real characters, byte for byte.
• Unicode mode: Every non-ASCII character becomes a \uXXXX escape — the entire document becomes pure ASCII.
• Keys toggle: Apply escaping to values only, or to values and keys together for ASCII-only transport.
• ASCII-only flag: After escaping, the tool reports whether the output contains any non-ASCII characters at all.
• Pretty-print control: Keep the JSON readable while hidden, or output compact.
• Live conversion: Output updates as you type, in both directions.
• Copy and download: Export the hidden or revealed document in one click.
• Private: All processing is client-side; nothing is uploaded.

1. Paste your JSON into the input pane.
2. Choose the direction: Escape to hide readable characters as codes, Unescape to reveal codes as characters.
3. Set the options: unicode mode for pure-ASCII output, the keys toggle, and pretty-print.
4. Check the ASCII flag to confirm the document is fully ASCII when that matters.
5. Copy or download the result.

Example 1 — JSON inside JSON. A webhook payload must embed another API response as a string field. Escape mode rewrites every inner quote and newline as \" and \n, and the embedded document nests correctly — no hand-escaping, no syntax break.

Example 2 — Line-oriented logging. A log pipeline splits records on newlines, but a note field contains real line breaks that corrupt every record. Escape mode turns them into \n text; the log stays one line per record and unescapes cleanly on read.

Example 3 — ASCII-only gateway. A legacy interface rejects non-ASCII bytes. Unicode mode converts every accented name and emoji into \uXXXX sequences, producing a document that passes through untouched and decodes back to the original text.

Example 4 — Source code embedding. A config with newlines and quotes goes into a single-quoted shell variable or a string literal. Escape mode produces the escaped form, the code compiles, and unescape mode restores the original for inspection.

• Strings survive hostile transports: Escape codes keep payloads intact through JSON nesting, logs and ASCII-only systems.
• Fully reversible: The unescape direction restores the original text byte for byte — nothing is lost in hiding.
• Valid JSON throughout: Escaped output is still parseable, so downstream consumers never break.
• ASCII guarantee on demand: The unicode option and the ASCII flag settle the question in seconds.
• Private and instant: Client-side processing with live preview and no uploads.