URL Encoder & Decoder
Parts of this URL
Query parameters
| Name | Value (decoded) |
|---|
Why URLs need encoding
A URL may only contain a limited set of characters, and several of those carry structural meaning:
? starts the query, & separates parameters, # starts the
fragment. Anything else — a space, an ampersand inside a value, Hindi text, an emoji — has to be
written as percent codes so it is not mistaken for structure.
Which mode to use
- Component — for one value you are about to put into a URL. Escapes everything, including the structural characters.
- Full URL — for an entire address you want to make safe without breaking it apart.
Share this tool with friends
Free to use, no sign-up, works on any phone.
Frequently Asked Questions
Component mode escapes everything that is not a plain character, including & = ? and /. Full-URL mode leaves those alone because they are structural. Use component mode for a single value, full-URL mode for a whole address.
Percent-20 is correct in a path and works everywhere. The plus sign is a form-submission convention that only applies inside a query string, which is why a plus in a path means a literal plus.
Yes. Each Devanagari character is three bytes in UTF-8, and each byte becomes a percent code, so one letter becomes nine characters. Decoding gives you the original text back unchanged.
It splits the query string into its individual parameters and decodes each value, which is far quicker than reading a long URL by eye when you are debugging a redirect or a tracking link.
No. It uses the browser's own encoding functions, so a URL containing a session token or a customer id stays on your device.