What Is URL Encoding and When Do You Need It? (With Examples)

URLs can only safely contain a specific set of characters. Spaces, special symbols, non-ASCII characters, and reserved characters in URLs all need to be encoded before they can be transmitted reliably. If you have ever seen %20 in a URL, you have seen percent-encoding in action. Here is what it does, when you need it, and how to encode and decode URLs instantly.

What is URL encoding (percent-encoding)?

URL encoding, formally called percent-encoding, converts characters that are not allowed or have special meaning in URLs into a safe representation. Each unsafe character is replaced by a % followed by two hexadecimal digits representing the character's ASCII or UTF-8 byte value.

Examples:

• Space → %20 (or + in form data)
• & → %26
• = → %3D
• / (in a parameter value) → %2F
• @ → %40
• Unicode characters like é → %C3%A9 (UTF-8 bytes)

Why URL encoding is necessary

URLs were originally designed for ASCII text in a strict format:scheme://host/path?query#fragment. Specific characters in this structure have reserved meanings:

• / separates path segments
• ? begins the query string
• & separates query parameters
• = assigns query parameter values
• # begins a fragment identifier

If your query parameter value contains any of these characters (e.g. a URL containing another URL, or a search query containing “&”), the URL parser will misinterpret them. Encoding the special characters prevents this.

When do you need to URL-encode manually?

• Building URLs with user input — If a user types a search query with spaces or special characters, encode it before appending to a URL.
• Passing URLs as query parameters — A URL inside another URL must be encoded so the outer parser does not interpret the inner URL's characters.
• Encoding non-ASCII text in URLs — International characters (accented letters, CJK characters, Arabic) must be UTF-8 encoded and then percent-encoded for URLs.
• Debugging API requests — Decode URL-encoded strings from API logs or error messages to read the original values.
• Working with email links — mailto: links in HTML that include a pre-filled subject or body require URL encoding.

Step-by-step: encoding and decoding URLs with ToolsGravity

1. Open the URL Encoder / Decoder and paste the text or URL you want to process.
2. Click Encode to convert special characters to their percent-encoded equivalents.
3. Click Decode to convert percent-encoded sequences back to their original characters.
4. For full URL encoding (encoding the entire URL including reserved characters), use the “Encode entire URL” option. For component encoding (only encoding a value that will be used inside a URL), use “Encode component.”

URL encoding vs HTML encoding: what is the difference?

All three serve different purposes and should not be confused. For HTML-specific encoding, use the HTML Encoder / Decoder tool instead.

Common URL encoding mistakes

• Double encoding — If you encode an already-encoded URL, the % itself gets encoded to %25, producing%2520 instead of %20. Always decode before re-encoding.
• Encoding the whole URL when you should only encode components — Encoding the full URL (including ://, /, and ?) breaks the URL structure. Only encode the values within the URL.
• Not encoding non-ASCII in paths — International characters in URL paths (common in CMS-generated URLs) must be properly percent-encoded for maximum compatibility.

Summary

URL encoding is a fundamental web concept that every developer and anyone working with web APIs needs to understand. The ToolsGravity URL Encoder / Decoder handles both directions instantly — encode for safe URL construction, decode to read obfuscated URL parameters. Remember the key distinction: encode components (parameter values), not entire URLs.