Decode a Nested Redirect URL

Decode a return_to / redirect parameter that is itself a URL. See the real destination hidden behind percent-encoding.

Part of the free URL Decoder. Runs in your browser — nothing is uploaded.

Decode a Nested Redirect URL

OAuth and login flows pass the destination as a query value, so the whole URL is percent-encoded. Decode that parameter to see where the user will land — and to spot open-redirect bugs.

Worked example: A return_to value

Encoded

https%3A%2F%2Fapp.example.com%2Fsettings%3Ftab%3Dbilling

Decoded

https://app.example.com/settings?tab=billing

Practical tip

After decoding, check the host. If it is not a host you own, do not redirect there.

How to use this URL Decoder

  1. 1Use the live tool above — it runs entirely in your browser and never uploads your data.
  2. 2Paste the sample from the worked example, or use your own input.
  3. 3Copy the result, then adapt the same steps in your editor, script, or pipeline.

Decode a Nested Redirect URL FAQs

Why is the redirect encoded twice?

Some proxies encode an already-encoded URL. Decode until you see a readable http(s) URL, then stop.

Is decoding a redirect URL safe?

Decoding is safe. Following an unvalidated decoded URL is not. Allow-list destinations on the server.