Escaping encodes the characters that are not legal inside a JSON string — double quotes, backslashes, newlines, tabs and other control characters — exactly as a valid JSON string literal would represent them.

How accurate is the conversion?

Escaping uses the browser's built-in JSON.stringify and unescaping uses JSON.parse, so the result matches the official JSON specification, including \\uXXXX unicode escapes. Invalid escape sequences are reported as an error rather than guessed.

Is my text uploaded anywhere?

No — all encoding and decoding runs locally in your browser and nothing is sent to a server.

JSON Escape / Unescape

Encode text into a JSON string or decode it back.

JSON escape and unescape

Convert raw text into a valid JSON string body — encoding quotes, backslashes, newlines, tabs and control characters — or decode an escaped JSON string back to plain text, resolving \n, \t, \", \\ and \uXXXX unicode escapes.

It uses the browser’s native JSON parser and serialiser, so the result is spec-correct. Everything runs in your browser — nothing is uploaded.