Percent-encode text for a URL, decode an encoded link back to readable text, and see every query parameter laid out in a table.
Paste a link with a ? in it, or a query string like a=1&b=2, in the input box to list its parameters here, decoded.
| # | Key | Value (decoded) |
|---|
Your links never leave your device. Everything is processed in this browser tab.
A URL may only contain a limited set of characters: letters, digits and a few symbols. Everything else, including spaces, Hindi text, emoji and symbols that have a job inside a URL such as &, = and ?, has to be written as percent-encoding. Each byte of the character's UTF-8 form becomes a % sign followed by two hexadecimal digits. A space becomes %20, the rupee sign becomes %E2%82%B9, and the Hindi word "नमस्ते" becomes six three-byte groups. The rules come from RFC 3986, the standard that defines URL syntax.
These are the two built-in JavaScript functions, and choosing the wrong one is the most common URL bug.
- _ . ! ~ * ' ( ). Use it for one piece you are about to insert into a URL: a search term, a query parameter value, a file name or a path segment. It turns /, ?, & and = into codes, so a value like "M/L & XL" cannot break the URL around it.: / ? # & =, and only encodes spaces and characters that are never allowed. Use it to clean up a complete link that has spaces or non-English text in it.HTML forms submitted with GET use a slightly different style in which a space becomes + instead of %20. Tick "Use + for spaces" to produce or read that form. When it is off, a + in encoded text is kept as a literal plus sign.
The browser's own decoder gives up completely on the first bad sequence with a "URI malformed" error. This decoder keeps going: it decodes every valid sequence, leaves a broken one exactly as typed, and lists each problem with its position. A broken sequence is a % not followed by two hex digits, such as the "50%" in a discount code, a byte that cannot start a UTF-8 character, or a multi-byte character that was cut short when a link was truncated.
Paste any link and the parameters after the ? appear in a table, one row each, with keys and values decoded. Repeated keys appear as separate rows, a key with no = is marked as having no value, and anything after # is ignored because the fragment is never sent to the server. This is handy for reading tracking links, checking which UTM tags a campaign URL carries, or debugging a search page.
Encoding the search phrase "red saree & dupatta" as a value gives red%20saree%20%26%20dupatta. Without encoding, the & would start a new parameter and the server would see a search for "red saree " plus a parameter called " dupatta" with no value. Paste ?q=red+saree&size=M%2FL with decoding on and the table shows q as "red saree" and size as "M/L".
Links often contain session tokens, email addresses or order numbers. Here they are processed by your browser only and never sent to Ur Next Door. The tool encodes text as UTF-8, which every modern site expects; very old systems that used other character sets will decode such links differently.
