ToolSphere

URL Parser & Query Splitter

More tools

Paste a URL to split it into protocol, host, port, path and hash, with every query string parameter decoded in a table. Free URL parser in your browser.

URL parser & query splitter

On this browser only

Give feedback

Did this tool help?

Tell us what worked, what didn’t, or what you’d like next.

Opens Google Forms in a new tab with this tool’s name filled in. No sign-in or email required. Feedback is optional.

About URL Parser & Query Splitter

The Anatomy of a URL

A URL breaks down into distinct, well-defined components, each serving a different purpose: the protocol (https://) specifies how to connect; the host identifies which server to reach; the path identifies a specific resource on that server; the query string (?key=value&...) carries additional parameters as key-value pairs; and the fragment (#section) identifies a location within the page itself, notably never sent to the server at all — it's purely client-side, used for in-page anchors or client-side routing state.

Query parameters deserve special attention because they're easy to misparse by hand: multiple values for the same key are valid (?tag=a&tag=b), values need percent-decoding to recover their original characters (see Complete Guide to URL Encoding), and parameter order is technically unspecified — a server can treat ?a=1&b=2 and ?b=2&a=1 identically, though not all implementations do.

Breaking a URL into these labeled components — rather than trying to visually parse a long query string by eye — is exactly how you catch a missing parameter, a wrong host, or an unexpectedly present fragment while debugging a redirect or API request URL.

Guides and tutorials

Frequently asked questions

Does the fragment (#section) ever get sent to the server?

No — the fragment identifier is purely client-side, used for in-page anchors or client-side routing; the browser strips it before the request ever reaches the server, unlike every other part of the URL.

Can a query string have multiple values for the same parameter name?

Yes — `?tag=a&tag=b` is valid and common, though how it's actually parsed (as an array vs. only the last value winning) depends entirely on the specific server or framework handling the request, not the URL spec itself.

Is query parameter order guaranteed to matter?

Not by the URL specification itself — a well-behaved server should treat differently-ordered but otherwise identical query strings the same way, though not every real-world implementation actually honors this.

Have a suggestion for URL Parser & Query Splitter?Share your feedback ↗