Convert escaped characters back to their original form with one click
Our unescape tool makes it simple to convert encoded text back to its readable form with just a few clicks—no technical knowledge required.
\n
or "
Auto-detect
: Works for most common formats (recommended for most users)JavaScript/JSON
: Handles sequences like \"
and \u0041
HTML/XML
: Converts entities like <
to <
Python
: Processes Python-specific escape sequencesURL Encoding
: Decodes percent-encoded characters like %20 to spacesUse the "Auto-detect" option first—it correctly identifies the encoding type in most cases, saving you time from manually selecting formats.
This tool comes in handy in various situations where you encounter encoded text that needs to be made human-readable again.
Our tool recognizes and processes a wide variety of escape sequences from different encoding systems and programming languages.
Escaped Form | Becomes | Format/Type |
---|---|---|
\\"Hello\\" | "Hello" | JavaScript/JSON |
Line\\nBreak | Line Break | JavaScript/Newline |
<div> | <div> | HTML Entity |
\\u2665 | ♥ | Unicode Escape |
%7B%22name%22%3A%20%22John%22%7D | {"name": "John"} | URL Encoding |
\\x48\\x65\\x6C\\x6C\\x6F | Hello | Hex Escape |
Understanding and properly handling escaped text is crucial for working with modern applications and data systems.
While unescaping makes text readable, be cautious with content from untrusted sources. Some encoded text might contain malicious scripts that become active when unescaped.
Proper unescaping ensures that data appears exactly as intended by the original author, preserving meaning and context that might be lost in encoded form.
When working with APIs or databases, quickly unescaping text helps identify issues with data encoding pipelines or processing errors.
Sometimes unescaping doesn't work as expected. Here's how to handle common problems.
This often happens when the wrong format is selected. Try the "Auto-detect" option first, or experiment with different format options if the result isn't as expected.
For text with multiple encoding types (like HTML entities within a JSON string), you may need to unescape multiple times with different format selections.
Some less common encodings might not be recognized. Try manually selecting the specific format, or use specialized tools for obscure encoding types.
This could indicate that the original encoding was applied incorrectly or the text was damaged during transmission. There may not be a perfect solution for badly encoded text.
Follow these guidelines to get the best results when working with escaped text.