URL Parser
Split URLs into parts with decoded query parameters
Input URL
Parsed Result
Query Parameters
| Parameter | Value |
|---|
How to Use
When you are debugging redirects, checking callback addresses or picking apart a marketing link, you often need to see a long URL in pieces: which scheme it uses, what port hides behind the domain, which endpoint the path targets, what the query string actually carries, and where the fragment points. URLs copied from address bars or server logs usually contain percent-encoded characters that are hard to read by eye. This tool uses the browser native URL parser to take the whole thing apart in one step.
Paste a full URL (it must include the scheme, e.g. starting with https://) and hit Parse: you get protocol, host, port, path, fragment and origin at once, and the port is marked as default when the URL omits it. The query table below decodes every parameter name and value into plain text, listing repeated parameters line by line - handy for verifying signature strings or tracking parameters. Everything runs locally; the URL never leaves your browser.
FAQ
Why does it say the URL cannot be parsed?
Browsers require a scheme before a URL can be parsed, so entering just example.com/path is treated as incomplete. Add https:// in front and try again. The scheme does not have to be http or https - ftp://, ws:// and others work too.
Are query parameter values shown decoded?
Yes. The table turns percent-encoding back into plain text, e.g. %E4%B8%AD displays as the character it encodes. Values that cannot be decoded are shown as-is without affecting other parameters. To re-encode, pair this tool with the URL encoder.
Why does the port show as the default port?
When the URL omits the port, browsers fill in the scheme default: 80 for http and 443 for https. The port field then shows that default instead of a blank, reflecting the port actually used; explicitly written ports are displayed unchanged.