URL Parser
Break a URL into protocol, host, port, path, query and fragment.Developer ToolsURL Parser
Split a URL into protocol, host, port, path, query parameters and fragment.
Must be absolute (with protocol). One entry per query parameter is listed below.
About this tool
Tracking parameters, hash routes and odd ports are easy to miss by eye. Paste a URL and each component is listed separately, with every query parameter decoded onto its own copyable row.
How to use the URL Parser tool
- Paste an absolute URL. It must include the protocol; relative paths are rejected with a clear message.
- Read the parts. Protocol, host, port, path, query string and fragment are listed with copy buttons.
- Inspect parameters. Each query parameter appears decoded on its own row.
Supported formats
Input
- An absolute URL
Output
- Protocol, host, port, path, query, fragment
- Decoded query parameter list
Inputs are validated before anything is processed. Invalid values and unsupported files are rejected with a clear error instead of failing silently.
Frequently asked questions
Why must the URL be absolute?
The WHATWG URL parser needs a scheme to split the rest; "example.com/path" alone is ambiguous.
Are query values decoded?
Yes. Percent-encoded values such as %20 are shown decoded, which is usually what you want to read.
Is the default port shown?
Ports are only listed when the URL includes one explicitly; otherwise you see (default).
Are international domains handled?
Yes, the browser's URL parser handles IDN hosts and percent-encoded paths.
Privacy
Everything you enter stays in this browser tab. There is no upload endpoint for tool inputs, no account, and no server-side copy of your text or files. Results are produced locally and disappear when you close the page.
No account is required and no file is ever uploaded. See the privacy policy for details about analytics and the limited data this site stores.
Known limitations
- Relative URLs are rejected instead of guessed against a base.
- No modifications — this tool reads URLs, it does not rewrite them.
- Credential parts (user:pass@) are parsed but not displayed.
Related tools
Other free tools from the same collection.