Use the free JSON String Escaper below: your data never leaves your browser — all work happens on your device, and nothing is uploaded to any server.
Why text breaks JSON
JSON looks simple: keys and values wrapped in quotes, separated by commas. But the moment your text contains a double quote, a backslash, a new line or a tab, a hand-built JSON string falls apart. A quote inside the value ends the string early. A new line inside the value is simply not allowed. A backslash starts an escape the parser does not expect. The result is an error message that points at a line you thought was fine.
This is a common bug when people build JSON by joining strings together: a configuration file, a test payload, a snippet for an API request, a seed value for a database. The text itself is innocent; it just contains characters that JSON treats as structure. The fix is escaping: replacing each special character with a safe sequence that means the same thing when the JSON is read back.
What escaping actually does
Escaping follows a small set of rules. A double quote becomes backslash-quote, so the parser knows it is content rather than the end of the string. A backslash becomes two backslashes. A new line becomes backslash-n, a carriage return becomes backslash-r, and a tab becomes backslash-t. Other control characters become backslash-u followed by four hex digits. Everything else, including accented letters and emoji, passes through unchanged.
This tool uses the browser’s own JSON encoder, the same routine that real applications use, so the output follows the standard exactly. That matters more than it sounds. A hand-rolled escaper often forgets one case: the backspace, the form feed, or a control character hiding in pasted text. The built-in encoder forgets nothing, and the result can be dropped straight into a JSON document and parsed without errors.
How to use this tool
Paste your text and press the button. By default the result includes the surrounding double quotes, so it is a complete JSON string you can paste as a value. Uncheck that option if you only need the escaped content to place inside quotes you already have. The character counts show how much the text grew, which is a useful hint when you are working with size limits on a field or a request body.
Typical uses include building test data for an API, embedding a message inside a JSON configuration, preparing a code sample, or fixing a broken payload you received from somewhere else. If you paste a block of text that contains quotes and line breaks, the escaped version is immediately safe to use, and you can verify it by pasting it into any JSON validator.
Escaping is not the same as encoding
People sometimes confuse escaping with other transformations. Escaping does not change the meaning of your text; it only changes how it is written so a parser reads it correctly. It is not encryption, not compression and not a way to hide content. The escaped string, once parsed, gives back exactly the text you started with, character for character.
It is also worth remembering that escaping is one-way only in the sense that you must unescape to read the text again, but every JSON parser does that automatically. So the escaped version is safe to store, send and log, and the original text reappears the moment anyone parses the JSON. One click here saves a debugging session later.
A final tip: when you paste escaped text into a larger JSON document, keep an eye on commas and braces around it. The escaped string itself is safe, but a missing comma after it will still break the document, and the error will point at the line after your string rather than at the string itself. Validate the whole document, not just the escaped part, and you will catch those slips at once.