HTML Decode - Free Online Tool

HTML Decode converts named and numeric entities back into plain characters so CMS exports, email archives, and API payloads become easier to read and edit, all without leaving your browser.

Decode HTML entities

Input encoded HTML

Decoded HTML/text

What is HTML Decode?

HTML Decode is a free online tool that reverses entity encoding: sequences like & become &, < becomes <, and numeric references such as ' become apostrophes. Content systems often emit heavily escaped HTML when exporting articles, RSS feeds, or notification templates. Developers and editors use HTML Decode to recover readable source before refactoring, diffing, or pasting into environments that expect raw characters instead of entities.

HTML Decode supports both decimal and hexadecimal numeric entities because those formats appear interchangeably in legacy data. Named entities cover the most common punctuation and symbols defined by the HTML specification. Unknown or malformed entities are preserved intentionally so you can spot data quality issues rather than silently corrupting strings.

HTML Decode is not an HTML parser: it does not build a DOM, execute scripts, or validate full documents. It operates on text, which makes it fast and predictable for focused cleanup tasks. When you need structural transformations—moving nodes, stripping tags selectively—reach for a proper parser or templating pipeline instead of expecting HTML Decode to rewrite markup trees.

How to Use This HTML Decode

Paste the entity-heavy string you want to simplify into the HTML Decode input textarea. This might come from a CMS export, an old email template, or a log line that double-escaped user input.
Scan for surrounding context such as JSON quotes; remove outer JSON escaping if you accidentally copied the whole JSON string instead of the inner HTML fragment.
Click Decode to expand entities. HTML Decode writes the readable result into the output textarea when parsing succeeds.
If some entities remain unchanged, confirm whether they are valid HTML entity names; typos like &nbps; will not decode and signal upstream data issues.
Use Copy to move decoded text into your editor, migration script, or ticket after verifying the output matches expectations.
Click Clear between samples so errors or partial output from one attempt do not confuse the next decode operation.
When migrating to a system that expects raw UTF-8, decode once, inspect, then let the destination platform apply its own escaping rules during publish.
Pair with HTML Encode when you need to round-trip: decode to edit, then encode again before placing literal examples back into HTML contexts.

Why Use This HTML Decode?

Why use this HTML Decode step in migrations: you can normalize exports before regex transforms, which reduces false matches on entity text.
Why use this HTML Decode flow for editing: authors read natural punctuation instead of " sequences, which lowers cognitive load during rewrites.
Why use this HTML Decode tool for debugging: API responses that embed HTML fragments become scannable so you can spot missing closing tags quickly.
Why use this HTML Decode experience for QA: testers compare decoded strings against product copy without manually replacing entities in spreadsheets.
Why use this HTML Decode option for privacy: decoded strings stay inside the browser session instead of being uploaded to ad hoc cloud parsers.
Why use this HTML Decode UI for consistency: named and numeric entities both resolve through one button, avoiding piecemeal manual replacements.
Why use this HTML Decode helper with URL Decode: stacked encodings sometimes require decoding HTML first, then percent-encoding layers, in careful order.

When to Use HTML Decode

Content engineers clean RSS descriptions that arrived with every quote entity-expanded twice during syndication.
Email marketers recover readable subject-line templates from archives where HTML entities obscured punctuation.
Developers decode snippets from error monitoring tools that HTML-escaped stack frames before JSON serialization.
Localization reviewers decode translated strings to verify apostrophes and accents before re-importing into TMS tools.
Students study how numeric entities map to unicode code points by decoding samples with HTML Decode and comparing charts.
Support analysts decode ticket descriptions exported from systems that escaped user messages aggressively for XSS prevention.

HTML Decode Features

Decode action for entity expansion

HTML Decode applies a single Decode operation so you always know which version of the string is current after edits.

Named and numeric entity support

Decimal and hexadecimal numeric entities decode alongside common named entities, which mirrors what authors see in real CMS exports.

Preserves unknown entities

When HTML Decode encounters an unrecognized token, it leaves the text intact so you can search logs for the typo instead of silently deleting data.

Monospace fields for diffing

Input and output use monospace fonts so subtle entity differences remain visible when using HTML Decode during forensic content reviews.

Copy and Clear controls

Copy moves decoded text to the clipboard with toast feedback, while Clear resets state for the next string in a batch cleanup.

Client-side text processing

HTML Decode never uploads pasted content, aligning with cautious handling of customer messages embedded in exports.

Understanding Named, Decimal, and Hexadecimal HTML Entities

Named entities map short mnemonics to characters: © for the copyright sign,   for non-breaking space in older content. Decimal numeric entities use &#NNN; syntax while hexadecimal uses &#xHH; for the same unicode code point in base sixteen. HTML Decode recognizes these patterns because they appear interchangeably depending on which editor or exporter produced the file.

