JSON Escape / Unescape

A JSON Escape / Unescape tool converts raw text into JSON-safe string content or decodes valid JSON escape sequences back to readable text. It is useful when building request bodies, embedding text in JSON, debugging parser errors, reviewing API logs, and moving values between application code and JSON fixtures.

Why JSON String Escaping Matters

When you paste a string value directly into JSON without escaping it, any double quote terminates the string prematurely, any backslash starts an unintended escape, and any raw line break makes the document invalid. JSON requires seven named escapes — \" \\ \b \f \n \r \t — plus \uXXXX Unicode escapes for control characters and optionally for non-ASCII characters. Getting even one character wrong produces a JSON syntax error that breaks every consumer of the document.

This matters most in three practical situations: (1) constructing JSON strings programmatically and needing to verify the escaping before sending, (2) copying a string value out of a JSON log or API response and needing to decode its escape sequences back to readable text, and (3) debugging a JSON parse error that originates from an unescaped character buried inside a long string value.

What ToolsSonic's JSON Escape / Unescape Workspace Provides

Bidirectional conversion with explicit modes. Choose Escape text to convert raw characters to JSON-safe sequences, or Unescape JSON string to decode sequences back to readable text. The workspace updates input/output labels, disables irrelevant controls, and runs the conversion automatically as you type.

Input format control for unescape. Competitors accept only escaped content. ToolsSonic also accepts a complete quoted JSON string literal — the kind you copy from an actual JSON document including the surrounding double quotes. This eliminates the most common user error: pasting "Hello \\"world\\" and getting a parse failure because the surrounding quotes were not expected.

Quote wrapping option. Escape mode can return either bare escaped content for embedding inside a surrounding string context, or a complete JSON string literal with surrounding double quotes for direct pasting into a JSON document. The output is the same characters either way; the wrapping makes the result immediately usable without an extra step.

Optional forward-slash escaping. The JSON specification allows but does not require \/ for forward slashes. Legacy HTML-embedding contexts and some JSONP implementations use it to prevent </script> injection. ToolsSonic exposes this as an opt-in checkbox so you can apply it for specific deployment contexts without it becoming the default.

Optional non-ASCII Unicode escaping. Keep Unicode for readable UTF-8 JSON or enable Escape non-ASCII as \u sequences to represent every character above U+007F as a four-digit \uXXXX escape. Characters outside the Basic Multilingual Plane — including most emoji — are handled as UTF-16 surrogate pairs when this mode is enabled.

Diagnostics with approximate position. When an invalid escape sequence is detected in unescape mode, the tool extracts the parser position, computes the line and column, and reports both. Competitors show a generic error message or no error at all. ToolsSonic shows exactly where the parse failed so you can fix the specific character without inspecting the entire input.

Six-stat bar. Input bytes, output bytes, total escape count, Unicode escape count, line-break count, and current mode give a precise picture of every conversion without leaving the page.

JSON Escaping vs Other Encoding Formats

JSON escaping is often confused with related but distinct encoding operations. The choice of the wrong tool produces silently wrong output in every case.

| Format | Use when | Example | |---|---|---| | JSON string escaping | Embedding text inside a JSON string | "Hello \\"world\\" | | URL percent-encoding | Encoding characters in URL components | Hello%20%22world%22 | | HTML entity encoding | Escaping characters for HTML output | Hello "world" | | Base64 encoding | Transport-safe binary or text encoding | SGVsbG8gIndvcmxkIg== | | SQL parameterization | Preventing SQL injection | Use prepared statements |

ToolsSonic provides dedicated tools for URL encoding, HTML entity encoding, and Base64, all linked from the JSON Escape / Unescape page.

Common use cases

• Escaping quotes, backslashes, tabs, and line breaks before inserting text into JSON
• Unescaping a JSON string value copied from an API response, log, or document
• Representing control characters below U+0020 with valid JSON escape sequences
• Converting Unicode characters to \u escapes for ASCII-only JSON transport
• Checking whether a complete JSON string literal parses without errors
• Preparing fixture string values and payload fragments for automated tests
• Debugging a JSON parse error caused by an unescaped character in a string
• Copying or downloading escaped text without uploading sensitive content

Why use ToolsSonic's JSON Escape / Unescape?

ToolsSonic's JSON Escape / Unescape workspace addresses the main gaps versus DevTools Daily, Code Beautify, Online JSON Tools, and Browserling: explicit escaped-content versus complete-JSON-string input formats, optional quote wrapping, optional slash escaping, optional non-ASCII Unicode escaping including UTF-16 surrogate pairs, line/column diagnostics, byte and escape count statistics, session history, copy/download, local file support, and context warnings that clearly distinguish JSON string escaping from URL encoding, HTML entities, Base64, and SQL. Every operation runs locally in the browser with no upload and no persistence.

JSON String Escape Sequence Reference

The JSON specification defines seven named escape sequences and a Unicode escape form.

| Input character | JSON escape | When it appears | |---|---|---| | Double quote " | \\" | Inside any JSON string value | | Backslash \\ | \\\\ | Any literal backslash | | Backspace | \\b | Legacy teletype control character | | Form feed | \\f | Page break control character | | Line feed (newline) | \\n | Multi-line string values | | Carriage return | \\r | Windows-style line endings | | Tab | \\t | Literal tab characters | | Control chars U+0000–U+001F | \\uXXXX | Any C0 control character | | Forward slash / | \\/ | Optional; for legacy HTML embedding | | Non-ASCII (optional) | \\uXXXX | When ASCII-only output is required |

The backslash and double quote escapes are mandatory in every JSON string context. The named control escapes (\\b \\f \\n \\r \\t) are required for those specific code points. Forward slash and non-ASCII escaping are always optional.