URL Parser
Break down a URL into its individual components such as protocol, host, path, parameters, and hash.
URL Parser
Results
| Protocol | https: |
|---|---|
| Host | example.com:8080 |
| Hostname | example.com |
| Port | 8080 |
| Path | /path/to/page |
| Query string | ?query=123 |
| Fragment | #section |
| Username | user |
| Password | pass |
Query parameters
| query | 123 |
|---|
How to break a URL into its parts
Paste any URL to see its protocol, host, path, query parameters, and fragment listed separately.
What each part means
- Protocol — the scheme, such as https:.
- Host — hostname plus port, if one is set.
- Path — everything after the host, before the query string.
- Query string — the part after ?, also broken down parameter by parameter.
- Fragment — the part after #, used for in-page anchors.
URLs without a protocol
A browser's URL parser requires a scheme to work at all. If you paste something like "example.com/path" with no https:// or http://, this tool assumes https:// so it still parses — a note appears when that happens.
How to use it
- Paste or type a URL into the input box.
- Every component updates immediately below.
- Any query parameters appear in their own table.
Privacy
Runs locally in your browser. No data is sent to the server.
FAQ
Why does it add https:// automatically?
Because the underlying URL parser can't interpret a URL with no scheme at all. Assuming https:// (today's overwhelming default) lets a bare domain still be inspected, with a note shown so it's clear a guess was made.
Does it decode percent-encoded characters?
The path and query values are shown as the browser's URL parser exposes them, which already decodes standard percent-encoding in most fields.
Is the URL I paste sent anywhere?
No. Parsing happens locally using the browser's own URL API; nothing is sent to a server.