URL Parser is a tool that breaks a URL into its components: protocol, domain (hostname), port, path, query string, query parameters, and fragment (hash). Ideal for debugging and analyzing complex URLs.
Query parameters are the portion of a URL after the question mark (?). They follow a key=value format and are separated by &. For example: ?utm_source=google&utm_medium=cpc contains two parameters: utm_source and utm_medium.
The fragment is the portion of a URL after the hash sign (#). Browsers use it to scroll to a specific section on the page (anchor), or in SPAs (Single Page Applications) for client-side routing.
No. Parsing is performed entirely in the browser using the native JavaScript `new URL()` API. The URL you enter never leaves your device.
This tool supports URLs with http and https schemes, including non-standard ports, nested paths, multiple query parameters, and fragments. URLs without a protocol will be rejected.
If the port is not shown, it means the URL uses the default port — 80 for http and 443 for https. Browsers automatically omit default ports from the URL representation.
Hostname contains only the domain name (example.com), while origin includes the protocol + hostname + port, such as https://example.com:8080. Origin is useful for CORS configuration.
Browsers automatically percent-encode special characters in URLs. This tool displays the decoded values for easier readability.
Yes. OAuth callback URLs typically contain many query parameters such as code, state, and scope. This tool separates them one by one in the query params table.
Yes. URL Parser is completely free, no account required, no disruptive ads, and available to use at any time.