Why did ` ` turn into a normal-looking space?

A non-breaking space is a different Unicode character from a regular space. It often looks identical in plain text, but line wrapping behavior changes in HTML and some editors hide the difference.

Why didn't decoding make my content safe to render?

Because decoding entities is not HTML sanitization. It only converts character references back into characters. Unsafe markup stays unsafe.

Why doesn't re-encoding produce the exact same entities I started with?

HTML entity encoder output is usually normalized. `<`, `<`, and `<` all represent the same character, so round-tripping preserves meaning, not the original entity style.

Do I need to encode quotes too?

In HTML text nodes, usually no. In attribute values, often yes. `"` itself is not an HTML entity; use `"` for double quotes when the context requires it.

Why are some Unicode characters left as-is instead of becoming entities?

Most Unicode characters can appear directly in HTML. Encoding is mainly required for characters with HTML syntax meaning, plus cases where you want compatibility or explicit escaping.

Why did my converted output clear after I edited the input?

The tool clears the previous result as soon as the input changes so swap and copy actions always reflect the current text. Run convert again to regenerate the output.

HTML Entity Encoder / Decoder

Encode plain text as HTML entities or decode HTML entities back to plain text in your browser.

Plain text input

HTML entity output

Basic named mode escapes the HTML-sensitive characters &, <, >, double quotes, and apostrophes while preserving the rest of the text as-is.

Named and numeric entities can decode to the same character, so round trips are not always lossless. For example, © and © both decode to the same symbol.