Encoding

JSON Unescape

Decode escaped JSON text back to readable form — newlines, quotes, and \uXXXX sequences included.

Decoding runs locally in your browser. Nothing is uploaded, logged, or stored.

0 chars
0 chars

How to use

  1. Paste the escaped text into the input panel (without surrounding quotes).
  2. Click Unescape — \n becomes a newline, \" a quote, \uXXXX the matching character.
  3. Copy the readable result.

How it works

The tool interprets your text exactly as a JSON parser reads the inside of a string literal: all standard escape sequences from RFC 8259 are supported, including Unicode escapes like \u4f60\u597d → 你好. Unknown sequences (for example \q) are reported as an error rather than silently passed through, so you know your input was not clean JSON-escaped text.

Need the opposite direction? Use the JSON Escape tool. If your input is a full stringified JSON document with surrounding quotes, the JSON Formatter will parse and pretty-print it instead.

Examples

Read escaped log lines

Log aggregators often flatten messages into escaped form — decode them to read the original multi-line text.

Inspect API string fields

Copy an escaped field value from an API response and decode it to see the actual content.

Frequently Asked Questions

Is my text uploaded anywhere?+
No. Decoding happens entirely in your browser.
Should I include the surrounding quotes?+
No — paste only the content between the quotes. If you include them, escape them or you will get an error.
Are \uXXXX sequences decoded?+
Yes, including surrogate pairs for characters outside the basic multilingual plane.
What if the input has an unknown escape like \q?+
An error is shown. JSON only defines a fixed set of escapes, so \q indicates the text was not JSON-escaped.

Related Tools

Looking for something else? Browse all tools