Practical usage guide
What this tool does
Unicode escapes and HTML entities are textual representations used in source code, JSON-like data, and HTML. Unicode escape mode works with code points, while HTML entity mode converts the characters that are most significant in markup or decodes numeric and a small set of named entities.
These transformations change representation, not trust. Encoding characters as entities is not a complete HTML sanitizer, and unescaping content does not make it safe to insert into a page.
Quick start
Identify the representation
Use Unicode unescape for sequences such as \u4f60 or \u{1f600}. Use HTML decode for &, ©, or 😀.
Choose escape or unescape
Escape makes characters explicit for source text; unescape returns readable Unicode characters for inspection.
Review the destination context
If the result will enter HTML, JavaScript, JSON, or an attribute, apply the escaping and security rules required by that exact context.
Common use cases
Read escaped logs and payloads
Turn copied Unicode escape sequences into readable multilingual text and emoji.
Prepare basic text for HTML source
Encode &, <, >, quotes, and apostrophes when demonstrating literal markup characters.
Inspect numeric entities
Decode decimal and hexadecimal character references to verify the code point they represent.
Limitations and important notes
Named HTML entity support is intentionally limited
The decoder supports amp, lt, gt, quot, apos, nbsp, and numeric entities. Names such as © are left unchanged.
Entity encoding is not XSS protection by itself
Safe rendering depends on context and framework behavior. Use a maintained sanitizer for untrusted HTML.
Some code points use surrogate pairs
Characters above U+FFFF may appear as two UTF-16 code units in older escape styles. Prefer code-point notation such as \u{1F600} when supported.