HTML Entity Decode

Introduction

HTML Entity Decode converts HTML entities back into their original characters so encoded markup and text display or behave as intended. This tool is useful for developers, content authors, and support teams who receive encoded content (from logs, APIs, or CMS exports) and need to restore readable HTML, punctuation, or non-ASCII characters.

What is this tool?

Many systems encode special characters as HTML entities (e.g., &, <, ©) to prevent browsers from interpreting markup or to preserve characters across encodings. This tool decodes named entities, decimal numeric entities (e.g., ©), and hexadecimal entities (e.g., ©) into their character equivalents so the content can be rendered or processed normally.

Why use this tool?

• Restore readability: Turn encoded content from logs, exports, or APIs back into readable HTML or text.
• Content editing: Prepare decoded HTML for editing in WYSIWYG editors or source views.
• Data migration: Decode entities before importing into databases or CMS fields that expect raw characters.
• Debugging: Diagnose double-encoding issues or confirm what content a browser will render.

How to use it

1. Paste the encoded string into the input area (for example, <div>Hello & welcome – 2026</div>).
2. Choose options if available (decode named entities only, decode numeric entities, or decode all).
3. Click “Decode.”
4. Copy the decoded output for pasting into editors, templates, or test pages.
5. If needed, use the Encode tool to re-encode for safe display or storage.

Example

Input (encoded):

<div class="note">Cost: $29.99 — © 2026</div>

Decoded output:

<div class="note">Cost: $29.99 — © 2026</div>

FAQ

Do you store my input?
No — inputs are processed in real time and are not retained. If your deployment logs inputs for debugging, disclose this in your Privacy Policy.

Can decoding cause XSS?
Yes. Decoding entities that were intentionally encoded for safety can reintroduce executable HTML/JavaScript. Always validate and sanitize decoded content before rendering in a browser, especially if the source is untrusted.

What about double-encoding or double-decoding?
Be cautious: some strings are encoded multiple times (e.g., <). Repeated decoding can produce undesired results. Use the tool’s preview and, if available, a single-step decode option to avoid accidental over-decoding.

Which entity formats are supported?
This tool supports named entities (e.g., ©), decimal numeric (e.g., ©), and hexadecimal numeric (e.g., ©), as well as common legacy entities.