How to Escape a JSON String Online (Free Tool + Complete Guide)

To escape a JSON string, replace every double quote with \", every backslash with \\, and every newline with \n. Doing this by hand for anything longer than a few words is error-prone — this guide shows the fastest way to do it online for free, explains every required escape sequence, and covers common mistakes like a trailing backslash or an unescaped quote breaking your JSON.

What is JSON string escaping?

A JSON string is always wrapped in double quotes: "hello world". The problem is that some characters have special meaning inside those quotes. If your text itself contains a double quote, a backslash, or a newline, the JSON parser can't tell where your string ends and where the surrounding structure begins — so it throws a parse error.

Escaping solves this by replacing those problematic characters with safe two-character sequences that start with a backslash. For example:

Raw text:
He said "hello"
and left.

Escaped (ready to put between JSON quotes):
He said \"hello\"\nand left.

Put that between the double quotes of a JSON field and it is a valid JSON string: "He said \"hello\"\nand left."

Which characters must be escaped?

Per RFC 8259 (the JSON specification), two characters are mandatory to escape, and a whole class of control characters must also be escaped:

Every other Unicode character — letters, digits, emoji, non-ASCII scripts — may appear unescaped inside a JSON string.

How to escape a JSON string online (step by step)

1. Open the JSON String Escape tool. It loads instantly with no signup required.
2. Paste your raw text into the Input field. This can be a SQL query, an error message, a code snippet, or any text containing quotes or backslashes.
3. Click Escape. The tool runs JSON.stringify() internally and strips the surrounding double quotes, giving you the inner escaped string.
4. Click Copy Output to copy the result to your clipboard, then paste it between the double quotes of your JSON field.

To reverse the process — turning an already-escaped string back into plain text — paste the escaped string and click Unescape instead.

Worked example

Suppose you want to store this SQL query as a JSON string value:

SELECT * FROM users WHERE name = "Alice" AND active = 1;

Paste it into the tool and click Escape. The output:

SELECT * FROM users WHERE name = \"Alice\" AND active = 1;

Now you can safely place this between quotes in your JSON document:

{
  "query": "SELECT * FROM users WHERE name = \"Alice\" AND active = 1;"
}

Common use cases

• SQL or code in a JSON field — queries and code snippets almost always contain double quotes and newlines that must be escaped.
• Embedding JSON inside JSON — storing a JSON payload as a string value in another JSON document requires all the inner quotes and braces to be escaped.
• Log lines and error messages — multi-line stack traces need \n to fit on a single JSON string.
• Hardcoding a string in source code — pasting any text that contains quotes into a JSON config or a string literal requires escaping first.
• API payloads — body text from a form, a user comment, or a document that is being sent as a JSON string field.

Escaping in JavaScript, Python, and other languages

You don't always need a tool — every language with a JSON library can escape a string for you:

JavaScript

const raw = 'He said "hello"\nand left.';
// JSON.stringify wraps in quotes — slice removes them
const escaped = JSON.stringify(raw).slice(1, -1);
// → He said \"hello\"\nand left.

Python

import json

raw = 'He said "hello"\nand left.'
# json.dumps wraps in quotes — strip them
escaped = json.dumps(raw)[1:-1]
# → He said \"hello\"\nand left.

Java

import com.fasterxml.jackson.databind.ObjectMapper;

String raw = "He said \"hello\"\nand left.";
ObjectMapper mapper = new ObjectMapper();
// writeValueAsString wraps in quotes — strip them
String escaped = mapper.writeValueAsString(raw);
escaped = escaped.substring(1, escaped.length() - 1);

Using a library is always safer than writing your own replacement loop — libraries handle edge cases like Unicode control characters and surrogate pairs that are easy to miss manually.

Common mistakes

Trailing backslash

If your escaped string ends with a lone \, the JSON parser sees it as the start of an escape sequence and throws an error. This happens when you copy only part of an escaped string. Make sure the final character is not a single backslash.

Unescaped quote inside the string

Pasting text that contains " directly into a JSON value without escaping it causes the parser to think the string ended there. The error message is usually Unexpected token or Expected comma or closing brace.

Real newlines inside a JSON string

A literal line break inside a JSON string is invalid. Multi-line text must use \n (and \r\n on Windows). Many editors silently paste a real newline when you hit Enter inside a JSON value, which then fails validation.

Double-escaping

If you run the escape tool twice on the same string, you get \\\" instead of \" — the backslashes themselves get escaped. Always start from the raw, unescaped text.

JSON string escaping vs URL encoding

These two are often confused because both convert special characters into a safe representation. The difference is the target format:

They are not interchangeable. If you need to put text into a URL query string, use the URL Encoder. If you need to encode binary data, use the Base64 Encoder. If you need text inside a JSON string, use the JSON String Escape tool.