Jsontify

Ad-free, fast, private JSON viewer & editor

Paste JSON, drop a file, or Open

Explorer

Tree explorer will appear here once JSON is loaded

Inspector

Select a node to inspect it

Paste or open a file to begin
🔒 Processed in your browser - nothing is uploaded to our servers

JSON Unescape

Paste a JSON-as-a-string value - the kind you get when an API response, a log line, or LLM output wraps real JSON inside a quoted string with escaped quotes and \n newlines - and Jsontify automatically detects it and shows an Unstringify button in the raw pane toolbar.

Click it and the escaped string is un-escaped and parsed, replacing your document with the real, readable JSON underneath - properly indented objects and arrays instead of a single line full of backslashes. It's a single undoable edit, so Cmd+Z (or Ctrl+Z) restores the original escaped string exactly.

This is the reverse of Stringify (see the JSON Escape tool) and the most common case where it's needed: a field in an API response that is itself a JSON string rather than a nested object, or a chat or log export where JSON got escaped once for storage and now needs to be read as JSON again.

Detection and un-escaping both run in the same background worker as parsing, so even a large escaped blob unstringifies instantly, and the result is immediately explorable in the tree and inspector - nothing is uploaded to our servers in the process.

Frequently asked questions

How do I know if my JSON needs unescaping?
You don't have to guess - Jsontify detects when the loaded document is itself a JSON string and only then shows the Unstringify button in the raw pane toolbar.
Does unescaping change my document?
Yes - unlike Stringify, Unstringify replaces your document with the real JSON underneath. It is a single undoable edit, so Cmd+Z restores the original escaped string.
Where does this kind of escaped JSON usually come from?
API responses with a field that holds JSON as a string instead of a nested object, and logs or LLM output where JSON was escaped once for storage or transport.
Is the unescaped content uploaded anywhere?
No. Detection and unescaping both run entirely in your browser - nothing is uploaded to our servers.