Content · Web Development · HTML

HTML URL Encoding Reference: Reserved and Unsafe Characters

A clear, practical lookup reference to HTML URL Encoding Reference: Reserved and Unsafe Characters. Learn when to use it, see working HTML, and avoid common mistakes.

1 views Published Oct 19, 2026 Updated Oct 19, 2026 Admin

This is a practical reference for understand when url special characters must be percent-encoded. Keep it nearby when you are writing a page, but do not worry about memorizing every entry at once.

What this reference covers


Understand when URL special characters must be percent-encoded. The entries below summarize the most useful choices and what each one means.

Value or itemWhat it means
SpaceEncoded as %20 in path components
#Fragment separator
?Query delimiter
&Query parameter separator
%Start of percent-encoding
/Path separator
encodeURIComponentEncodes query value in JS

See it in HTML


A small example shows how one of these ideas appears in a normal page:

<section>
    <a href="/search?q=HTML&amp;sort=newest">Find HTML lessons</a>
</section>

How to use the reference


Begin by identifying what the page is trying to achieve. Then choose the entry that describes that job, instead of choosing a setting merely because it looks familiar.

Read the code from the outer element inward. Pay attention to attribute names, tag nesting, and any links between elements through IDs. A browser may accept some incorrect markup, but accepting it is not the same as using it correctly.

A useful check before publishing


Try changing one choice in the example while keeping the rest of the page the same. Inspect the result in your browser. For compatibility-sensitive features, test another browser; for accessibility-sensitive features, use keyboard navigation and an accessibility inspector.

Some entries describe browser hints rather than guarantees. User input still needs server-side validation, and event-based behavior needs JavaScript even if the HTML describes the control.

Common Beginner Mistakes


  • Treating every item in a reference list as interchangeable instead of choosing the one that matches the job.
  • Copying reference markup without checking the element’s surrounding context or required attributes.
  • Assuming one successful browser test proves the markup is accessible or universally supported.

Key Takeaways


  • Understand when URL special characters must be percent-encoded.
  • Pick a setting for its meaning, then test the smallest working example.
  • HTML references are most useful when combined with validation, browser inspection, and accessibility testing.
Share this resourceSend this page to someone who may find it useful.