URL Parser
Break a URL into its parts and decode each query parameter.
Breaks a URL into its components and decodes each query parameter.
About URL Parser
The URL Parser dissects any URL into its parts — protocol, credentials, host, port, path, query parameters and fragment — and decodes each query value for you. Long URLs from redirects, OAuth flows, tracking links and log lines are nearly unreadable raw; parsed and decoded, they explain themselves.
Every query parameter is listed as a decoded key–value row, so double encoding, unexpected parameters and mangled values stand out immediately. It is the natural companion to the Query Parameter Builder: one takes URLs apart, the other puts them together.
How to use
- Paste the full URL into "URL".
- Read the breakdown: protocol, host, port, path, fragment and any embedded credentials.
- Review the query parameter table — each value is shown percent-decoded.
- "Load sample" demonstrates a URL with credentials, an explicit port, repeated keys and encoded characters.
Frequently asked questions
Which parts make up a URL?
scheme://user:password@host:port/path?query#fragment. Most URLs use only a few parts, but auth flows and legacy systems exercise all of them — and each part has its own encoding rules.
Is the fragment (#…) sent to the server?
No — fragments stay in the browser. That is why OAuth implicit flows put tokens there, and why a server-side log will never show you what came after the #.
Why does a parameter value show as still-encoded after parsing?
That value was encoded twice (%2520 instead of %20 is the giveaway). Some component in the chain encoded an already-encoded value — a real bug worth reporting, and this view is how you catch it.