JSON Escape / Unescape
Escape text so it's safe to embed inside a JSON string, and unescape it back.
Putting text inside a JSON string
To place arbitrary text inside a JSON string value, certain characters must be escaped — quotes, backslashes, newlines and the like — or they break the JSON. This escapes your text so it can sit safely as a JSON string, and reverses the process to recover the original. It is the everyday need when you are embedding a block of text, or a nested chunk of JSON, into a JSON field.
Paste text to escape it, or an escaped string to unescape it.
The nested-JSON case
A common and confusing situation is JSON inside JSON — a field whose value is itself a JSON document, stored as an escaped string. That is where you see the tell-tale backslash-quotes piling up. Escaping handles putting it in; unescaping recovers the readable inner JSON so you can actually work with it. Distinguish this from formatting: escaping is about making text safe to embed, formatting is about laying JSON out to read. Here the job is purely the safe embedding.
Frequently asked questions
What does escaping do to my text?
It backslash-escapes characters like quotes, backslashes and newlines so the text can sit safely inside a JSON string.
Why do I see backslash-quotes in some JSON?
That is JSON stored inside a JSON string — nested and escaped. Unescaping recovers the readable inner JSON.
Is my text uploaded?
No. The escaping happens in your browser.