AppHelp guide
URL Encoding vs Percent Encoding
Understand reserved URL characters, percent-encoded bytes, plus signs, query strings, and common double-encoding mistakes.
Quick answer
Percent encoding represents unsafe URL bytes as %HH. URL encoding is the practical process of applying percent encoding to URL components, query values, or form-style parameters depending on context.
Encode components, not whole URLs blindly
A full URL contains syntax characters such as :, /, ?, &, and #. Encoding a single component is different from encoding an entire URL string. Know whether your value is a path segment, query value, redirect URL, or full link.
Spaces can be %20 or plus
In many query-string and form contexts, plus signs can represent spaces. In path segments and strict component encoding, %20 is clearer.
Watch for double encoding
If a value contains %2520, it may have been encoded twice. Decode one layer at a time and verify whether the result is still intended to remain encoded inside another value.
Frequently asked questions
Should I encode a whole URL or only one component?
Usually encode the component you are inserting, such as a query value or path segment. Encoding a whole URL can change the syntax characters that make it work.
Why do spaces sometimes become plus signs in URLs?
Plus signs can represent spaces in form-style query strings. In path segments and strict URL components, %20 is usually clearer.