JSON Unescape and Unstringifier

Paste stringified JSON into the input field on the left side of the tool. The unstringified, properly formatted JSON will appear automatically in the output field on the right. Use the 'Copy to Clipboard' button to grab the result or 'Download Text' to save it as a file. The tool removes the outer wrapping quotes and resolves all escape sequences, turning characters like \" back into regular quotes, \n into actual newlines, and \t into proper tabs. All processing happens directly in the browser, so no data gets sent to external servers.

Stringified JSON is what you get when JSON data has been converted into a plain text string. The process adds escape characters throughout the content, wrapping the entire structure in quotes and replacing internal quotes with backslash-escaped versions. The result is technically valid but almost impossible to read or work with by eye.

This happens frequently when JSON is stored inside other JSON, passed through APIs, logged in server outputs, or saved in database fields as text. What should be a clean, structured object ends up looking like a wall of backslashes and escaped characters.

Manually cleaning up stringified JSON is tedious and error-prone. Missing a single escaped quote or removing the wrong backslash breaks the entire structure. This tool handles the conversion accurately, turning that messy string back into properly formatted JSON. If you need to go the other direction, the JSON stringify tool converts plain text into a JSON-safe string. You can also use the JSON formatter to beautify the output.

There are plenty of situations where unstringifying JSON saves time: Debugging API responses where JSON payloads have been double-encoded or wrapped in strings. Reading server logs that store JSON data as escaped text strings. Extracting readable data from database records where JSON is stored as a stringified value. Cleaning up webhook payloads that arrive with extra layers of string encoding. Inspecting configuration files where JSON values have been escaped for storage.

When JSON gets stringified, the structured data is converted into a single text string. A simple object like this:

{"name": "Convert Case", "type": "tool"}

Becomes this when stringified:

"{\"name\": \"Convert Case\", \"type\": \"tool\"}"

The entire object is wrapped in outer quotes, and every internal quote is preceded by a backslash. Nested objects, arrays, and special characters all receive the same treatment. The deeper the nesting, the more layers of escaping pile up, making the data progressively harder to read.

Starting with this stringified JSON:

"{\"site\":\"convertcase.net\",\"tools\":[\"case converter\",\"word counter\"],\"settings\":{\"theme\":\"dark\",\"autoSave\":true}}"

The unstringifier produces this clean output:

{
  "site": "convertcase.net",
  "tools": ["case converter", "word counter"],
  "settings": {
    "theme": "dark",
    "autoSave": true
  }
}

Sometimes JSON ends up stringified more than once, particularly when data passes through multiple systems or APIs. Double-stringified JSON has two layers of escaping, with backslashes escaping other backslashes. This tool handles multiple layers of stringification, resolving each level of escaping to return the original clean JSON structure.

Paste the escaped text into the left panel. Each backslash sequence is turned back into the character it stands for: \" becomes a quote, \\ a single backslash, \n a line break, \t a tab and \u00e9 the letter é. It works whether or not the text still has its surrounding quotes, so you can paste a value straight out of a log or an API response. In code, JSON.parse() does the same for a quoted string.

Paste the whole escaped string. The outer quotes are optional, and text that was stringified several times is unwrapped in one pass. If the output is identical to the input, the text is not a valid escaped string, most often because it contains a quote that is not preceded by a backslash or a real line break inside the string. Keys and values are kept exactly as they were before stringification.