URL Parser
Parse URLs into components and inspect decoded query parameters.
URL Parser
Parse a URL into protocol, hostname, port, path, query parameters, and hash. This is useful for debugging API endpoints, UTM links, redirects, and encoded query strings.
What gets extracted
- Protocol, origin, host, port, pathname, query string, and fragment
- Raw and decoded query parameters
- A structured JSON representation of the URL
How to use URL Parser
The URL parser breaks a URL into protocol, host, path, query parameters, and hash. It is useful when debugging redirects, links, and tracking URLs.
Developers often use this page when they need url parser, url checker, url validator, and query string parser.
Privacy and data handling
This tool can handle security-sensitive text, so it is meant for local inspection and test data.
- Normal use does not require uploading your input to a server.
- Use redacted tokens, passwords, secrets, headers, and connection strings when possible.
- Copy buttons use your browser clipboard permission, so clear the clipboard after handling secrets.
Examples
Break a URL into parts
Input
https://example.com/docs?page=2#introOutput
protocol: https
host: example.com
path: /docs
query: page=2
hash: introParsing is useful when debugging redirects and tracking links.
Steps
- 1Paste a full URL.
- 2Review each parsed part.
- 3Copy the piece you need, such as a query parameter or hostname.
Common use cases
- Debug a redirect URL.
- Inspect query parameters in a copied link.
- Check protocol, domain, path, and hash values.
Practical tips
- Make sure the URL includes protocol when parsing fails.
- Decode query values when they contain percent-encoded text.
- Be careful with URLs that include tokens.
FAQ
What parts does a URL have?
A URL can include protocol, username, password, hostname, port, path, query string, and hash fragment.
Why are query values hard to read?
They may be URL encoded. Decoding turns percent-encoded characters back into readable text.