URL Parser
| Protocol | |
| Host | |
| Port | |
| Path | |
| Query string | |
| Fragment |
Query parameters (decoded)
| Parameter | Value |
|---|
No query parameters in this URL.
About this tool
URLs look simple until you have to debug one. A tracking link with seventeen query parameters, a redirect chain that keeps dropping the fragment, an API call failing because a port snuck into the host — this tool splits any URL into its components so you can see exactly what is going on: protocol, hostname, port, path, query string, and fragment, each on its own row. Query parameters are additionally decoded and laid out in a table, which makes spotting a double-encoded value or a misspelled parameter name far easier than squinting at one long string.
A couple of practical notes. If you paste an address without a scheme (like example.com/path), the parser assumes https:// and tells you so. Percent-encoded characters in parameter values are decoded for display — if you need to go the other direction and encode a URL, the URL Encoder tool on this site does that. Fragments (the part after #) are never sent to servers, which is why they survive redirects differently from query strings; seeing the fragment isolated here often explains ‘lost anchor’ mysteries. Everything is parsed locally in your browser.
Privacy: all processing happens in your browser. Nothing you paste is uploaded or stored.