URL Encoder / Decoder
Percent-encode and decode URLs and query strings, with live results and a decoded parameter table — all in your browser.
encodeURIComponent · safe for values & queries (encodes &, =, ?, /)
🔒 Every conversion runs only in your browser — your input is never sent to a server.
What it does
Type or paste text or a URL and the encoded (or decoded) result appears instantly. For encoding you pick a scope: Component uses encodeURIComponent, which escapes everything — including &, =, ? and / — so a value slots safely inside a query string; Full URL uses encodeURI, which keeps the reserved : / ? & = characters so a whole address stays a working link. Decoding turns %20 and other percent sequences back into real characters and also treats + as a space, so strings that came from form submissions restore cleanly. If your input is a URL, its query parameters are broken out into a decoded name/value table below.
Which scope to use
Use Component when you're inserting a single value — a search term, a redirect target, a filename — into a query string or path segment, so its special characters can't break the URL structure. Use Full URL when you already have a complete address and only want to clean up characters like spaces or non-ASCII letters while leaving the link's delimiters intact. When in doubt for a single value, Component is the safer choice.
Private by design
Encoding, decoding and the parameter breakdown all run locally on your device. Nothing is uploaded, and the tool keeps working with the connection switched off, so you can safely work with links that contain tokens or personal data.
Frequently asked questions
What's the difference between encodeURIComponent and encodeURI?
Component mode (encodeURIComponent) escapes &, =, ?, / and more, so it's right for a single value inside a query or path. Full URL mode (encodeURI) preserves reserved characters like : / ? & = so it can encode an entire address without breaking it.
How are spaces and non-English characters handled?
Non-ASCII characters are encoded as UTF-8 byte sequences (e.g. %EC%95%88), and spaces become %20. When decoding, a + is also converted back to a space so strings from form submissions restore naturally.
Is my input sent to a server?
No. Encoding, decoding and the parameter table all happen inside your browser — nothing is ever uploaded.