Entities exist because HTML mixes structure with text. Without them, including a literal less-than in prose would start a tag. Encoding defers the ambiguity; decoding restores the original character when you switch contexts from HTML to plain text editing. Double decoding can accidentally turn intended literal & sequences into ampersands if you decode twice without noticing.

Browser innerHTML behavior differs from string-level decoding: browsers may normalize whitespace or implied tags. HTML Decode works at the string layer, which is predictable but means you must still validate final markup in a real DOM environment before publishing complex documents.

Decision Guide

Best for

Content migration cleanups.
Developer debugging of templating output.

Avoid when

You need full HTML parsing and DOM transformations.

Example

Decode escaped heading HTML

Input

&lt;h1 class=&quot;hero&quot;&gt;Welcome&lt;/h1&gt;

Output

<h1 class="hero">Welcome</h1>

HTML Decode Best Practices

Decode only when the next step expects raw text

If your CMS will re-escape on save, decoding too early might trigger different escaping rules. Plan the pipeline so HTML Decode sits at the correct stage.

Watch for mixed encodings

Sometimes percent-encoding and HTML entities stack. Decide which layer to decode first based on which syntax you visually observe in the string.

Keep backups before mass decoding

Batch conversions are safer when originals remain in version control so you can diff if HTML Decode revealed unexpected unicode characters.

Validate after decode in browsers

If decoded output will become live HTML, load it in a safe preview environment to ensure no script-bearing tags appeared after entities were removed.

Document unknown entities you find

When HTML Decode preserves a token, log it for upstream teams so exporters can fix typos instead of every consumer working around them.

Troubleshooting

Some entities remain unchanged.

Unknown entities are preserved intentionally. Check if your source entity is valid HTML.

Unexpected symbols after decoding numeric entities.

The numeric code may point to a different Unicode character than expected.

Common HTML entity problems and how HTML Decode helps

Double-escaped RSS content

Feeds sometimes contain &lt; sequences. HTML Decode once reveals < so you can decide whether another decode pass is appropriate or whether the feed generator is misconfigured.

Numeric entities pointing to unexpected symbols

When   appears as a narrow no-break space, decoded text looks like a normal space but behaves differently in layout. HTML Decode exposes the real character so you can normalize spacing intentionally.

Legacy nbsp proliferation

Older exports replace every space with non-breaking spaces. Decoding entities is only the first step; you may still need whitespace normalization after HTML Decode.

JSON wrapping confusion

Pasting a JSON string with escaped quotes may prevent HTML Decode from seeing true entity boundaries. Strip JSON escaping first, then decode HTML entities.

Expecting DOM-level fixes

HTML Decode will not balance tags or remove unsafe attributes. Use a sanitizer when structural cleanup is required, not additional decode passes.

FAQs

How do I decode HTML entities to normal text online?

Paste the escaped string into HTML Decode and click Decode to expand entities into characters. Copy the result once it matches your expectations. The tool is free and runs locally, which makes it convenient for quick cleanup between CMS exports.

Does HTML Decode support numeric entities like {?

Yes. Both decimal and hexadecimal numeric entities decode when they follow HTML rules. If a numeric reference is out of range or malformed, the tool leaves it unchanged so you can correct the source data instead of producing silent corruption.

Can HTML Decode execute scripts in my browser?

No. HTML Decode manipulates text only and does not inject output into the live DOM as executable HTML. You should still treat decoded strings carefully before pasting them into files that will later be interpreted as HTML with script tags.

Why are some entities unchanged after HTML Decode?

Unknown names, missing semicolons in contexts that require them, or partial copies can all prevent recognition. Fix the upstream string or compare against the HTML specification list. Preserving unknown tokens is safer than guessing.

Is HTML Decode safe for customer messages?

Decoding runs locally, but customer messages may contain sensitive information once readable. Handle decoded text under your privacy policy and avoid sharing screens when PII becomes visible. The tool does not log content, yet human processes still matter.

How is HTML Decode different from HTML Encode?

HTML Decode expands entities to raw characters while HTML Encode performs the opposite transformation for display contexts. They address opposite directions in a content pipeline and are often used sequentially during migrations.

Can I decode an entire HTML document with HTML Decode?

You can paste large strings, but HTML Decode is a text transform, not a formatter or validator. Very large documents may be easier to process with editor macros or build tooling. Use this page for focused fragments and debugging samples.

Does HTML Decode fix broken markup?

No. It only replaces entity sequences with characters. Missing closing tags or invalid attribute syntax remain after decoding and require templating or parser fixes elsewhere in your workflow.

HTML Decode is the fast way to turn entity-heavy text back into something humans can edit, review, and ship without fighting invisible character codes.

HTML Encode

Live

Escape HTML special characters to safe entities.

URL Decode

Live

Decode URL-encoded text back to normal format.

Base64 Decode

Live

Decode Base64 strings back to readable text.

JSON Validator

Live

Validate JSON and see errors with line and position.