In1.

HTML entity encoder and decoder

Escape characters that have special meaning in HTML — like the angle brackets, ampersand and quotes — into their entity form, or decode entities back into plain characters. Optionally encode all non-ASCII too.

Loading tool…
All Web tools

How to use HTML Entity Encoder / Decoder

  1. 1

    Choose encode or decode

    Pick whether to turn characters into entities or turn entities back into characters.

  2. 2

    Paste your text

    Enter the text to escape, or the entity-laden text to decode.

  3. 3

    Set the non-ASCII option

    When encoding, optionally also convert every non-ASCII character to a numeric entity.

  4. 4

    Copy the result

    The converted output appears instantly — copy it with one click.

Why HTML needs entities

A handful of characters carry special meaning in HTML, and using them literally where they are not meant as markup breaks the page or, worse, opens a security hole. The less-than and greater-than signs delimit tags, the ampersand begins an entity, and quotes delimit attribute values. If you want to show those characters as text — to display a snippet of code, a math expression, or a company name like 'Tom & Jerry' — you have to write them as HTML entities instead: < for less-than, > for greater-than, & for the ampersand, and so on. Doing this is also the foundation of preventing cross-site scripting, because escaping user-supplied text before putting it into a page stops it from being interpreted as active markup. This tool encodes those characters into their safe entity form for you, so you can drop text into HTML without it being misread as tags, and without having to remember every entity by hand.

Decode entities back to plain text

The reverse problem is just as common: you have HTML full of entities and you want to read or reuse the actual characters. Text scraped from a web page, pulled from an HTML email, or copied out of a database can be littered with &, <, ' and numeric codes that make it awkward to read and useless to paste somewhere that expects plain text. Decoding turns all of that back into the characters it represents, so <a href="x"> becomes the readable tag again and & becomes a simple ampersand. In1 decodes both the named entities and the numeric ones using the browser's own HTML parser, which means it understands the full range of entities a real browser does — not just a short hand-coded list — so even unusual or rare entities are decoded correctly. Whether you are cleaning up scraped content, reading an export, or preparing text for a non-HTML context, decoding restores it to its natural, usable form.

Optionally encode every non-ASCII character

Sometimes escaping the core HTML characters is enough; other times you want to go further and encode every character outside the basic ASCII range as a numeric entity. This is useful when you need maximum compatibility with systems or encodings that might mishandle accented letters, symbols, emoji or characters from non-Latin scripts. With the non-ASCII option turned on, In1 converts each such character into its numeric HTML entity, guaranteeing that the output contains only plain ASCII while still rendering as the original text in any browser. This can prevent garbled characters when content passes through older email systems, certain databases, or templating setups with uncertain encoding. When you do not need that, you can leave the option off and encode only the characters that actually have special meaning in HTML, keeping the output compact and readable. Having the choice means the tool fits both the everyday case of escaping markup characters and the stricter case of forcing everything into a safe ASCII-only form.

Private by design — runs in your browser

The text you are escaping or unescaping might be source code, user-generated content, scraped data, email templates or anything else you would rather not hand to an outside service. In1 performs all entity encoding and decoding locally in your browser. The encoding uses simple, transparent rules and the decoding leans on the browser's built-in HTML parser, so nothing is ever uploaded, stored or logged. There is no account and no sign-up. The conversion happens instantly as you type or switch modes, with no network request, which means it works the same offline as online and never stalls on a slow connection. You can paste a large block of HTML and read its decoded form immediately, or escape a snippet and copy the safe version with a single click. This local-only approach matters because escaping is so often tied to security and to handling untrusted input — doing it on your own machine keeps both the input and the result entirely under your control.

Who uses an HTML entity tool?

It is a daily utility for people who work with web content and markup. Front-end and back-end developers escape text before injecting it into pages to display code samples safely and to guard against cross-site scripting, and decode entities when reading data that arrived HTML-encoded. Technical writers and bloggers encode code snippets so the angle brackets show up as text instead of vanishing as tags. Email developers escape content to keep templates valid and force non-ASCII into a portable form. Data engineers decode entities out of scraped or exported HTML to recover clean text. QA testers and security researchers encode and decode payloads while probing how an application handles special characters. Even support staff occasionally need to decode an entity-laden string a user pasted. Because the tool handles encoding, decoding, the core HTML characters and the optional full non-ASCII pass — all instantly and privately — it covers the whole range of everyday HTML-escaping needs in one place.

Get more from In1

Higher limits, batch processing and an API are on the way. Want early access?

Frequently asked questions