URL parser
Paste a URL and see every part of it, with the query parameters decoded.
- Runs in your browser — your text is never sent anywhere
- No sign-up, no quotas, free to use as often as you like
How it works
A long URL with a dozen tracking parameters is unreadable by design. Splitting it out shows what is actually being carried — which is useful for debugging, and quietly interesting when you look at what a marketing link contains.
Parsed by the browser itself
It uses the browser's own URL parser, the same code that runs when you click a link, so the result matches how a URL will genuinely be interpreted rather than how a regular expression guesses it might be. Edge cases around ports, credentials and unusual schemes behave correctly.
Parameters are decoded
Percent-encoding is undone, so %20 becomes a space and %40 becomes an at sign. Repeated parameters are all listed rather than collapsed, because a URL may legitimately carry the same key more than once and which one wins depends on the server.
Reading a tracking link
utm_source, utm_medium and utm_campaign are campaign tracking. gclid, fbclid and msclkid are click identifiers added by ad platforms, and they are what makes a shared link needlessly long — they can nearly always be deleted before you pass a link on.
The origin
Protocol, host and port together form the origin, which is the unit browsers use for security decisions. Two URLs with the same origin can read each other's data; a difference in any of the three, including http versus https, makes them separate.
URL parser — questions
Does it work without https at the front?
Yes. If the scheme is missing, https is assumed so the rest can be parsed.
Are the parameters decoded?
Yes, percent-encoding is undone so you see the real values.
What if a parameter appears twice?
Both are listed. Which one a server uses varies, so collapsing them would hide a real problem.
What is the origin?
Protocol, host and port together. Browsers use it for security decisions, and http and https are different origins.
Is the URL sent anywhere?
No. It is parsed in your browser.