Space becomes `%20`
A visible example that shows why raw text should not be dropped directly into a URL.
hello world -> hello%20world URL & Web 5 min read 2026-03-10
URL Encoding Explained for Query Strings and Debugging
Understand percent-encoding, when it matters, and how to encode or decode URLs safely when debugging web requests.
Intro
URL encoding looks trivial until a request breaks because spaces, ampersands, question marks, or Unicode characters were interpreted as structure instead of data.
Percent-encoding is one of those web fundamentals that becomes visible only when something goes wrong.
What is it?
URL encoding replaces characters that are unsafe or reserved in a URL with percent-based escape sequences.
It is especially important inside query strings, path segments, and form submissions.
Why it matters
- Incorrect encoding breaks links, API requests, redirects, and tracking parameters.
- Decoding is often necessary when debugging logs or copied URLs from browsers and proxies.
- Correct encoding prevents special characters from changing the meaning of the URL.
Examples
Reserved characters need care
Characters like `&` or `=` have structural meaning inside query strings.
Common mistakes
- Encoding an entire URL when only one parameter value should be encoded.
- Double-encoding already encoded text.
- Reading encoded logs without decoding them first.
- Confusing form encoding behavior with raw URL component encoding.
FAQ
Should I encode the whole URL or only values?
Usually only the dynamic component you are inserting, such as a query parameter value or path segment, should be encoded.
Why does `%2520` appear instead of `%20`?
That usually means the data was encoded twice. `%25` is the encoded form of the percent sign itself.