User Rating 0.0
Total Usage 0 times
Input Text 0 chars
HTML Encoded Output
0 chars
Browser Preview (Decoded)
Copied to clipboard
Is this tool helpful?

Your feedback helps us improve.

About

This tool converts plain text into HTML Entities, replacing standard characters with their numeric code references. This technique is widely used by web developers to obfuscate sensitive data (like email addresses) from basic web scrapers and spam bots, or to ensure special characters (like Emojis or mathematical symbols) render correctly across all browsers and encodings.

While modern bots are becoming smarter, entity encoding remains a fundamental layer of defense and a critical utility for escaping reserved HTML characters (like < and >) within code blocks. The tool supports Decimal, Hexadecimal, and a Random Mixed mode for maximum pattern disruption.

html encoder entity converter email obfuscator web dev tools unicode escape

Formulas

HTML Entities use a specific syntax to tell the browser to render a character based on its Unicode number.

Entity = & + # + code + ;

For Hexadecimal representation, an x is added before the code:

Hex Entity = & + # x + hex(code) + ;

Where code is the Unicode code point of the character.

Reference Data

CharacterDecimal EntityHex EntityDescription
"""Quotation Mark
&&&Ampersand
<<<Less Than
>>>Greater Than
@@@At Symbol (Emails)
AAAUppercase A
aaaLowercase a
©©©Copyright Sign
Euro Sign
Infinity
😀😀😀Grinning Face

Frequently Asked Questions

It provides a basic layer of protection. It stops simple "regex-based" harvesters that look for "[email protected]". However, sophisticated bots that execute JavaScript or render the full DOM will eventually see the decoded email. It is better than plain text, but not a silver bullet.
There is no functional difference for the browser; both render the same character. Decimal uses base-10 numbers (e.g., A), while Hex uses base-16 (e.g., A). Mixing them can make the source code slightly harder for humans and simple scripts to read.
Yes. The tool uses Unicode code point parsing to correctly handle surrogate pairs, ensuring Emojis like 😀 (😀) are encoded into their correct single entity representation.
Each single character (1 byte for ASCII) is replaced by at least 4-8 characters (e.g., "a" becomes 'a'). This increases the string length by approximately 400-600% depending on the content.