Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenConvert markup into entity-escaped text you can place safely inside a page or template.
Anything you want displayed literally rather than parsed.
&, <, > and double quotes become named entities.
The escaped version updates live in the right-hand panel.
Paste it between tags or inside a double-quoted attribute.
You are writing a docs page that shows a snippet like <button disabled>, and the browser keeps rendering an actual button. The angle brackets need to become entities before they go into the HTML. Paste the snippet here and copy the escaped version.
The encoder replaces four characters: & becomes &, < becomes <, > becomes > and the double quote becomes ". Everything else, including single quotes, accented letters and emoji, is left as it is, which is fine for UTF-8 pages. Output updates as you type, with Copy, Download, Sample and Clear buttons above the panels. Because & is always escaped, text that already contains entities gets escaped again, so < turns into &lt;. Encode raw text only.
Know what this protects and what it does not. Escaping these characters is the right treatment for text placed between tags or inside a double-quoted attribute. It is not enough inside a single-quoted attribute, a script or style block, or a URL attribute such as href, where different rules apply; use your template engine's context-aware escaping there. To reverse the process, the HTML entity decoder restores the original, and the HTML to plain text tool strips tags entirely when you only want the words.
The replacement is a handful of string operations in your browser tab, so snippets from private repositories are not sent anywhere.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
The encoder covers &, <, > and the double quote, which is enough for element content and double-quoted attributes. If the output goes inside a single-quoted attribute, replace ' with ' yourself or switch that attribute to double quotes.
No. Non-ASCII characters are left as they are, since any page served as UTF-8 displays them directly. Named entities for accented letters are only needed for legacy encodings.
For text inserted between tags, yes. For JavaScript strings, CSS, URLs in href or src, and unquoted attributes, no. Each context has its own escaping rules, so rely on a framework that escapes by context in application code.