HTML Decoder

What are HTML entities?

HTML entities are the escape mechanism that lets HTML carry characters that would otherwise have a special meaning in the markup. The four characters <, >, & and " all mean something structural to an HTML parser, so anywhere you want to display them as literal text in a page you write them as <, >, & and " respectively. The same mechanism is used to encode characters that were difficult to type or transmit before Unicode was universal — typographic quotes (“, ”), arrows (→), the copyright symbol (©), accented letters (é), and non-breaking spaces ( ). HTML5 defines around 250 named entities; numeric entities (decimal © or hex © for ©) can represent any Unicode codepoint, including emoji.

Why decode HTML entities?

You see HTML-encoded text in three places more than anywhere else:

• API responses and content feeds. Many CMS-backed APIs return article bodies, comments and form-submission text with HTML entities still in place, on the assumption that the consumer will render it as HTML. If you’re processing the content as plain text (storing it in a database, running analytics on it, displaying it in a native app), you need to decode first so Don't becomes Don't.
• Debugging escaped templates. When a web page shows literal & text instead of &, something has encoded the data one too many times. Pasting the offending string here and watching it decode shows you exactly how many encoding layers are wrapped around the original — and where in your pipeline to fix the bug.
• Examining web-scraped content. HTML scraped from a page often arrives with entities still in place, especially when extracted with a tool that pulled raw markup rather than rendered text. Decoding gives you the plain-text version a human would read.

In every case the workflow is the same: paste, read, copy.

How to decode HTML on ToolJutsu

1. Paste your HTML-encoded text into the input box. Named entities (&, ©,  ), decimal numeric (©) and hex numeric (©) are all accepted in the same paste.
2. Read the result in the Decoded box. The output updates live as you type or paste — there’s no Convert button.
3. Click the Copy button to put the decoded text on your clipboard.
4. If you suspect double-encoding (the output still contains &something; sequences), paste the output back into the input and decode again. Each click peels off one layer.

Common scenarios

When you’re decoding an API response to display it in a native app or terminal, paste the full response in — the decoder leaves non-entity text untouched, so paragraphs of mixed entities and plain text decode cleanly without disturbing the surrounding content.

When you’re debugging an escaped template that’s rendering & on the page instead of &, paste the rendered output here. If one decode brings you back to readable text, the template encoded once too many; if it takes two decodes, you’ve got double-encoding to hunt down in your CMS.

When you’re examining scraped HTML and want to extract the prose without rendering it through a full browser, this decoder gives you the same output the browser would have shown — including all the typographic quotes, em dashes and special punctuation that named entities cover.

When you need to encode rather than decode — for instance, preparing user-supplied text for safe insertion into an HTML template — use the sibling HTML Encoder. The two together let you round-trip text between escaped and unescaped forms with confidence.

Privacy

The decoder reads your input and runs it through a hidden DOM node, which is how every browser turns entity sequences back into characters. All work happens synchronously in JavaScript on your device. The page makes no network requests after the initial JavaScript loads — ToolJutsu never sees the content you paste, including any sensitive data in API responses, scraped pages or debug output.

Compatibility notes

The browser’s HTML parser is available in every desktop and mobile browser of the last 15 years, so the decoder works without polyfills in Chrome, Firefox, Safari, Edge and every mobile browser in current use. The set of recognised named entities matches the HTML Living Standard, which means anything a real web page can render through entities, this decoder can decode. If you need to decode programmatically, the same DOM-parser trick (element.innerHTML = x; return element.textContent) works in any JavaScript environment with DOM access.