URL Parser
Break any URL into protocol, host, port, path, query parameters and hash.
Break a URL into its parts
The URL Parser takes any URL and splits it into its components — protocol, host, port, path, query string, and hash — and lists every query parameter separately. Paste a URL and see its structure instantly. It uses the browser's built-in URL parser, so the breakdown is accurate and standards-compliant.
Anatomy of a URL
A URL is made of distinct parts, each with a job. Understanding them helps with debugging links, building query strings, configuring redirects, and reading analytics. For example, in https://shop.example.com:8080/products?id=42#reviews, the protocol is https:, the host is shop.example.com:8080, the path is /products, the query is ?id=42, and the hash is #reviews.
The components explained
| Part | Example |
|---|---|
| Protocol | https: |
| Hostname | shop.example.com |
| Port | 8080 |
| Path | /products |
| Query | ?id=42 |
| Hash | #reviews |
How to use it
- Paste a full URL (include the protocol, e.g. https://).
- Read the breakdown of each component.
- Review the individual query parameters in the list below.
Why parse URLs?
- Debugging — see exactly what parameters a link carries (great for UTM tags).
- Development — confirm your generated URLs are structured correctly.
- Analytics — read campaign and tracking parameters at a glance.
- Security review — inspect suspicious links before clicking.
Query parameters made clear
The query string after the ? holds key-value pairs separated by &. The parser decodes and lists each one, so a long, messy query becomes an easy-to-scan table. This is especially handy for inspecting UTM campaign tags, API parameters, and redirect targets.
Private and free
Parsing happens entirely in your browser — nothing is uploaded or stored. The tool is completely free with no sign-up.
Frequently asked questions
Do I need to include the protocol?
Yes. Include http:// or https:// so the URL can be parsed correctly.
Does it list query parameters?
Yes. Each key-value pair in the query string is decoded and listed separately.
What can I use it for?
Debugging links, inspecting UTM tags, verifying generated URLs, and reviewing suspicious links safely.
Is my data private?
Yes. Parsing runs entirely in your browser and nothing is uploaded.