JSON Escape / Unescape (JSON Stringify)

Putting text inside JSON means escaping quotes, backslashes and line breaks; pulling it out means undoing that. This tool does both, and also handles the two cases that cause most confusion: turning a whole JSON document into a single escaped string (to embed it in another JSON field, an environment variable or a test fixture), and decoding JSON that was stringified once or several times, as logs and message queues often deliver it.

How to use this tool

1. Choose a mode: escape, unescape, stringify or unstringify.
2. Paste the text or JSON.
3. For escaping, decide whether to keep the surrounding quotes, escape non-ASCII characters as \uXXXX and escape / for safe use inside a <script> tag.
4. Copy the result.

Formula

" → \" \ → \\ line feed → \n tab → \t other control characters → \u00XX

This follows RFC 8259 §7, the same rules JSON.stringify uses: only the quote, the backslash and characters below U+0020 must be escaped. Everything else, including Korean, emoji and /, may appear as is; the options escape non-ASCII characters (characters above U+FFFF as surrogate pairs such as \ud83d\ude00) and / for ASCII-only or HTML-embedded output. Unescaping uses a strict parser and reports invalid escapes such as \x with their position.

Example

The sample text — He said "hi" to C:\Users\Ada, a line break, a tab and some Hangul — becomes "He said \"hi\" to C:\\Users\\Ada\nTab:\there · 한글 ✓": each quote and backslash gets a backslash, the line break becomes \n and the tab \t. Stringifying {"a": [1, 2]} gives "{\"a\":[1,2]}", which unstringifies back in one layer.