%

URL Decoder

Decode URL encoded text back to readable format

About the URL Decoder

This tool URL decodes percent-encoded text back into readable characters, turning %20 into a space and %26 into an ampersand. It is how you read what a long tracking URL or redirect chain actually contains.

To URL decode a value is to reverse percent-encoding so the URL becomes readable. A string full of %20, %2F and %3A is unpleasant to parse by eye, and the parameters you actually care about are usually buried inside it.

The common case is a redirect or tracking URL where an entire other URL has been encoded and embedded as a parameter. Decoding reveals the destination — useful for checking where a link really goes, and for debugging an OAuth or SSO flow where the return URL is nested inside the request.

Double encoding is worth watching for. If decoding leaves you with %2520 rather than a space, the value was encoded twice and needs decoding again — a frequent bug when a URL is built by code that has already been escaped once.

How to use the URL Decoder

  1. Paste the encoded text. Enter the URL or percent-encoded value.
  2. Decode it. Percent escapes are converted back to characters.
  3. Check for double encoding. If you still see %25 sequences, decode again.
  4. Copy the result. Take the readable value.

URL Decoder features

  • Decodes percent-encoded text and full URLs
  • Handles UTF-8 multi-byte escapes
  • Reveals URLs nested inside query parameters
  • Makes double encoding visible
  • Instant results as you type
  • Runs entirely in your browser

Frequently asked questions

What does URL decoding do?

It converts percent escapes back to characters, so %20 becomes a space and %26 becomes an ampersand.

Why is a whole URL inside my parameter?

Redirect and tracking links embed the destination as an encoded parameter. Decoding reveals where the link actually goes.

What if I still see %25 after decoding?

The value was encoded twice. Decode it again to get the original text.

Are accented characters handled?

Yes. UTF-8 multi-byte escape sequences are decoded back to the correct characters.

Is my input uploaded?

No. Decoding happens entirely in your browser.