HTML Entity Decoder

Decode named, decimal and hexadecimal HTML entities like & and 🚀 back into plain readable text, safely in your browser.

No uploadsNo sign-upInstant results
& → &🚀 → 🚀100% Local • Zero Uploads
Decode HTML Entities
Offline engine ready100% private in-browser workspace • Zero cloud uploads
100% Private • Zero Server File Uploads

Why Use Utiliome's Free HTML Entity Decoder?

Built from the ground up for strict privacy, instant execution, and zero friction. No subscriptions, paywalls, or account registrations required.

Nothing Is Rendered or Executed

Entities are resolved with a lookup table and code point conversion. Your input is never inserted into the page, so a decoded <script> tag is just text.

Comprehensive Entity Support

Resolves the full HTML 4 named set (&copy;, &euro;, &eacute;), other HTML5 names through an inert parser, and decimal (&#8212;) and hexadecimal (&#x1F680;) references.

Full WHATWG Named, Decimal & Hex Entity Table

Decodes all 2,200+ official HTML5 named character references (&amp;, &mdash;, &copy;) alongside decimal (&#8212;) and hexadecimal (&#x2014;) numeric entities.

Safe Non-Executing Decoding Pipeline

Unescapes HTML entities into inert plain text without injecting live DOM nodes or executing embedded <script> or onerror payloads.

Utiliome vs Traditional Cloud Alternatives

Compare our local-first WebAssembly engine against legacy cloud tools.

Feature Utiliome (Local Browser) Legacy Cloud Converters
Entity Standard Coverage Full WHATWG HTML5 named entities + decimal (&#NNN;) + hex (&#xHHH;) references Handles only the 5 basic XML entities (&amp;, &lt;, &gt;, &quot;, &#39;)
XSS & Script Execution Safety Decodes into pure string memory without innerHTML script or image event execution Assigns untrusted input to live div.innerHTML, triggering XSS payloads in browser
Supplementary Astral Code Points Uses String.fromCodePoint() to decode emoji entities (&#128640; / &#x1F680;) accurately Uses legacy String.fromCharCode() which truncates code points above &#65535;
Data Privacy 100% client-side execution — scraped HTML and CMS exports stay in local RAM Submits pasted HTML snippets to remote backend servers
How it works

How to Use HTML Entity Decoder in 3 Easy Steps

No software installation required. Everything runs directly inside your web browser.

1

Paste Encoded HTML

Paste text containing named or numeric HTML entities into the editor.

2

Decode Instantly

Entities are resolved as you type. The input is never rendered, so no script inside it can run.

3

Copy Restored Plain Text

Copy the clean decoded text for use in documentation, scripts, or databases.

How HTML Entities Are Decoded Safely

Quick Answer: Utiliome decodes named HTML5 character references (&amp;, &lt;, &mdash;, &nbsp;), decimal numeric entities (&#169;, &#8217;), and hexadecimal numeric entities (&#x2014;, &#x1F680;) back into native UTF-8 Unicode text using a non-executing parser that never triggers XSS scripts. All computation executes 100% locally in your browser with zero server uploads.

Many online decoders paste your text into a hidden page element and let the browser resolve the entities, which means pasted markup becomes part of the page. This decoder uses a lookup table instead, and only hands rare HTML5 names it does not know to a detached, inert parser that never renders or runs anything:

Given this entity-encoded string:

Utiliome &amp; Co. &#8212; &quot;Free &lt;Developer&gt; Tools&quot; &copy; 2026 &#x1F680;

The decoder resolves named, decimal, and hex entities into clean Unicode characters:

Utiliome & Co. — "Free <Developer> Tools" © 2026 🚀

Hex entities like &#x1F680; decode directly into the rocket emoji (🚀), while impossible code points (above U+10FFFF, lone surrogates, or &#0;) become the replacement character �.

To escape text for HTML output, use HTML Entity Encoder.

Named, Numeric and Legacy Entities Explained

Quick Answer: To prevent double-unescaping bugs where a literal encoded sequence like &amp;lt; is mistakenly turned into an active < tag in a single pass, our decoder resolves character references deterministically in accordance with the WHATWG HTML5 tokenization state machine. All computation executes 100% locally in your browser with zero server uploads.

Understand the technical safeguards in the decoding engine:

  • Never rendered: Your input is never inserted into the page. Decoded tags such as <script> are plain text in the output box.
  • Astral plane code points: Numeric entities exceeding the 16-bit BMP range (such as emojis up to U+10FFFF) are decoded with String.fromCodePoint, preventing surrogate truncation.
  • Browser-compatible quirks: &#128; to &#159; map to the Windows-1252 characters browsers display (&#128; is €), upper-case legacy forms like &AMP; work, and &amp or &copy without a semicolon are accepted.
  • Malformed entity tolerance: Unrecognized entity names or unclosed ampersands are retained as literal text without throwing parsing exceptions.

HTML Decoder vs HTML Encoder: Which Direction Do You Need?

Quick Answer: Use HTML Entity Decoder when converting escaped HTML/XML character references (&amp;, &#x27;) back to readable Unicode text, and use HTML Entity Encoder when escaping raw <, >, &, and quotes before embedding untrusted text into HTML markup or attributes. All computation executes 100% locally in your browser with zero server uploads.

Encoding and decoding are mirror images, so Utiliome keeps a dedicated page for each direction:

  • Encode when you are writing HTML and need to display characters that HTML would otherwise interpret: code samples with tags, product names with &, quotes inside attributes, or symbols that must survive an ASCII-only pipeline.
  • Decode (this page) when you are reading HTML that someone else produced: scraped content, RSS feeds, exported comments or JSON fields that arrive with &amp; and &#8217; in them and need to become plain text again.

If text was encoded twice (you see &amp;lt; instead of &lt;), decode it twice; each pass removes one layer.

WHATWG HTML5 Named, Decimal, and Hexadecimal Entity Reference Table

Quick Answer: The WHATWG HTML Living Standard defines three interchangeable character reference syntaxes—case-sensitive named entities, base-10 decimal code points (&#D;), and base-16 hexadecimal code points (&#xH;)—all resolving to the exact same Unicode scalar value. All computation executes 100% locally in your browser with zero server uploads.

Below are the most frequently encountered HTML character references in CMS exports, RSS/Atom feeds, and scraped JSON payloads:

Rendered Glyph Named Entity Decimal Entity Hexadecimal Entity Unicode Scalar & Purpose
< / > &lt; / &gt; &#60; / &#62; &#x3C; / &#x3E; U+003C / U+003E (Tag delimiters)
& &amp; &#38; &#x26; U+0026 (Entity start delimiter)
" / ' &quot; / &apos; &#34; / &#39; &#x22; / &#x27; U+0022 / U+0027 (Attribute quotes)
(NBSP) &nbsp; &#160; &#xA0; U+00A0 (Non-breaking space)
— / – &mdash; / &ndash; &#8212; / &#8211; &#x2014; / &#x2013; U+2014 / U+2013 (Em / En dashes)
© / ® &copy; / &reg; &#169; / &#174; &#xA9; / &#xAE; U+00A9 / U+00AE (Legal symbols)

For companion markup and string tools, see HTML Entity Encoder, HTML to Markdown Converter, Unicode \uXXXX String Escaper, and URL Encoder & Decoder.

FAQ

HTML Entity Decoder FAQ and Technical Guide

Everything you need to know about using Utiliome's free online html entity decoder.

Is this decoder safe to use with untrusted user input containing script tags?

Yes. The input is never inserted into the page: entities are resolved with a lookup table (and, for rare HTML5 names, a detached parser that cannot run scripts), so a decoded <script> tag is just text in the output box.

Can this tool decode hexadecimal entities like &#x1F680;?

Yes. Both hexadecimal entities (&#x...;) and decimal entities (&#...;) are parsed and converted to native characters via String.fromCodePoint.

Why do I see &amp; or &#39; in my text instead of & and an apostrophe?

The text was HTML-encoded more than once, usually because a CMS, feed or API escaped content that was already escaped. Decode it, and if entities are still visible decode the result again; each pass removes one layer of encoding.

Is it safe to paste HTML from an unknown website into the decoder?

Yes. The decoder only converts entities to characters and shows the result as plain text in a text box. No script, style or image in the pasted HTML is executed or loaded, and nothing is sent to a server.

Why do I see strings like "&amp;amp;" or "&amp;#039;" in my CMS or API response?

That is double-encoding: the text was already HTML-encoded once (& became &amp;), and then a second serializer escaped the leading ampersand again (&amp; became &amp;amp;). Run the decoder twice if you need to unwrap doubly escaped legacy database records.

Are HTML named entities case-sensitive?

Yes! Per the WHATWG HTML5 specification, &eacute; decodes to lowercase "é" (U+00E9) while &Eacute; decodes to uppercase "É" (U+00C9). Hexadecimal entities (&#xE9; vs &#xe9;), however, are case-insensitive.