JSON Escape and Unescape

No. Escape returns only the inner string body, so you place it between your own double quotes when building a JSON value. Likewise, unescape expects the body without the outer quotes and decodes what is inside.

Backslash and double quote are protected, and backspace, form feed, newline, carriage return and tab use their short forms backslash b, f, n, r and t. Any other control character below U+0020 becomes a backslash uXXXX sequence. Printable letters, digits, punctuation and unicode above that range pass through unchanged.

JSON allows a forward slash either plain or as backslash slash, and both are valid. This tool leaves it plain when escaping for readability, but unescape still accepts backslash slash and decodes it back to a slash.

It stops and shows an error rather than guessing. A lone trailing backslash, an unknown letter after a backslash, or a backslash u sequence without four hex digits are all rejected so you can fix the source.

Yes, on the unescape side. A four hex digit escape such as backslash u00e9 decodes to its character. On the escape side, printable unicode is kept as the literal character rather than expanded into an escape.

It escapes the text you paste as one string literal, which is exactly what you want when embedding a JSON blob inside another JSON string. It does not validate or reformat JSON structure; use a JSON formatter for that.

There is no fixed cap. Processing happens in your browser, so the practical limit is your device memory, and even long strings escape or decode almost instantly.

JSON escaping protects characters that would break a JSON string, mainly quotes, backslashes and control codes. URL encoding uses percent codes to make text safe inside a web address, a different character set and syntax. Reach for the URL encoder when the target is a link.

Yes. Everything runs locally in your browser and nothing is uploaded to a server, so sensitive strings never leave your device.