URL encoder
What this URL encoder does
Percent-encoding replaces reserved characters (spaces, &, Unicode outside ASCII, slashes inside query values) with %HH escapes so URLs stay parseable in browsers, curl, and server frameworks. This tool helps you craft safe query parameters and path segments without hand-counting which symbols need escaping—especially when analytics labels contain ampersands or campaign names include emoji.
When to use it
Use it when constructing manual marketing links, reproducing server-side encoding bugs, or teaching juniors why + and %20 both appear in legacy logs. Encode each component—never an entire URL twice—or CDNs will serve double-encoded paths. Pair with URL decoder to verify symmetry, and with UTM link generator when you need structured campaign fields instead of ad hoc strings.
Worked example
A search filter called Tom & Jerry breaks GET requests. You encode the value to Tom%20%26%20Jerry, paste it into the query builder, and the API stops truncating at the ampersand boundary.
Frequently asked questions
Encode full URL or only pieces?
Encode individual query keys/values or ambiguous segments. Encoding an already-valid URL wholesale usually creates double-encoding bugs.
How does this differ from Base64?
Percent encoding keeps text mostly readable; Base64 targets arbitrary binary. Pick the format your transport expects.
Non-ASCII paths?
Modern browsers apply UTF-8 percent encoding (IRI). Older stacks may need explicit Unicode normalization—test end-to-end.