Unescape JSON strings online

JSON unescape reverses escape encoding: sequences like \", \\, \n, \t, and \uXXXX become their real characters. When you unescape json online, you translate transport-safe escaped json back into what an editor would show.

This is not URL decoding, Base64 decoding, or HTML entity decoding — each layer has its own alphabet. Use this page when the input uses JSON backslash escape syntax.

The tool applies the same rules as javascript unescape json via JSON.parse: it understands quoted string literals and bare escaped fragments. It does not use the legacy JavaScript unescape() function for URL-encoded strings.

Malformed sequences — a lone backslash or truncated quote — surface as errors rather than silent corruption so you can fix the source.

Paste your escaped string into the input panel. Unescaped text appears live as you edit. A value like "Line one\nHello" becomes readable text with a real line break.

You can paste with or without outer double quotes — the tool tries both forms automatically. Copy unescaped text with one click or save as a .txt file.

Import a .txt or .json fragment when the string is too long to paste reliably from a log viewer or database export.

Clear the editor when finished if you are working with sensitive content on a shared machine.

Javascript unescape json in application code means JSON.parse on a quoted string value — exactly what this tool does internally.

Python json.loads on a quoted string, Go json.Unmarshal, and Java Jackson parsers follow the same specification. Compare your app's output against this page when debugging charset or double-encoding issues.

Log aggregators and APM tools often display escaped json on one line. Unescape here to read multiline stack traces and user-facing error messages as the author intended.

When a mobile crash report stores escaped json in a custom field, unescape json free in the browser before pasting into a ticket or wiki.

Log and API inspection: when a JSON field contains \n and \" sequences, unescape to read the original message before escalating to engineering.

Database exports: legacy columns sometimes store escaped json text. Unescape to inspect real line breaks and punctuation before normalization.

Double-encoding detection: if output still looks escaped, the pipeline may have encoded twice. Unescape once, inspect, and trace where the extra pass happened.

Content migration: moving strings between a JSON API and a plain-text editor during integration — unescape when pulling from JSON, escape when pushing back.

Unescaping an entire JSON document removes escapes that the parser still needs. Unescape string contents, not whole documents, unless you intend to edit raw text.

Wrong layer: percent-encoded URLs (%22) need the URL Decoder, not json unescape. HTML entities need the HTML Unescape tool.

Invalid escape sequences produce errors. A trailing backslash or incomplete \u reference cannot decode — fix the source or escape only the portion you need.

Security: unescaping untrusted log data for display is fine for reading. Re-inserting unescaped text into live systems still requires validation at the application layer.

Unescaping runs locally in your browser. Log excerpts, customer data, and internal API responses never upload to a server.

Pair with our JSON Escape tool for reverse conversion. Use the JSON Formatter when you need to beautify a whole document after fixing a string field.

Treat unescaped content from untrusted sources carefully — inspect malicious payloads in isolated environments before re-publishing.