URL Encoder
Percent-encode a URL or query-string component for safe use in links.
Why unencoded URLs break
A raw space in a URL is often interpreted as the end of the address; an unencoded & inside a query value is read as a new parameter separator. Both silently corrupt the intended request.
Component vs full URL encoding
Encoding a full URL preserves structural characters like / and ? so it still resolves. Encoding a single value meant for a query string also escapes those characters, since otherwise they would be misread as part of the URL structure.
Common Mistakes to Avoid
Encoding an entire URL as a single component
Solution:
Component encoding escapes / and ? too, which breaks a full URL's structure. Use full URL encoding for a whole address, and component encoding only for a single value being inserted into it.
Double-encoding a URL
Solution:
Encoding an already-encoded string turns "%20" into "%2520", which will not decode correctly. Always check whether a value is already encoded first.
Frequently Asked Questions
Full URL encoding preserves structural characters like / and ?. Component encoding escapes those too, for values meant to sit inside a single query parameter.
No — encoding happens entirely in your browser.
Why unencoded URLs break
A raw space in a URL is often interpreted as the end of the address; an unencoded & inside a query value is read as a new parameter separator. Both silently corrupt the intended request.
Component vs full URL encoding
Encoding a full URL preserves structural characters like / and ? so it still resolves. Encoding a single value meant for a query string also escapes those characters, since otherwise they would be misread as part of the URL structure.