URL Encoder & Decoder
Percent-encode and decode URLs and query strings.
Runs in your browser — your text never leaves your device.
Save this tool
Keep URL Encoder & Decoder handy
Use your browser's Share menu, then “Add to Home Screen”.
URL breakdown
About this tool
URLs may only contain a limited set of characters, so anything else has to be percent-encoded: a space becomes %20, an ampersand becomes %26, and so on. Getting this wrong is how query parameters silently break, usually when a value contains an ampersand or a plus sign and the server reads it as structure rather than content. This tool offers both encoding modes, and the difference matters. Component mode escapes the reserved characters too, which is what you want for a value going inside a query string or path segment. Full mode leaves the URL's own structure alone, so you can tidy a complete link without destroying it. Decoding gives you clear feedback rather than a silent failure when the input contains a stray percent sign. There is also a breakdown view that splits any URL into its scheme, host, path, query parameters and fragment, which makes a long tracking-laden link readable at a glance. Everything runs locally in your browser.
How to use it
- Paste a URL, a query value, or an encoded string
- Choose component or full-URL mode, then Encode or Decode
- Copy the result, or expand the breakdown to inspect the parts
Frequently asked questions
What is the difference between the two modes?
Component mode escapes reserved characters such as &, ?, =, / and #, so it is correct for a single value going inside a URL. Full mode leaves those intact so a complete URL stays functional. Using full mode on a query value is the classic cause of parameters breaking.
Why does my space sometimes become %20 and sometimes a plus?
Percent-encoding uses %20 everywhere. The plus sign comes from the older form-encoding rules used in application/x-www-form-urlencoded bodies and some query strings. Both appear in the wild, so servers usually accept either, but %20 is the safer choice.
Why does decoding fail with an error?
Almost always because the input contains a percent sign that is not followed by two hexadecimal digits, which is invalid. That happens when a literal percent character was never encoded in the first place, or when a string was decoded twice.
Is it safe to paste a URL containing a token?
Yes. Encoding and decoding happen entirely in your browser, so nothing you paste is transmitted or logged. That said, treat any URL containing a session token as a secret regardless of what tool you use.