Backslash-escape the characters JSON reserves: double quotes become \", backslashes become \\, and literal newlines must become \n, since raw line breaks are not allowed inside a JSON string. A browser-based JSON escape tool converts any text into a safe JSON string literal, and unescapes it back, entirely on your own device.
Free JSON string escaper. Escape text into a safe JSON string literal, or unescape a JSON string back to raw text. Handles quotes, newlines and unicode. Private.
Open JSON String Escape / Unescape → Free toolFree JSON unescape tool. Turn an escaped JSON string back into readable text, decoding backslash escapes, quotes, newlines and unicode sequences.
Open JSON Unescape →JSON strings are delimited by double quotes, so any quote inside the text ends the string early, and the format forbids raw control characters such as literal newlines and tabs. That is why pasting a multi-line message or an HTML snippet into a JSON payload produces a parse error. The fix is escaping: quotes, backslashes and control characters are replaced with backslash sequences, and anything else can be written as a \u unicode escape.
A JSON string escaper takes your raw text, a log line, an error message, a snippet of HTML, and outputs a valid JSON string literal you can drop into a payload, a fixture or a config file. The companion unescape direction turns an escaped string from an API response or a log back into readable text with real line breaks. Both run entirely in your browser, so payload contents are never sent anywhere.
Double quotes and backslashes always, plus control characters like newlines and tabs, which become sequences such as \n and \t.
Yes. The unescape direction decodes backslash sequences back into readable text with real line breaks.
No. Escaping and unescaping run entirely in your browser.