HTML Decoder

Decode HTML.

Turning entities back into readable text

HTML entities like &, < and © are the encoded, safe-to-embed form of characters that would otherwise be ambiguous or special inside markup. This reverses that process - useful when you've copied text out of a page's source, an RSS feed, or an API response and it's still showing the encoded entities instead of the actual characters they represent.

Why these characters get encoded in the first place

Characters like <, >, and & have special meaning in HTML markup itself - a literal < in page text could be mistaken for the start of a tag. Encoding them as entities lets that exact character appear visually on the page without the browser trying to interpret it as markup, which is why they show up encoded whenever text passes through any system that generates HTML.

Where encoded entities commonly turn up

RSS and Atom feeds, API responses that embed HTML fragments as text, and page source views are the most common places entities appear in a form you'd want decoded - any system that generates HTML from user-submitted or database text typically encodes special characters automatically as a safety measure.

Why decoding here is safe even for untrusted text

This tool only converts entities to their text form and displays the result as plain text in the output box - it never renders the decoded content as live HTML in a browser context, so even if the original text contained something like an encoded script tag, decoding it here simply shows you the plain-text characters, with nothing executed.

Perguntas frequentes

Is this safe to use on untrusted HTML?

This tool only converts entities to their text form in the result box here - it does not render the decoded HTML as a live page, so no scripts execute.

Why do entities show up in RSS feeds and API responses?

Any system that generates HTML or XML from stored text typically encodes special characters like < and & as a safety measure, since those characters have specific meaning in markup. Decoding reverses that for readability.

What's the difference between this and the HTML Encoder tool on this site?

This tool converts encoded entities back into their original readable characters. The HTML Encoder tool does the reverse - converting special characters into their safe entity form for embedding in markup.

Can I decode numeric entities like &#65;?

Yes - both named entities (like &amp;) and numeric entities (decimal or hex) are decoded correctly, since the conversion relies on the browser's own built-in entity-decoding behavior.

Will decoding change anything other than the special characters?

No - only actual HTML entities are converted; any plain text in your input passes through completely unchanged.

Mais em Technical SEO & Site Management