How to use the JSON Escape Tool.
JSON string escaping must handle quotes, backslashes and control characters. Use a serializer rather than a sequence of improvised substitutions.
Make the workflow fit your task.
Treat the input as a string value and use a JSON serializer to produce valid quoting and escapes. Distinguish a complete JSON document from a string embedded inside another document. Parse the result back to confirm that the original characters are recovered.
- What you provide
- String content.
- What you get
- Correctly escaped JSON string and inverse decoding.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Encode the text hello followed by one line break and then world as a complete JSON string literal. Preserve the line break when parsed back.
Completed example
"hello\nworld" The JSON source contains a backslash followed by n, not an unescaped newline inside the quotes. Parsing this string returns the original text with one line break.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should the surrounding quotation marks be included in an escaped JSON string?
Include them when producing a complete JSON string literal. Omit them only when the destination specifically expects the interior representation.
Why do backslashes multiply when the string passes through another layer?
Each serialization layer may escape the previous representation. Track whether you are handling original text, JSON text or a displayed code string.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