HTML entities
EncodingEncode text as HTML entities or decode them back. Supports named, decimal, and hex formats.
What this tool helps with
HTML entities let you put characters that would otherwise be parsed as markup — like <, >, & — safely inside HTML text content or attributes. This tool encodes between named entities (&), decimal numeric (&), and hex (&) forms, and decodes any of them back to plain text. It is UTF-8 correct so emoji and non-Latin scripts round-trip without being mangled, and it runs in your browser so content that you can't paste into a remote tool stays local.
Encodes: & < > " '
How to use HTML entities
- Open the HTML entities page and paste, type, or generate the html input you want to work with.
- Pick the options you need so the tool can encode text as HTML entities or decode them back. Supports named, decimal, and hex formats
- Copy the entities result with one click and use it in your next step — terminal, editor, ticket, or anywhere else you need it.
Common uses
- Reach for HTML entities when you need to encode text as HTML entities or decode them back. Supports named, decimal, and hex formats during debugging, code review, or content preparation.
- Skip installing a desktop html app — open this encoding utility on a shared machine, an iPad, or a colleague's laptop and it just works.
- Bookmark or share the page when you and your team keep coming back to the same html, entities, encode, and decode workflow.
FAQ
Named, decimal, or hex — which should I use?
Named entities (&, ©) are the most readable. Numeric forms work for any Unicode codepoint and don't depend on the parser knowing the name. For modern UTF-8 documents you rarely need to escape beyond <, >, &, and "; older or strictly ASCII systems may need everything escaped.
Why are my escaped characters still appearing as markup?
Most likely the escaping happened after the parser had already interpreted them, or a downstream stage un-escaped. Escape closer to where the value is finally rendered into HTML, not in the original data.
Does this handle attribute values too?
Yes. The same encoding applies inside attributes, with the additional requirement that quote characters matching the attribute's surrounding quotes are escaped.