JSON String Escape and Unescape guide
Convert plain text to JSON string content or decode valid JSON escape sequences back into text.
What this tool does
JSON String Escape and Unescape performs the string-level transformation defined by JSON syntax. Escape mode converts quotation marks, backslashes, control characters, tabs, carriage returns, and line breaks into a form that can appear between the double quotes of a JSON string. It returns the inner string content without adding surrounding quotes.
Unescape mode accepts escaped content with or without surrounding double quotes. It validates the value through the JSON parser and restores the represented Unicode string. Sequences such as \n, \t, \\, \", and valid \uXXXX escapes are interpreted according to JSON rules.
This tool handles one string value, not a complete object or array. Use the JSON Formatter for full JSON documents. It also does not escape content for HTML, URLs, shell commands, SQL, regular expressions, or JavaScript source contexts, because each destination has different safety requirements.
How to use it
- Choose Escape string or Unescape string.
- Paste the source text or escaped JSON content.
- Select the conversion button.
- Review whitespace and line breaks in the result.
- Copy the output into the intended JSON workflow.
When inserting escaped content manually into a JSON document, add the surrounding double quotes and ensure the surrounding object syntax is valid.
Benefits
- Uses native JSON serialization and parsing behavior
- Preserves Unicode characters and meaningful whitespace
- Accepts unescape input with optional surrounding quotes
- Reports malformed escape sequences instead of guessing
- Keeps all text within the browser
Context and safety notes
Escaping makes a string syntactically representable in JSON; it does not make untrusted content safe in every application. After parsing JSON, output must still be handled appropriately for its destination. For example, inserting a parsed value into HTML with an unsafe API can still create a cross-site scripting problem.
Unicode can be represented directly or with escape sequences, so two JSON strings can look different while decoding to the same value. Conversely, invisible characters and different Unicode normalization forms can produce text that looks similar but is not byte-for-byte identical.
The practical notice is to validate the complete JSON document and apply destination-specific security controls rather than treating string escaping as universal sanitization.
JSON escape and unescape example
Suppose the source contains Line one, a line break, and "quoted". Escape mode returns Line one\n\"quoted\", which can be placed between the surrounding quotes of a JSON string. Unescape mode reverses those valid escape sequences and restores the line break and quotation marks. The result is string content rather than a complete JSON object.
Use the JSON Formatter to validate, format, or minify a complete object or array. After parsing a document, the JSON Property Path Inspector can resolve a specific nested value without confusing JSON string escaping with object navigation.