JavaScript String Unescape
Unescape JavaScript string escape sequences.
What is JavaScript String Unescape?
The JavaScript String Unescape tool converts escaped JavaScript string sequences back into their original, human-readable form. When JavaScript strings are escaped — whether for transport, storage, logging, or embedding in code — they contain sequences like \n for newlines, \t for tabs, \uXXXX for Unicode characters, and \xXX for hex-encoded characters. This tool decodes all of those sequences in one click, giving you the clean, readable text underneath.
This is especially useful for developers who encounter escaped strings in API responses, log files, minified code, or serialized data and need to quickly understand what the string actually contains. Instead of mentally parsing backslash sequences or writing a throwaway script, you can paste the escaped string in and get the decoded output immediately — saving time and reducing the chance of misreading encoded content.
How to Use
Using the tool is straightforward: paste your escaped JavaScript string into the input field and the decoded output appears instantly. You do not need to include surrounding quotes — just the raw escaped content. For example, pasting Hello\nWorld\t! will produce Hello followed by a real newline, then World, a tab, and an exclamation mark. Unicode sequences like \u0048\u0065\u006C\u006C\u006F will correctly render as Hello.
The tool handles all standard JavaScript escape sequences: \n (newline), \r (carriage return), \t (tab), \ (literal backslash), ' and " (quotes), \0 (null character), \xXX (hexadecimal), and \uXXXX (Unicode code points). It also supports the extended \u{XXXXX} format introduced in ES6 for characters outside the Basic Multilingual Plane, such as emoji and rare Unicode symbols.
One edge case to be aware of: if your input contains sequences that are not valid JavaScript escape sequences, the tool will leave them as-is or flag them depending on the context — it will not silently corrupt your data. Also note that this tool decodes the escape sequences themselves; it is not a URL decoder or HTML entity decoder, so \u0026 will become & but %26 or & will remain unchanged. Use the appropriate companion tools for those formats.