Encoding

HTML Entity Encode

Encode text into HTML entities so characters like <, >, &, and quotes display as literal text instead of being interpreted as markup — converted live in your browser.

Published April 10, 2024
Last reviewed June 27, 2026

Tool Summary Answer Block

This tool accepts structured input and returns deterministic output in the browser with no server upload.

Tool name: HTML Entity Encode
Input intent: Provide source content to transform, validate, or analyze.
Output intent: Receive normalized output suitable for copy, reuse, or debugging.
Example input: <a href="/search?q=cats & dogs">Tom & Jerry</a>
Example output: <a href="/search?q=cats & dogs">Tom & Jerry</a>

0entities0characters

Text to encodeDrop file

Encoded HTMLRead-only

Need to decode entities? Switch to HTML Entity Decode

Tool Introduction

Encode text into HTML entities so characters like <, >, &, and quotes display as literal text instead of being interpreted as markup — converted live in your browser.

Tool Overview

When you put user text or code samples directly into an HTML page, characters such as <, >, &, and quotation marks can break the page or open the door to cross-site scripting (XSS). Encoding turns those characters into HTML entities — for example < becomes < and & becomes & — so the browser renders them as literal text rather than parsing them as tags or attributes. This tool encodes the reserved HTML characters plus any non-ASCII character (using numeric entities like é), updating instantly as you type. Everything runs locally, so it is safe for sensitive snippets. Use it to display code in documentation, escape values before injecting them into templates, or prepare strings for HTML email and XML.

Use Cases

Display code samples in documentation without the browser parsing them as markup
Escape user-supplied text before injecting it into an HTML template to prevent XSS
Prepare special characters for HTML email or XML documents
Show literal angle brackets and ampersands in a web page
Sanitize content copied from rich editors before storing it as HTML

Input/Output Examples

Tags, quotes, ampersands, and slashes all become entities.

Input Intent

<a href="/search?q=cats & dogs">Tom & Jerry</a>

Output Intent

&lt;a href=&quot;&#x2F;search?q=cats &amp; dogs&quot;&gt;Tom &amp; Jerry&lt;&#x2F;a&gt;

FAQ

Which characters get encoded?+

The reserved HTML characters &, <, >, double and single quotes, and the forward slash are encoded, along with any non-ASCII character (encoded as a numeric entity like é). Plain letters, numbers, and spaces are left as-is.

Does encoding prevent XSS?+

Encoding output before placing it in HTML is a key defense against cross-site scripting, because it stops user text from being interpreted as tags or attributes. Always encode untrusted data for the exact context (HTML, attribute, URL, or JavaScript) where it is used.

What is the difference between named and numeric entities?+

Named entities like & are human-readable shortcuts for common characters; numeric entities like & reference a character by its Unicode code point. Both render to the same character.

Is my text uploaded anywhere?+

No. Encoding happens entirely in your browser, so your text never leaves your device.