Redirect URL decoder
Detect and extract the real destination from Google AMP (google.com/amp/s/...), Google Search redirects (/url?q=), YouTube short links, Facebook l.php?u=, Outlook SafeLinks, Bitly preview pages, LinkedIn lnkd.in previews, and t.co preview-page URLs — all pattern-based, no network call.
Chain
Original URL
How to use
- Paste a wrapped URL.
- The tool detects the wrapper type and shows the Original URL in plain text. If multiple wrappers are nested, it unwraps them recursively and shows the full chain.
- Copy original grabs the cleanest destination.
- The Why panel explains which wrapper was detected and what it does.
Recognised wrappers
- Google AMP cache —
google.com/amp/s/example.com/page - Google search redirect —
google.com/url?q=https://... - Facebook —
l.facebook.com/l.php?u=... - Outlook SafeLinks —
safelinks.protection.outlook.com/?url=... - YouTube short —
youtu.be/ID→youtube.com/watch?v=ID - Generic redirectors — any URL with a
?url=,?redirect=,?to=, or similar param that containshttps://...
FAQ
Why can't this follow a Bitly / lnkd.in / t.co redirect?
Those services encode the destination on the server side, not in the URL — there's no in-URL pattern to extract. CORS prevents the browser from following them. Use the curl snippet shown in the tool footer.
What if the URL is wrapped multiple times?
The tool unwraps recursively up to 8 layers, stopping when it sees a URL it can't simplify further.
Is this safe?
The tool only parses the URL string — it doesn't visit anything. Whether the eventual destination is safe is a separate question; use the fingerprint for a quick sanity check.
Can I add custom redirector patterns?
Generic ?url= / ?redirect= / ?to= params are already auto-detected. For something more specific, fork the page source — the patterns live in tool.js.