In this article
Why links look like this
When text that contains spaces, symbols or non-English letters goes into a web address, it is percent-encoded: each special character becomes “%” plus two hexadecimal digits. Tracking and redirect systems often place an entire web address inside another one, encoding it so it does not break – which is why some links are hundreds of characters of % codes.
How to decode
- Paste the link or text into the URL Decoder.
- Turn on “+ to space” if the text came from a form or search query, where “+” stands for a space.
- Read the decoded result. If a % sequence is malformed, the tool points to its exact position.
All UTF-8 sequences are decoded, so Urdu, Arabic, Chinese and emoji appear as real characters.
See where a redirect really goes
Email newsletters, ads and some search results wrap the destination in a tracking link, for example https://tracker.example/click?url=https%3A%2F%2Fshop.com%2Fsale%3Fid%3D7. Decoding shows the real destination: https://shop.com/sale?id=7. This is a useful safety habit – if a “bank” email decodes to an address that is not your bank’s real domain, do not click it.
Double encoding
If the decoded text still contains % codes – like %20 after one pass – the link was encoded twice. Decode again. The sign of double encoding is “%25”, the encoded form of the % sign itself. Double encoding is a common bug in websites and can break links; if you run a site and see “%2520” in your URLs, a script is encoding something that was already encoded.
Making long links readable
| Part | Example |
|---|---|
| Encoded | q=%D9%84%D8%A7%DB%81%D9%88%D8%B1%20weather |
| Decoded | q=لاہور weather |
For a structured view of a whole address – protocol, domain, path, each parameter and the fragment – paste it into the URL Parser, which also decodes each parameter value.
Cleaning links before sharing
Shared links often carry tracking parameters such as utm_source, fbclid or gclid. They are harmless but long and reveal where you found the link. Decode, check the parameters, and remove the ones you do not need before sharing – the page usually works the same without them.
When decoding fails
- “Malformed sequence”: a % sign is followed by something other than two hex digits – for example a real “100%” inside text. Check the position shown.
- Strange characters: the text may have been encoded in an old, non-UTF-8 character set.
- Still unreadable: the value may be Base64 rather than URL-encoded – try the Base64 Decoder.
Decoding happens in your browser; links you paste are not sent anywhere. To encode text for a URL, use the URL Encoder.