How to use it
- Paste or type a full URL into the box, including its protocol, such as
https://. - The parts update live as you type, no button to press.
- Read off the protocol, host, port, path, query string, hash and origin, each in its own row.
- Scan the query parameter table to see every key and value, fully decoded.
- Press Copy on any row to grab that value for an API call, config or bug report.
Parsing runs on the browser's built-in URL object, the same engine the address bar uses, so the results match how a real browser reads the link. If the URL is missing a protocol or is malformed, you get a clear error instead of a wrong answer.
Parts of a URL
A URL looks like one long string, but it is made of distinct pieces. Here is what each row means.
- Protocol, the scheme at the start, like
https:orftp:. It tells the client how to reach the resource. - Host, the hostname such as
example.com. This is the server the request is sent to. - Port, the network port, like
8080. It is often blank, which means the protocol's default (443 for HTTPS, 80 for HTTP). - Path, everything after the host, such as
/blog/post. It points at a specific page or file on the server. - Query, the part after the
?, like?q=astro&page=2. It carries named parameters, shown one per row in the table. - Fragment, the part after the
#, like#section. The browser uses it to jump to a spot on the page and it is never sent to the server.
The origin is the protocol, host and port combined, such as https://example.com:8080. It is the identity browsers use for security rules like the same-origin policy and CORS.
When you need it
Anyone working with the web reaches for a URL breakdown constantly: debugging a redirect that lands on the wrong path, reading a tracking link stuffed with UTM parameters, confirming an API endpoint hits the right host and port, or checking that a query string survived encoding. Splitting the URL into labeled parts turns a wall of text into something you can read at a glance.
Frequently asked questions
Is my URL sent anywhere?
No, it is parsed in your browser with the native URL constructor and never uploaded.
Why does a bare domain fail?
The parser needs an absolute URL. Add a protocol, so example.com becomes https://example.com.
Does it decode the query parameters?
Yes, each key and value in the table is shown decoded, so %20 reads as a space.
Why is the port blank?
A blank port means the protocol's default is used, 443 for HTTPS and 80 for HTTP.
Is it free?
Yes, completely free with no sign-up and no limits.
Related: URL Encode / Decode · UTM Link Builder