Decode one layer of JSON string escaping or escape Unicode text as a complete JSON string literal.
LOCAL FILE CONVERSION
Decode one layer of JSON string escaping or escape Unicode text as a complete JSON string literal.
Drop one UTF-8 source file · Up to 200 KB · No uploadLOCAL INPUT
1 lines · 28 characters · 28 bytes
COMPUTED RESULT
0 output bytes ·
Choose a complete quoted JSON string, content without outer quotes, or plain-text escape mode. Exactly one layer is decoded. Objects, invalid escapes, raw controls and lone UTF-16 surrogates are rejected.
Processing uses your browser memory. Inputs are not included in page analytics. Text tools accept up to 200,000 UTF-8 bytes unless a tighter limit is stated. Worker operations time out after 45 seconds and can be cancelled. Clipboard and downloads require an explicit action.
Enter your values locally; no inputs are uploaded.
Check validation feedback before reviewing the browser-generated result.
Review the explanation, copy supported outputs or reset the workspace.
Each JSON escape is decoded exactly once. For example, a JSON string containing an escaped backslash followed by n produces the literal two characters backslash and n, rather than recursively creating a newline.
Choose a complete quoted JSON string, content without outer quotes, or plain-text escape mode. Exactly one layer is decoded. Objects, invalid escapes, raw controls and lone UTF-16 surrogates are rejected.
Processing takes place locally in browser memory. Inputs are not sent to a processing service, persisted by this tool or included in analytics. Ordinary page requests may still be logged. Clipboard and downloads require explicit actions.
Each JSON escape is decoded exactly once. For example, a JSON string containing an escaped backslash followed by n produces the literal two characters backslash and n, rather than recursively creating a newline.
Complete literal mode expects the outer double quotes. Content mode expects the escaped content without outer quotes. Escape mode accepts plain Unicode text and returns a complete quoted JSON string.
No. Literal mode requires a JSON string value. Objects, arrays, numbers, booleans and null are rejected instead of being converted to misleading text.
A lone UTF-16 surrogate is not a Unicode scalar value. Rejecting it avoids silently replacing malformed Unicode during later UTF-8 encoding or downloads. Valid surrogate pairs decode normally.
No. JSON string syntax requires escaped controls such as backslash-n. Plain-text escape mode can accept an actual newline and encode it correctly.
Yes. Use the complete literal consisting of two double quotes, or empty content in content-only mode. Empty literal input without quotes displays guidance rather than inventing a JSON value.