URL Encoder / Decoder
Percent-encode text for safe use in URLs, decode %20-style sequences back to readable text, and break any URL into its parts with every query parameter decoded. Runs entirely in your browser.
New to this? Read the URL Encoder / Decoder guide →
Which encode mode do I want?
- Encode (component) — for a piece of a URL, like a query-string value. Encodes every reserved character, including
/,?and&. This is the one you want 90% of the time. - Encode (full URL) — for a complete URL that just needs unsafe characters (spaces, quotes, non-ASCII) escaped while keeping its structure intact.
- Decode — turns
%20-style sequences back into characters, and treats+as a space the way form submissions do.
Paste a full URL in any mode and the breakdown table shows its host, path and each query parameter decoded — the fastest way to read a long tracking link. Everything runs in your browser; nothing is uploaded. The guide explains percent-encoding, %20 vs +, and the double-encoding bug.
Where you'd use this
Constructing links that survive being pasted, and debugging ones that did not. Query strings break on spaces, ampersands and plus signs, and the failure usually shows up as a truncated parameter rather than an error.
For example: A tracking link ending ?utm_campaign=spring sale&ref=news loses everything after "spring". Encoding it to spring%20sale keeps the campaign name intact in analytics.
Frequently asked questions
What is URL encoding (percent-encoding)?
URLs may only carry a small set of safe characters, so everything else is escaped as a % followed by two hex digits per UTF-8 byte — a space becomes %20, é becomes %C3%A9. Encoding keeps your data from being confused with URL structure like ? and &.
What is the difference between %20 and +?
%20 is the true percent-encoding of a space and works anywhere in a URL. + means a space only inside query strings, a convention inherited from HTML form submissions. When decoding query strings this tool treats + as a space; when encoding it produces %20.
When do I use component mode vs. full-URL mode?
Component mode (encodeURIComponent) escapes everything including / ? and &, so use it for a value going into a URL, like a query parameter. Full-URL mode (encodeURI) keeps structural characters intact, so use it to clean up a complete URL without breaking it apart.
Is my text or URL uploaded?
No. Encoding, decoding and the URL breakdown all run locally in your browser — nothing you paste leaves the page.