What is JSON Escaping?

When JSON is embedded inside a string (like in a database field or API response), special characters must be escaped with backslashes. This tool converts those escaped strings back to readable, valid JSON.

Example

Escaped JSON string:

"{\\"name\\":\\"John\\",\\"age\\":30}"

Unescaped JSON:

{
  "name": "John",
  "age": 30
}

Common Escape Sequences

Why Does This Happen?

JSON gets double-escaped in several common scenarios:

• Database storage — JSON stored as a text column needs escaping
• API responses — JSON embedded in another JSON string
• Logging — Log systems often escape JSON for single-line output
• Message queues — Kafka, RabbitMQ often stringify JSON payloads
• Environment variables — Complex config stored as escaped strings

Programmatic Solutions

JavaScript

// Unescape a JSON string
const escaped = '{"name":"John","age":30}';
const unescaped = JSON.parse(escaped);

// If double-escaped (string within string)
const doubleEscaped = '"{\"name\":\"John\"}"';
const parsed = JSON.parse(JSON.parse(doubleEscaped));

Python

import json

# Unescape a JSON string
escaped = r'{"name":"John","age":30}'
unescaped = json.loads(escaped)

# If double-escaped
double_escaped = r'"{"name":"John"}"'
parsed = json.loads(json.loads(double_escaped))

Command Line (with jq)

# Parse escaped JSON
echo '"{\"name\":\"John\"}"' | jq -r '.' | jq '.'

Escape Mode

This tool also works in reverse. Use Escape mode to convert JSON into an escaped string for embedding in:

• JavaScript string literals
• JSON string values
• Database text fields
• Environment variables

Pro Tips

• 💡 Multiple layers — If one unescape doesn't work, the JSON might be double or triple escaped. Run it multiple times.
• 💡 Check the quotes — Properly escaped JSON strings are usually wrapped in outer quotes.
• 💡 Validate after — Use the JSON Validator to ensure the unescaped result is valid JSON.

Related Tools

• JSON Escape — Convert raw text to escaped JSON strings
• JSON Validator — Validate your unescaped JSON
• JSON Stringify — Similar escaping functionality
• JSON Minify — Compact JSON for storage

Common Mistakes & Pro Tips

• Unescaping reverses escape sequences back to raw characters — It turns \n back into a real newline, \" back into a quote, and \\ back into a single backslash, recovering the original text that was placed inside a JSON string. It is the exact inverse of escaping a string's content.
• Invalid escape sequences cause failure — JSON only permits the escapes \" \\ \/ \b \f \n \r \t and \uXXXX. A stray backslash before any other character, such as \x or \q, is invalid and a strict unescaper will reject it rather than guess your intent.
• Watch the layer count to avoid over- or under-unescaping — If a payload was escaped twice, one unescape pass leaves a layer of backslashes behind; unescape exactly as many times as it was escaped. Over-unescaping a single-escaped string can corrupt legitimate backslashes that were meant to remain.
• \uXXXX requires four hex digits — A unicode escape must be a backslash, a lowercase u, and exactly four hexadecimal digits, like \u0041 for 'A'. Fewer digits or non-hex characters make the sequence invalid, and surrogate pairs (😀) must appear together to form characters above U+FFFF.
• Unescaping content is not parsing the document — Unescaping operates on the characters inside one string; it does not interpret JSON structure like braces or arrays. If you have a full stringified JSON document, parse it (or stringify-then-parse) rather than only unescaping, or you may get text that is still a JSON literal.