URL parser — break any link into its parts.
Paste a URL to see its protocol, host, port, path, every query parameter, and fragment laid out clearly — useful for debugging links, APIs, and redirects.
Parse a URL
LiveTurn any long URL into a short, trackable link.
Once you know what's inside a link, shorten it — with click analytics by source, location, and device, all in one dashboard.
What is a URL made of?
Every link is built from a small, fixed set of parts — in the same order, every time.
A URL isn't one opaque string — it's a structured address. The protocol says how to reach it, the host says which server, the path says which resource on that server, the query string carries extra parameters, and the fragment points to a spot within the page.
Parsing a URL means splitting it back into those named parts instead of reading it as a single blob of text. That's exactly what your browser does internally before it opens a page — this tool just shows you the result.
It's especially useful for reading query strings with many parameters, spotting a typo in a redirect URL, or checking exactly what a shortened or tracking link actually points to.
?color=blue&size=M#reviews
Every part of a URL, explained.
| Part | Example | What it means |
|---|---|---|
| Protocol | https: | The rules used to connect — almost always https today. |
| Host | shop.example.com | The domain or server being reached. |
| Port | :8443 | Optional. Which door on the server to use — omitted when it's the default (80 or 443). |
| Path | /products/mug | Which resource on that server, similar to a folder path. |
| Query string | ?color=blue&size=M | Key-value parameters, separated by &, that customize the request. |
| Fragment | #reviews | A pointer to a specific spot within the page — never sent to the server. |
Where this comes in handy.
Debugging redirects
Check exactly what a redirect or tracking link points to, and which parameters it's carrying, before you click it.
Reading API endpoints
Quickly separate the base endpoint from query parameters when reading logs, docs, or webhook payloads.
Auditing tracking links
See every UTM or affiliate parameter attached to a link, laid out as a clean key-value list.
Spotting duplicate keys
Some query strings repeat the same key, like multiple size= filters — the parser lists each occurrence separately.
Checking non-standard ports
Confirm whether a link points to a specific port, like a staging server or local dev environment.
Teaching URL structure
A quick, visual way to show how a link is put together, part by part.
Common questions
Does the fragment get sent to the server? +
No. Everything after the # stays in the browser and is used to scroll to or reveal content on the page — the server never sees it in the request.
Why does a query parameter appear more than once? +
URLs allow the same key to repeat, commonly used for multi-select filters like tag=red&tag=blue. The parser lists each occurrence in order rather than silently dropping duplicates.
What happens if I paste a URL without a protocol? +
Include https:// or http:// at the start — without it, the text can't be reliably split into host and path, since something like "example.com/page" is technically ambiguous.
Is this the same as decoding a URL? +
Related, but different — parsing splits a URL into its structural parts, while decoding converts %-encoded characters back into readable text. Use the URL encoder/decoder for the latter.
Does this tool store or send the URLs I paste? +
No. Parsing happens entirely in your browser using standard URL parsing — nothing is transmitted or logged.