Developer Tools

How to Read Messy Links Full of % Codes

Links copied from emails, search results and ads are often a jumble of percent codes. Decoding them shows what they really say – and where they really go.

In this article
  1. Why links look like this
  2. How to decode
  3. See where a redirect really goes
  4. Double encoding
  5. Making long links readable
  6. Cleaning links before sharing
  7. When decoding fails

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.

URL DecoderDecode %20, %26 and other percent-encoded characters back into readable text. Handles UTF-8, optional + as space and explains malformed input.
Open the free tool

How to decode

  1. Paste the link or text into the URL Decoder.
  2. Turn on “+ to space” if the text came from a form or search query, where “+” stands for a space.
  3. 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.

PartExample
Encodedq=%D9%84%D8%A7%DB%81%D9%88%D8%B1%20weather
Decodedq=لاہور 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.

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.

URL DecoderDecode %20, %26 and other percent-encoded characters back into readable text. Handles UTF-8, optional + as space and explains malformed input.
Open the free tool
Keep reading

Related articles

All articles
Dev

URL Encoding Explained – Why Spaces Become %20

Paste a link with spaces, “&” or Urdu text and it can break. URL encoding fixes this by turning special characters into safe % codes.

3 min read
Web

The Anatomy of a URL – Every Part Explained

Web addresses look like random strings, but every part has a job. Understanding them helps with SEO, analytics, debugging – and spotting scam links.

3 min read
Dev

How to Decode Base64 into Text, an Image or a File

A long string of random-looking letters in a log, an email or an API response is often Base64. Here is how to see what is really inside.

3 min read