What Is the Revert Unicode Text Tool?
Restore supported styled characters to ordinary text, or explicitly encode and decode Unicode escapes. Restore is the default because it addresses the page's original styling-removal task. Unsupported characters remain unchanged; output can still contain Unicode.
How to Use the Revert Unicode Text Tool
- Paste styled text and choose Restore supported styles, or select Encode/Decode for an explicit escape format.
- Choose JavaScript, legacy percent, U+ list, HTML references, CSS string contents or UTF-8 URI component.
- Inspect the method and output before copying or downloading.
- Use output as input when you want another deliberate conversion step. It does not automatically select an inverse operation.
How the Revert Unicode Text Tool Works
Restore applies compatibility normalization only to supported mathematical alphanumeric, letterlike, fullwidth ASCII, circled letter and circled 1-to-20 character ranges when the result is printable ASCII. Other text remains unchanged. It does not repair inverted text, confusable letters, mojibake or arbitrary scripts.
JavaScript uses UTF-16 Unicode escape units; supplementary characters use a surrogate pair. Legacy percent syntax uses %u units and is distinct from UTF-8 URI percent bytes. U+ mode accepts a complete whitespace-separated list; an actual space must be U+0020. CSS encoding uses terminated six-digit escapes, while CSS decoding supports string escapes and newline preprocessing. HTML decoding preserves the existing valid-scalar/single-layer rules and limited named-reference list.
Revert Unicode Text Tool Example
| Input | Mode/format | Output |
|---|---|---|
| 𝗛𝗲𝗹𝗹𝗼 Ａ① | Restore | Hello A1 |
| Hello World! | Encode U+ list, then decode it | Hello World!, including the original space |
\u0041 | Decode JavaScript | Literal doubled-backslash escape remains unchanged |
\u0041 | Decode JavaScript once | A |
| %C3%A9 | Decode UTF-8 URI component | é |
When to Use the Revert Unicode Text Tool
Restore supported styling before searching text, inspect an escaped Unicode value, or make a small CSS/URI-component example. Preserve the original when typography or exact identifiers matter.
Common Mistakes
Auto recognizes one format in priority order: JavaScript Unicode escapes, supported-looking HTML references, legacy %u, then a complete U+ list. It leaves input unchanged when none matches and never guesses CSS or ordinary UTF-8 URI components. Mixed formats require explicit separate passes. Restoration is lossy: several styled characters can map to the same plain character.
This is not a complete JavaScript/JSON/Python parser or an output-context security encoder. Malformed unrecognized escape tokens remain literal; recognized invalid scalars or unpaired surrogate results show an error. CSS NUL, surrogate and out-of-range escapes use the replacement character under CSS rules. Invalid HTML numeric references remain literal. URI encoding does not encrypt text. Inputs over 1,000,000 UTF-16 units block output; errors are separate from copyable text.
Tips for Better Results
Choose the source format explicitly for logs, paths and mixed text. Count units correctly: a supplementary character occupies two UTF-16 units. Keep output selectable for manual copying and test it in the receiving parser or application.
References: Unicode normalization, CSS Syntax and MDN URI-component encoding.