Break a URL into its protocol, host, path and query parameters.
Parsed locally in your browser.
How do you parse a URL into its parts?
A URL is parsed with the standard browser URL API, which splits it into protocol, hostname, port, path, search (query) and hash. Query parameters follow the "?" separated by "&", and the hash ("#") points to a page section. For example, https://shop.example.com:8443/cart?id=42#reviews has host shop.example.com, port 8443, path /cart, query id=42 and hash reviews.
Understanding your result
Query parameters follow the “?” and are separated by “&”. The hash (“#”) points to a section within the page.
Formula and method
The URL is parsed with the standard browser URL API, which splits it into protocol, hostname, port, path, search (query) and hash.
Assumptions and limitations
Parsing uses the browser's standard URL API, which expects an absolute URL with a scheme; relative paths and malformed strings may fail or normalise unexpectedly. It shows decoded query values but does not follow redirects, resolve the host, fetch the page or interpret fragment routing used by single-page apps.
Worked example
https://shop.example.com:8443/cart?id=42#reviews has host shop.example.com, port 8443, path /cart, query id=42 and hash reviews.
How to use this tool
- Paste a full URL including http:// or https://.
- Read the components and query parameters.
Common mistakes to avoid
- Leaving off the scheme — a URL needs http:// or https:// to parse as absolute.
About the URL Parser
Paste a URL to see all of its parts — protocol, host, port, path, hash and each query parameter — laid out clearly.
Who should use this tool
Developers debugging links, redirects, tracking parameters and APIs.
Benefits
- See every URL component laid out at a glance
- Read each query parameter as a clear key-value pair
- Rely on the same parser browsers use natively
- Inspect URLs privately with nothing sent anywhere
Practical use cases
- Debug tracking parameters on a marketing link
- Check the host, port and path of an API endpoint
- Decode and read encoded query values quickly
- Confirm a redirect URL is formed as expected
Explore all Developer Tools tools
Frequently asked questions
Does it decode query values?
Yes. Percent-encoded parameter values are shown decoded.
Is my URL sent anywhere?
No. Parsing happens entirely in your browser.
Can I parse a relative URL like /cart?id=42?
The standard URL parser expects an absolute address with a scheme, such as https://example.com/cart?id=42, so a bare relative path may not parse on its own. Prefix it with a base origin to resolve it correctly. Once absolute, every part including the query and hash is broken out clearly.