URL Decoder
Decode percent-encoded URL text.
Result appears here
Decode percent-encoded URL text.
Result appears here
Percent-encoded text shows up in places that were never meant to be read by people: server access logs, analytics exports, redirect links, error messages and the address bar after a search. A phrase like caf%C3%A9%20au%20lait%3Fq%3D1 is hard to scan. Paste it here and the readable version appears immediately in the result box, with no button to press. It is a small job, but doing it by eye is slow and easy to get wrong, especially with long strings of repeated codes.
The decoder uses the JavaScript function decodeURIComponent. It converts every %XX sequence back to the character it stands for and understands multi-byte UTF-8, so accented letters, non-Latin scripts and emoji come back correctly. Text that contains no percent sequences is returned unchanged, which makes it safe to paste something half-encoded. Nothing is stored or reformatted beyond the decoding itself, so what you see is exactly the text the escapes represent.
Two behaviors catch people out. A plus sign is not turned into a space, because decodeURIComponent treats it as an ordinary character; query strings from HTML forms often use plus for space, so you may need to replace those yourself. And a stray percent sign that is not followed by two valid hex digits makes the whole decode fail with an error. Knowing both behaviors up front saves a lot of confusion when a result looks almost right but not quite.
Access logs record requested paths exactly as they arrived, escapes included. Paste a path or query string from the log to see the search phrase, file name or parameter value the visitor actually sent. This is often the quickest way to understand traffic.
Marketing and login links often hide a destination address inside a parameter. Decode the value to see where the link really points before you click, or to confirm your own redirect is built correctly. Doing this takes a few seconds and can reveal unexpected hops.
A link copied from a browser may show a title or file name as a wall of %E2 and %C3 codes. Decoding restores the original wording so you can reuse it in a document or message. Check the result before reuse.
If a decoded result still contains percent signs, such as %20 where a space should be, the data was encoded twice. Decode it again to confirm, then fix the code that encoded it a second time. Fixing the source is better than decoding forever.
Decoding runs in your browser using a built-in JavaScript function. The text you paste stays on your device and is not sent to a server.
The text contains a percent sign that is not followed by two hexadecimal digits, or a sequence of escapes that does not form valid UTF-8. A common cause is a link that was cut off while copying. Fix or remove the broken piece and the rest will decode.
No. decodeURIComponent leaves plus signs unchanged. In form-style query strings, a plus often stands for a space, so swap them for spaces first if you want the text as the sender typed it. Alternatively, replace the plus signs with %20 before decoding, which gives the same outcome.
It is a space. The number after the percent sign is the character's byte value in hexadecimal, and 20 in hex is 32, the ASCII code for a space. Likewise %26 is an ampersand, %3D is an equals sign and %2F is a slash. Common neighbors you will meet in logs are %3A for a colon and %3F for a question mark.
Decode it once, look at the result, and if it still contains percent sequences, copy the output back into the input and decode again. Seeing %2520 in the original is the typical sign of double encoding. Stop once no percent sequences remain.
Yes, it will be converted back to readable characters, including the escaped separators inside parameter values. Keep in mind that the decoded text may no longer be a valid link, so use it for reading rather than for pasting back into a browser.
Each character outside basic ASCII is stored as two to four UTF-8 bytes, and each byte gets its own percent sequence. The decoder joins them again. If one byte is missing, the sequence is invalid and decoding fails.