HTML Entities Converter

Convert all applicable characters to HTML entities (server-grade).

Input

Result

Was this tool helpful?

Thanks for the feedback!

The HTML Entities Converter replaces every character that has a named HTML entity with that name, so é becomes é, © becomes © and a curly quote becomes “. It runs PHP's htmlentities() function with the ENT_QUOTES flag on the server, which is useful when you are preparing text for an older system, a template that isn't UTF-8, or you simply want to see the entity names for a string.

Example output

Input:

Café & Crème – ₹450 © 2026 "Special" 'offer' <b>

Result:

Caf&eacute; &amp; Cr&egrave;me &ndash; ₹450 &copy; 2026 &quot;Special&quot; &#039;offer&#039; &lt;b&gt;

Maths and typography symbols are named too: 10 × 5 ÷ 2 ≥ 20 → “quotes” … ½ becomes 10 × 5 ÷ 2 ≥ 20 → “quotes” … ½.

The names follow a pattern that makes them easy to read back: the base letter plus the accent, so é is e with an acute accent, è is e with a grave, ü is u with an umlaut and ñ is the ñ in "España". Capital letters get a capital first letter, as in É for É.

Why ₹ and Hindi text are left alone

PHP uses the HTML 4.01 entity table by default. That list covers Latin-1 accented letters, Greek letters, arrows, maths operators and common punctuation, but it predates the rupee sign, which was introduced in 2010, and it contains no names for Indian scripts or emoji. Characters without a name are output unchanged rather than as numeric codes. They display correctly on any UTF-8 page; if you really need an ASCII-only file, write the rupee sign as ₹ by hand.

How it differs from the HTML Encoder

Input	HTML Encoder	This converter
< > & " '	escaped	escaped
é ü ñ	unchanged	named entities
© – “ ” …	unchanged	named entities
₹, Hindi, emoji	unchanged	unchanged

For a modern UTF-8 page, the lighter HTML Encoder is enough. This converter earns its place when a destination mangles non-ASCII characters, for example an old email template, a database column with a Latin-1 collation, or a system that shows Ã© instead of é.

Points to watch

Not for XML or RSS. XML only predefines five entities. A feed or sitemap containing é will fail to parse, so keep XML in UTF-8 or use numeric references.
Existing entities are encoded again. & in the input becomes &amp;. Decode first with the HTML Decoder if your text is partly encoded.
Edges are trimmed. Spaces and line breaks at the very start and end of the input are removed before conversion; spacing inside the text is kept.

Because conversion uses PHP, your text is sent to the EthicalFusion server and the converted result is returned to the page.

Frequently asked questions

Why wasn't the ₹ sign converted to an entity?

PHP uses the HTML 4.01 entity list, which has no name for the rupee sign. Named-less characters are left as they are; use ₹ manually if you need a code.

What is the difference between this and the HTML Encoder?

The HTML Encoder changes only five special characters. This converter also turns accented letters and symbols like © and – into named entities.

Can I use the output in XML, RSS or a sitemap?

Not if it contains named entities for accented letters or symbols, because XML only predefines five entities. Keep XML files in UTF-8 instead.

Why are entity codes already in my input encoded again?

PHP escapes the ampersand at the start of each existing code, so it becomes a double-encoded entity. Decode the text first if it is already partly encoded.

Which quote characters are converted?

Both, because the ENT_QUOTES option is used. Double quotes get the named quot entity and single quotes become the numeric code '.