How to Parse a URL
Paste an absolute URL including its scheme, then choose Parse URL. The result lists protocol, hostname, port, pathname, search, hash, username, password and origin. Copy one value or the full JSON result. Clear removes the input and result. A relative path needs a base URL and is rejected by this tool rather than assigned an invented host.
URL Components and Normalization
Parsing uses the browser URL implementation. It can normalize hostnames, encode characters and omit a default port. The protocol includes its trailing colon; search and hash retain their leading punctuation. An opaque scheme may have the origin null. Parsing checks URL structure only; it does not prove that a destination exists, is safe or is reachable.
Query Parameters and Credentials
Query parameters are displayed in order, including repeated names. URLSearchParams decodes percent escapes and treats a plus sign as a space. Username and password fields show the URL API representation, which may remain percent-encoded. Pasted credentials are displayed locally, so avoid sharing screenshots or copied output containing secrets. This tool never opens or fetches the URL.
Standards and references
Frequently asked questions
Does URL Parser visit the address?
No. It parses text locally without DNS lookup or a request to the destination.
Can I parse a relative URL?
Enter an absolute URL with a scheme, such as https://example.com/path. Relative paths require a base and are not accepted here.
Why did the hostname or port change?
The standard URL parser normalizes parts of the address, including hostname spelling and default ports. Results describe the parsed URL, not a byte-for-byte transcription.
Are repeated query parameters preserved?
Yes. Query parameters are shown as an ordered list so duplicate names are not overwritten.