URL Encoder and Decoder
Percent-encode or decode URLs and query strings — full-URL or component mode, with a live parameter breakdown.
Stays on your device. This tool runs in your browser — nothing you paste or open ever leaves it. Nothing uploaded, nothing to leak.
↳ received from
Query parameters
Help us improve
Was this tool useful? Tap a star.
Thanks — your rating helps others find it.
URL encoding (percent-encoding) replaces characters that are not safe in a web address — spaces, accents, symbols — with %xx codes so links and query strings survive transit. TechWhack encodes and decodes both ways, lets you choose whether to keep the URL structure (slashes, ?, and) or encode every character, and breaks a query string into a readable table of its parameters. It all runs in your browser.
Whole URL versus component
The two encoders exist for a reason. Whole-URL encoding leaves reserved characters like / ? : = intact, so a complete address stays usable. Component encoding escapes those too, which is exactly what you want when a value (an email, a redirect target, a search term) is going inside one query parameter. Picking the wrong one is the most common URL bug.
FAQ
When should I URL-encode the whole URL versus just a parameter?Encode a single component, like one query value, when you need to escape characters such as & or = that would otherwise break the URL structure. Whole-URL mode preserves the structural characters; this tool offers both modes so you do not over-encode a working link.
Why does a space become %20 or sometimes a plus sign?Spaces are not allowed in URLs, so they are percent-encoded as %20, and in older query-string contexts a space may appear as a plus sign. Decoding turns either form back into a normal space.
How can I see all the parameters in a long URL?Paste the URL and the query string is broken out into a parameter table, so each key and value is listed clearly. That makes it easy to inspect tracking links or API requests with many parameters.
What is the difference between URL encoding and Base64?URL encoding escapes only unsafe characters with percent codes so a string is valid inside a URL, while Base64 re-encodes all the data into a different character set. Use URL encoding for links and Base64 for embedding binary data in text.