What JSON Escape helps you do
Run JSON string escaping on your text, or parse a quoted JSON string back into plain text. It is the precise escape used by JSON, so the output can be embedded directly in JSON values. The unescape direction expects a quoted string, not an object.
JSON escaping runs entirely in your browser and is not sent to Haivix.
How it works
These tools transform characters rather than meaning. Some map letters to other Unicode glyphs, some insert combining marks, and some encode bytes into a text-safe representation. The result is still text, so it can be copied into a document or chat, but the visual effect depends on the font and platform that renders it. Nothing is uploaded, and some transformations are not reversible; keep the original when that matters. The output is a snapshot of the pasted text, so changing the source afterwards does not update it.
How to use JSON Escape
- Paste plain text to escape, or a quoted JSON string to unescape.
- Choose the direction.
- Check the outer quotes and a quote inside the text.
- Copy the escaped or unescaped result.
When to use it
- Prepare a string to place inside a JSON field.
- Read a JSON-escaped string extracted from an API response.
- Turn multi-line text into a single valid JSON string.
- Prepare a value for a config or fixture.
- Inspect how a control character is represented in JSON.
- Clean up a string copied from a log line that escaped it.
When not to use it
- Do not use it to build or validate a whole JSON object.
- Do not paste a JSON object into the unescape direction.
- Do not use it as a substitute for a JSON formatter.
Example
A double quote inside the text becomes backslash-quote when escaped, which is valid inside a JSON string. A newline becomes backslash-n rather than a literal line break. In the other direction, a quoted value such as "hello" returns hello without the quotes.
What you can do with JSON Escape
- Escape a plain string as a JSON string value.
- Unescape a quoted JSON string.
- Escape quotes, backslashes and control characters.
- Turn multi-line text into one valid JSON string.
- Copy the escaped or unescaped result.
- Run the conversion locally with no upload.
Example: preview the transformation before sharing
Paste a short sample and inspect the result in the place it will be used. A fancy style that looks right in one app can show as boxes or plain letters in another.
Check whether the transformation is reversible. Escapes, Morse and binary can be decoded; styled letters and Zalgo usually cannot be restored perfectly.
Copy the result and keep the original if the text will be edited later or read by a screen reader. Styled characters are separate code points, so a search for the plain word will not find them.
If the text is for accessibility, prefer plain characters. A screen reader may read styled letters one by one or skip the combining marks entirely.
If the output will go into a field with a character limit, count the characters before and after. Styled letters often use more code points than the plain form, so a caption that fit before may no longer fit.
For a reversible encoding, test the round trip on a short sample. Encode, decode, and compare; if the result differs, the tool is not the right one for that data.
Keep the plain source in a note next to the styled version. When the effect stops rendering or a reader cannot parse it, the plain text is the only accessible fallback.
What to know before you start
- It operates on a single string value and does not build or validate a whole JSON object.
- Pasting an object rather than a quoted string is not supported; use a JSON formatter for that.
- The escaped output includes the enclosing quotes.
- It does not pretty-print or minify a document.
Common mistakes
- Pasting an object rather than a quoted string into the unescape direction.
- Forgetting that the escaped result includes the outer quotes.
- Using slash escaping instead of JSON escaping for a JSON value.
- Expecting the tool to validate the surrounding document.
Troubleshooting
If unescaping fails, the input may not be a valid quoted JSON string.
If the output includes quotes you did not expect, the escape direction wraps the value.
If a newline remains literal, it was not escaped by the source.
If the value will not parse in your application, check the surrounding JSON separately.
Related standards and documentation
- Styled letters are separate Unicode code points, not formatting; search and spell-check may not recognize them.
- Combining marks attach to the preceding character and can affect cursor movement and accessibility.
- Base64, binary and escapes are encodings, not encryption.
- Character counts can change after a transformation because Unicode code points differ from visible glyphs.
- Preview in the destination app.
- Some styles are one-way.
- Keep the original for editing.
- Prefer plain text for accessibility.