Why does parsing fail on a URL without https:// in front?

The tool uses the browser's URL constructor, which requires an absolute URL with a scheme; paste the full address including http:// or https:// rather than just a bare domain or path.

How are repeated query parameters like page=1&page=2 shown?

The parameter list panel shows each occurrence separately in order, and the JSON representation groups repeated keys into an array of values instead of keeping only the last one.

Does parsing a URL here send it to a server first?

No, splitting the URL into its parts is done entirely with the browser's built-in URL API running on the page, so a link containing an auth token or session parameter is never transmitted anywhere to be parsed.

Does this tool show me the username and password in a URL?

Yes, if the URL includes userinfo like https://user:pass@host, the username and password fields are extracted and shown separately in the components table alongside the rest of the parts.

URL Parser

Break a URL into protocol, host, path, query parameters and fragment, locally.

Local, Runs entirely in your browser, your data never leaves your device.

Loading tool…

Break a URL down into its component parts

Paste a URL and this tool runs it through the platform's built-in URL parser to split it into protocol, username, password, hostname, port, origin, path, hash and a full list of query parameters, duplicates preserved in order. It's useful when you're debugging a redirect chain, checking what a third-party link actually points at, or verifying that a query string was built correctly. Because parsing happens with the browser's own URL API, nothing about the link is requested or sent anywhere.

How to use the URL Parser

Paste a full URL into the input field, including its scheme, such as https://.
Read the Components panel for protocol, hostname, port, path, credentials and fragment.
Check the Query parameters panel for every key/value pair, in the order they appear in the URL.
Copy the JSON representation, or use Send To to pass it into another tool.

Query parameters are also offered as a JSON object, where a key that repeats in the URL (like tag=a&tag=b) becomes a JSON array of values rather than overwriting the earlier one, matching how the query string tool treats duplicates.

Parsing requires an absolute URL, since it's built on the WHATWG URL constructor; a bare path or hostname without a scheme will fail to parse rather than being guessed at.

Frequently asked questions

Why does parsing fail on a URL without https:// in front?: The tool uses the browser's URL constructor, which requires an absolute URL with a scheme; paste the full address including http:// or https:// rather than just a bare domain or path.
How are repeated query parameters like page=1&page=2 shown?: The parameter list panel shows each occurrence separately in order, and the JSON representation groups repeated keys into an array of values instead of keeping only the last one.
Does parsing a URL here send it to a server first?: No, splitting the URL into its parts is done entirely with the browser's built-in URL API running on the page, so a link containing an auth token or session parameter is never transmitted anywhere to be parsed.
Does this tool show me the username and password in a URL?: Yes, if the URL includes userinfo like https://user:pass@host, the username and password fields are extracted and shown separately in the components table alongside the rest of the parts.