What characters need to be escaped in JSON?

JSON requires escaping: double quotes (\" for "), backslashes (\\ for \), forward slashes (\/ for /, optional but common), and control characters (\n for newline, \t for tab, \r for carriage return). Unicode characters can be escaped as \uXXXX. Example: "He said \"Hello\"" becomes valid JSON. Without escaping, quotes would break JSON structure. Escaping ensures special characters are treated as data, not syntax.

Why do I need to escape JSON for logging or config files?

Embedding JSON inside JSON, logs, or config files creates nesting conflicts. Example: storing API response JSON as a string value requires escaping all quotes and backslashes. Without escaping: {"response": {"name": "John"}} breaks the outer JSON. With escaping: {"response": "{\"name\":\"John\"}"}. Escaped JSON treats the inner JSON as a plain string value, preventing parsing errors.

What is the difference between JSON escaping and URL encoding?

JSON escaping uses backslashes for special characters (\" for quotes). URL encoding uses percent-encoding (%20 for space, %22 for quotes). JSON escaping is for embedding strings in JSON. URL encoding is for passing JSON in query parameters (e.g., ?data={"name":"John"} becomes ?data=%7B%22name%22%3A%22John%22%7D). Use JSON escaping for JSON-inside-JSON. Use URL encoding for JSON-in-URLs. They solve different problems.

Can I escape entire JSON objects or only strings?

Escaping applies to JSON strings (text values). To escape an entire JSON object, first stringify it (convert to a JSON string), then escape that string. Example: object {"name": "John"} → stringified "{\"name\":\"John\"}" → escaped as a value in another JSON: {"data": "{\"name\":\"John\"}"}. You are essentially nesting JSON by treating inner JSON as a string value.

Why does my unescaped JSON still look weird?

Common issues: 1) Double-escaping (escaping already-escaped JSON creates \\\" instead of \"). Solution: unescape once, verify, then use. 2) Mixed encoding (JSON escaping + URL encoding). Solution: decode URL first, then unescape JSON. 3) Invalid escape sequences (\q is invalid; only \", \\, \/, \n, \t, \r, \uXXXX are valid). Validate JSON after unescaping using a JSON parser.

When should I use Base64 encoding vs JSON escaping?

JSON escaping: when embedding JSON strings in other JSON (config files, logs, nested API responses). Base64 encoding: when transmitting binary data (images, PDFs) or JSON through systems that only accept alphanumeric text (email, XML attributes, some legacy APIs). Base64 is not human-readable; JSON escaping maintains readability. Choose based on use case: nested JSON → escape; binary data or restrictive systems → Base64.

JSON Escape/Unescape - Encode & Decode Online

How to Escape/Unescape JSON

Paste your JSON or escaped string into the input area
Select escape or unescape mode
Choose encoding type (JSON, Base64, or URL)
Copy the escaped or unescaped output

Why Use Our JSON Escape Tool?

JSON Escaping: Escape quotes, backslashes, and special characters
Base64 Encoding: Convert JSON to Base64 for safe text transmission
URL Encoding: Encode JSON for use in URL parameters
Bidirectional: Both escape and unescape in one tool
Validation: Checks JSON syntax before escaping
100% Free: No limits on string length or usage

When to Escape JSON Strings

JSON escaping converts special characters like quotes and backslashes into escape sequences (\", \\) so the JSON can be safely embedded within other JSON or strings. Without escaping, quotes would terminate the string prematurely.

Common scenario: You have a JSON object that contains another JSON string as a property value. The inner JSON needs escaping so its quotes don't conflict with the outer JSON structure. Example: {"config": "{\"name\":\"value\"}"}.

Use cases: Storing JSON as string values in databases, embedding JSON in HTML attributes or JavaScript strings, sending JSON as part of another JSON payload, and preparing JSON for transmission through systems that don't natively support JSON structure.

Privacy & Security

All escaping and encoding happens locally in your browser. Your JSON strings are never uploaded to servers, stored, or logged. The processing uses JavaScript, keeping your data completely private.