Fixing a broken search URL
Before
URL with a space broke the request
After
Space encoded as %20, request went through
This was in a marketing email. The broken link was silently losing clicks. Fixed in 10 seconds.
I built this when I kept seeing broken URLs from OAuth callbacks and tracking links — spaces becoming `%20`, ampersands breaking query strings. Paste a URL, encode or decode, and see what's actually going on.
Your files are processed in your browser and never uploaded to any server.
The most common mistake I see: encoding a whole URL instead of just the parameter value. If you encode `https://example.com/search?q=hello world` as one string, the `:` and `/` and `?` also get encoded — and the URL stops working. Encode only the value: `hello%20world`. This tool follows `encodeURIComponent`, which is what you actually want for parameters.
— Mirza Noman Baig
These are actual measurements from using this tool, not estimates.
Before
URL with a space broke the request
After
Space encoded as %20, request went through
This was in a marketing email. The broken link was silently losing clicks. Fixed in 10 seconds.
Before
Callback URL arrived with %26 in the query
After
Decoded — the %26 was actually an & that got double-encoded
Double-encoding was the bug. This tool made it obvious.
Before
Search term 'coffee & tea' broke the query
After
Encoded to 'coffee%20%26%20tea'
The ampersand was being parsed as a query separator. Encoding fixed it.
Both directions in one tool, with a swap button to flip.
Matches the JavaScript standard for URL parameter encoding.
Safe for API requests, OAuth callbacks, and tracking links.
URLs with tokens or keys never leave your browser.
Just the parameter value. Encoding the whole URL breaks the `://` and the `?`. Use this tool on individual values.
Yes. Same behavior as JavaScript's encodeURIComponent, which is what you want for query strings and path segments.
No. Everything runs in your browser. Your URLs never leave your device.
URL encoding handles `&`, `?`, spaces, and special characters for URLs. HTML escaping handles `<`, `>`, `&` for HTML. Use the right tool for the right context.
Yes. Non-English characters get encoded as UTF-8 percent sequences, which is correct.