Why unescape a JSON string?
Log entries, API error bodies and config values often arrive as escaped JSON strings full of \n and ”. Paste one above to read the actual text with real line breaks.
How it works
The input is parsed locally as a JSON string literal (quotes added automatically if you pasted bare content). Every escape — \n, \t, ”, \, \uXXXX — is decoded to its real character. Invalid escape sequences produce a clear error.