HTML Entities Converter — Encode & Decode

What Are HTML Entities?

HTML entities are special codes used to represent characters that have a specific meaning in HTML or cannot be typed directly. They start with an ampersand (&) and end with a semicolon (;). The most important entities are &amp; (&), &lt; (<), &gt; (>), and &quot; (") — these must be escaped when used as content in HTML to avoid being interpreted as markup.

Named vs Numeric HTML Entities

Named entities: &amp; &lt; &gt; &copy; &reg; &trade; — human-readable names. Decimal numeric entities: &#169; for © — uses the decimal Unicode code point. Hexadecimal entities: &#xA9; for © — uses the hex Unicode code point. All three formats are valid HTML. Named entities are most readable; numeric entities cover any Unicode character.

Common HTML Entities You Need

&amp; = & (ampersand — must always be escaped in HTML). &lt; = < (less than — starts HTML tags, must be escaped). &gt; = > (greater than — ends HTML tags, escape in attributes). &quot; = " (double quote — escape inside attribute values). &apos; = ' (apostrophe — escape in single-quoted attributes). &nbsp; = non-breaking space. &copy; = ©. &reg; = ®. &trade; = ™.

The Five Essential HTML Entities

Five characters require HTML entity encoding in all HTML contexts because they have special structural meaning: < (less-than, which begins HTML tags) encodes as <, > (greater-than, which ends HTML tags) as >, & (ampersand, which begins entities themselves) as &, " (double quote in attributes) as ", and ' (single quote in attributes) as ' or '. Failing to encode these five characters when they appear in user-generated content is the root cause of Cross-Site Scripting (XSS) vulnerabilities — one of the most common and serious web security issues.

Named vs Numeric Entities

HTML entities come in two formats. Named entities use descriptive names: © for ©, ™ for ™, € for €, — for —. Numeric entities use decimal (© for ©) or hexadecimal (© for ©) Unicode code point values. Named entities are more readable and memorable but have less complete coverage. Numeric entities can represent any Unicode character. Both formats decode to identical output — the choice between them is a developer preference or style guide decision, not a technical requirement.

HTML Entities vs Unicode Characters

A common question: should you use HTML entities or Unicode characters directly in HTML source? The modern answer: use Unicode characters directly in UTF-8 encoded HTML files, and reserve HTML entities only for the five structural characters that must be encoded. Writing © directly in UTF-8 HTML is equivalent to © — both display identically. The historical reason for using named entities — ASCII-only file encoding that couldn't represent non-ASCII characters — no longer applies to modern web development where UTF-8 is the universal standard.

Entity Encoding for User Content

Web applications that display user-submitted content must HTML-encode all text before displaying it in HTML context. A user who submits the text '<script>alert(1)</script>' as their username should see that exact text displayed on their profile, not have a JavaScript alert execute. Proper HTML encoding transforms the < and > to < and >, rendering the text visible without executing it. This sanitization step is fundamental to web security and must occur at display time rather than storage time — storing pre-encoded text creates double-encoding problems when text is processed by multiple systems.

Special Character Reference for Creators

Common HTML entities useful for content creators:   (non-breaking space, prevents line break between words), — (em dash —, for punctuation), – (en dash –, for ranges), … (ellipsis …, three dots as single character), « » (guillemets « », used in French and other European typography), © (copyright ©), ® (registered trademark ®), ™ (trademark ™). These entities ensure these characters display correctly in all HTML contexts without depending on the character being present in the document's encoding.

The Five Critical HTML Entities

HTML has five characters that must always be escaped in content: & (ampersand → &), < (less-than → <), > (greater-than → >), " (double quote → "), and ' (apostrophe → ' or '). Using any of these raw characters in HTML content can break the page: an unescaped & starts what HTML parses as an entity reference, an unescaped < starts what HTML parses as a tag. Web security depends on proper HTML entity encoding — failure to encode user input before inserting it into HTML is the cause of Cross-Site Scripting (XSS) vulnerabilities.

XSS and HTML Entity Encoding Security

Cross-Site Scripting (XSS) is consistently one of the top web security vulnerabilities. The attack works by injecting script content into a web page through input that isn't properly HTML-encoded. If a user types <script>alert('xss')</script> into a comment field and the application renders it as HTML without encoding, the script executes in other users' browsers. Proper HTML entity encoding of all user-provided content before rendering it as HTML prevents this — <script> renders as the visible text rather than executing as a script tag.

Named vs Numeric HTML Entities

HTML entities have two forms: named (& <   ©) and numeric (& <   ©). Named entities are human-readable and more common in hand-written HTML. Numeric entities work for any Unicode character — even ones without names — using either decimal (€ for €) or hexadecimal (€ for €) notation. For special characters not in the named entity list, numeric entities are the only encoding option. This tool generates both forms, letting you choose based on your context and readability preferences.

Non-Breaking Space ( ) Use Cases

The non-breaking space (  or  ) is among the most used HTML entities in professional web development. Unlike a regular space,   prevents line breaks between the words it connects, and in certain contexts prevents multiple spaces from collapsing to one. Common uses: keeping a number with its unit together (10 km won't line-break between 10 and km), preventing a title from breaking at an awkward point, adding horizontal spacing in HTML where regular spaces would collapse, and creating indentation in contexts where CSS spacing isn't available.

HTML Entities in Email Templates

Email HTML has stricter encoding requirements than web page HTML because email clients have inconsistent CSS support and different HTML rendering engines than browsers. Characters like em dashes (—), curly quotes ( ' '), ellipses (…), and special mathematical symbols should always be encoded as named or numeric HTML entities in email templates to ensure they render correctly across all email clients. Plain text versions of emails should use ASCII equivalents (-- for —, ... for …). Email developers who understand HTML entities produce more consistently-rendered templates across the Gmail, Outlook, Apple Mail, and other clients that recipients use.