Break a URL into its pieces
You’re staring at https://user:[email protected]:8080/v2/users?role=admin&active=true&page=3#section1 and trying to mentally parse where the hostname ends, what port it’s using, and which query parameters are present. That’s what this tool does in one click.
Paste a URL, hit parse, and every component shows up in a clean table: protocol, username, password, hostname, port, pathname, query string, hash, and origin. Query parameters get their own separate table with each key-value pair on its own row, including duplicate keys, which are valid in URLs.
The parsing uses the browser’s native URL API, which follows the WHATWG URL standard. If the browser can parse it, this tool can show you what’s inside it.
The components, explained
Take https://user:[email protected]:8080/v2/users?role=admin&active=true#section1:
Protocol: https:. The scheme.
Username/Password: user / pass. Optional auth credentials (rarely used directly in URLs anymore).
Hostname: api.example.com. The server.
Port: 8080. Defaults to 80 (HTTP) or 443 (HTTPS) when omitted.
Pathname: /v2/users. The resource path.
Search: ?role=admin&active=true. The query string.
Hash: #section1. The fragment identifier (never sent to the server).
Origin: https://api.example.com:8080. Protocol + hostname + port.
Debugging scenarios
API endpoint verification. You’re building a URL programmatically and need to confirm the base URL, path, and query parameters are all correct before making the request.
Tracking link inspection. Marketing URLs have 15 query parameters, UTM codes, referrer IDs, redirect chains. Parsing them into a table makes each one visible.
OAuth flow debugging. Callback URLs carry authorization codes, scopes, state tokens, and encoded redirect URIs. Parsing shows each piece separately.
Log analysis. Extract components from access log URLs to understand traffic patterns.
For encoding and decoding URL components, the URL Encoder and URL Decoder are also available.
FAQ
Does it need a protocol?
Yes, https:// or http:// is required for the URL API to parse correctly.
Duplicate query parameters?
Each occurrence gets its own row in the parameter table. Completely valid in URLs.
Encoded characters?
The URL API decodes percent-encoded characters in the parsed output, so you see actual values.
Auth credentials in the URL?
Extracted and displayed separately if present. https://user:[email protected] shows username = user, password = pass.
Client-side?
Yes, your URLs never leave your browser. Uses the native URL API.