HTML Entity Encoder / Decoder
Convert text to HTML entities and back, escaping <, >, &, quotes and optionally all non-ASCII characters.
Related tools
All Encoding & decoding tools →Open HTML Entity Encoder / Decoder and you get an answer straight away, with no account to create. You will find it under Encoding & decoding, with Base64 Encoder / Decoder and URL encoder / decoder for the neighbouring cases.
How to use it
- Open the tool — no signup or install needed.
- Enter your input or adjust the available options.
- Get your result instantly, then copy or download it.
Frequently asked questions
What does HTML Entity Encoder / Decoder do?
Convert text to HTML entities and back, escaping <, >, &, quotes and optionally all non-ASCII characters.
When would I actually use this?
Reading a payload someone sent you, embedding a small file in a config, and finding out why a query string breaks once it reaches the server.
What is the most common mistake?
Treating Base64 as a form of protection. It is an encoding, not encryption — anyone can decode it instantly, and a token pasted into a public issue is a leaked token.
How is HTML Entity Encoder / Decoder different from Base64 Encoder / Decoder?
They sit next to each other but answer different questions: Base64 Encoder / Decoder is the one to open when you need it to encode and decode Base64 online — free. Pick whichever matches what you're starting from — both are free.
Is there a tool for the next step?
URL encoder / decoder is the closest one after this: Encode and decode URLs and query parameters.
What else is worth having open alongside it?
UUID Validator / Decoder and JWT decoder — they come up in the same task often enough to be worth a second tab.
Where do the figures come from?
The encodings follow their RFCs, so a round trip is lossless. URL encoding has two variants — one that encodes a space as %20 and one as a plus sign — and the tool says which it applies.