URL Parser & Inspector

Decompose any URL into protocol, host, path, query params, and hash — with per-field copy.

Client-side

About this tool

The URL Parser breaks any URL into its constituent parts using the browser's built-in URL API: protocol, hostname, port, pathname, query string, and hash fragment. Each component is shown in a table with an individual copy button, and query parameters are expanded into a separate key-value breakdown.

Understanding URL structure is essential for web development, API debugging, and security analysis. Query string parameters are often percent-encoded; this tool decodes them automatically so you can read the actual values. The hash (anchor fragment) is shown separately from the query string.

The tool prepends https:// automatically if you omit the scheme, so you can paste domain-only strings. Everything runs in the browser using the W3C URL standard (new URL()) — no server involved.

FAQ

What is the difference between the path and the query string?

The path is the part after the domain before the question mark (e.g. /articles/123). The query string is everything after the ? (e.g. ?page=2&sort=asc). The hash (#section) is the fragment, processed only by the browser and never sent to the server.

Are query parameter values decoded?

Yes. Percent-encoded query values (like %20 for a space) are decoded to human-readable form in the Query Parameters table. The raw query string is shown as-is.

Can I parse URLs without http/https?

The tool prepends https:// if no scheme is present, so domain-only inputs like "example.com/path" are handled. URLs with custom schemes (ftp://, ssh://, etc.) are parsed as-is.

What happens with malformed URLs?

The browser's URL API returns a parsing error, which is displayed inline. Common issues: missing domain, invalid characters, or unbalanced brackets in IPv6 addresses.