JSON Escape / Unescape
Escape and unescape JSON strings
About the JSON Escape / Unescape
Embedding one piece of JSON inside another — or stuffing a multi-line string into a single JSON value — breaks the moment a quote or newline is taken literally. JSON Escape converts a raw string into its safely escaped form, and reverses the process when you need the original back.
Developers hit this whenever a string has to travel through a JSON field that is itself a string: storing a JSON snippet as a value, pasting a code block into a config, or preparing a multi-line message for an API. Escape mode turns the dangerous characters into their backslash equivalents; unescape mode restores them so you can read the content as it was written.
How to Use the JSON Escape / Unescape
- Choose your direction with the Escape / Unescape toggle.
- In Escape mode, paste the raw string you want to make JSON-safe; in Unescape mode, paste the escaped string.
- Read the converted output as you type — quotes, backslashes, and whitespace characters are handled automatically.
- Click Copy to grab the result for your JSON value or your editor.
Why Use ToolForge’s JSON Escape / Unescape
- It handles the full set of characters that break JSON strings — quotes, backslashes, newlines, carriage returns, tabs, form feeds, and backspaces — not just quotes.
- The single Escape/Unescape toggle works both directions, so you can round-trip a value without switching tools.
- It processes any input without imposing a format, so you can escape a whole code block or a one-line string equally.
- Conversion is local to your browser, keeping whatever you paste private.
Frequently Asked Questions
When do I need to escape a string for JSON?
Whenever a string value contains characters that have special meaning in JSON — most commonly double quotes and backslashes, or literal line breaks and tabs. Escaping them lets the string sit safely inside a JSON value without breaking the surrounding structure.
What characters does escaping affect?
Backslash, double quote, newline, carriage return, tab, form feed, and backspace are converted to their backslash escape sequences (\\, \", \n, \r, \t, \f, \b). Unescape mode converts those sequences back into the original characters.
Is escaping the same as encoding?
No. Escaping prepares a string for safe inclusion inside JSON by backslash-escaping special characters. Encoding schemes like Base64 or URL encoding serve different transport needs — use a dedicated encoder for those.
Why did my escaped string come back wrong after unescaping?
Unescape expects input that was actually escaped — sequences like \n and \". If you unescape a string that contains a literal backslash that was never an escape sequence, the result can differ from what you expect. Make sure you are reversing genuinely escaped text, not raw input with stray backslashes.
