Home/ Questions/Q 6544083
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T11:25:24+00:00

Are they the same as XML, perhaps plus the space one (   )?

  • 0

Are they the same as XML, perhaps plus the space one ( )?

I’ve found some huge lists of HTML escape characters but I don’t think they must be escaped. I want to know what needs to be escaped.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you’re inserting text content in your document in a location where text content is expected1, you typically only need to escape the same characters as you would in XML. Inside of an element, this just includes the entity escape ampersand & and the element delimiter less-than and greater-than signs < >:

    & becomes &amp;
< becomes &lt;
> becomes &gt;

    Inside of attribute values you must also escape the quote character you’re using:

    " becomes &quot;
' becomes &#39;

    In some cases it may be safe to skip escaping some of these characters, but I encourage you to escape all five in all cases to reduce the chance of making a mistake.

    If your document encoding does not support all of the characters that you’re using, such as if you’re trying to use emoji in an ASCII-encoded document, you also need to escape those. Most documents these days are encoded using the fully Unicode-supporting UTF-8 encoding where this won’t be necessary.

    In general, you should not escape spaces as &nbsp;. &nbsp; is not a normal space, it’s a non-breaking space. You can use these instead of normal spaces to prevent a line break from being inserted between two words, or to insert          extra        space       without it being automatically collapsed, but this is usually a rare case. Don’t do this unless you have a design constraint that requires it.

    1 By "a location where text content is expected", I mean inside of an element or quoted attribute value where normal parsing rules apply. For example: <p>HERE</p> or <p title="HERE">...</p>. What I wrote above does not apply to content that has special parsing rules or meaning, such as inside of a script or style tag, or as an element or attribute name. For example: <NOT-HERE>...</NOT-HERE>, <script>NOT-HERE</script>, <style>NOT-HERE</style>, or <p NOT-HERE="...">...</p>.

    In these contexts, the rules are more complicated and it’s much easier to introduce a security vulnerability. I strongly discourage you from ever inserting dynamic content in any of these locations. I have seen teams of competent security-aware developers introduce vulnerabilities by assuming that they had encoded these values correctly, but missing an edge case. There’s usually a safer alternative, such as putting the dynamic value in an attribute and then handling it with JavaScript.

    If you must, please read the Open Web Application Security Project’s XSS Prevention Rules to help understand some of the concerns you will need to keep in mind.

    • 0