Escaping runs entirely in your browser — nothing is uploaded.
Escape and unescape JSON strings online, free. JSON string escaping makes raw text safe to place between the double quotes of a JSON value: the double quote, backslash, and control characters are replaced with backslash sequences per RFC 8259. This tool escapes text into a valid JSON string body — or unescapes one back to plain text — using the browser's native JSON engine, entirely on your device.
Escaping and unescaping use JavaScript's native JSON engine and follow RFC 8259 exactly, so \n, \t and \uXXXX control characters round-trip correctly. 100% free, no registration, and complete privacy — everything runs locally in your browser, so your data never touches a server.
Convert raw text into a JSON-safe string and back, with one click in either direction.
Escapes the double quote, backslash and U+0000–U+001F control characters, using \n, \t, \r and \uXXXX forms.
Runs on the browser's native JSON engine — no upload, no wait.
Your text is processed locally and never sent anywhere — safe for tokens and secrets.
Prefix it with a backslash: a literal " becomes \". JSON strings are delimited by double quotes, so any double quote inside the value must be escaped as \" or the parser will end the string early. This tool does it for you — paste the text and click Escape.
Per RFC 8259, JSON requires escaping the double quote (\"), backslash (\\), and the control characters U+0000–U+001F. Common ones have short forms: \n (newline), \r (carriage return), \t (tab), \b (backspace), \f (form feed). Any other control character is escaped as a \uXXXX hex sequence.
Escaping converts raw text into a form that is safe to place between the quotes of a JSON string (e.g. a newline becomes \n). Unescaping reverses it — turning \n back into an actual newline. Use Escape when building JSON by hand; use Unescape to read a value copied out of a JSON document.
No. All escaping and unescaping runs locally in your browser using JavaScript's native JSON engine — nothing is uploaded, logged, or stored. It is safe for API keys, tokens, and other sensitive strings.
Unescape expects a valid JSON string body — for example \u0041 or \n. If the input contains a lone backslash or an incomplete \u sequence it is not valid JSON and will fail. Re-check that every backslash starts a legal escape sequence.
We use cookies for analytics and personalized ads to help keep these tools free. Until you accept, ads stay non-personalized and analytics cookies are off. See our Privacy Policy.