About Parse URL
Use the URL parser online to inspect an absolute HTTP or HTTPS link. It can parse repeated URL query parameters into an ordered list without collapsing repeated names. The browser's standard URL parser normalizes the URL; no destination is fetched.
How to inspect the parts of an HTTP URL
- Paste a complete HTTP or HTTPS URL.
- Select Process to parse and serialize its components.
- Review the JSON, noting decoded query values and any exposed credentials, then copy or download it.
A practical example
- Input
https://example.com/a?tag=one&tag=two#part
- Result
{ "href": "https://example.com/a?tag=one&tag=two#part", "protocol": "https:", "origin": "https://example.com", "hostname": "example.com", "port": "", "pathname": "/a", "hash": "#part", "username": "", "password": "", "query": [ { "name": "tag", "value": "one" }, { "name": "tag", "value": "two" } ] }
Both tag parameters remain present and keep their original order.
Supported input and limitations
- Input is limited to 5 MB. Relative links, mailto, file, and custom schemes are not supported. Standard URL normalization can change the serialized spelling or omit a default port.
- Query values use URLSearchParams rules, including + as space. Embedded credentials and tokens can appear in output; this tool is excluded from workspace recovery, but copied or downloaded results can expose them.
Processing happens on your device. Read about local processing and optional workspace recovery.
Frequently asked questions
Will repeated query parameter names be lost?
No. Parameters are serialized as an ordered array of name/value pairs, so repeated names remain separate entries.
Does the URL parser open the destination?
No. It only parses the supplied string. A successful parse does not establish that the destination exists or is safe.