How to Parse a URL Into Its Components
Paste an Absolute URL
Drop a full URL that includes a scheme, such as https://example.com/path?id=42#top, into the input field. Parsing happens on your device using the browser native URL constructor, so the value you type stays on your device. Relative paths without a scheme will not parse because the URL API needs a base.
Read the Component Cards
The tool instantly fills nine cards: Full URL, Origin, Protocol, Host, Hostname, Port, Pathname, Search and Hash. Empty parts, such as a missing port or hash, are shown as (empty) so you can tell a blank field from a parsing gap at a glance.
Inspect the Query Parameters
If the URL has a query string, a Query Parameters table lists every key and its decoded value. Percent-encoded characters are unescaped for you, and a key that repeats appears once per occurrence so duplicate parameters stay visible.
What Each URL Component Means
The parser exposes the same properties the browser URL API returns. Knowing what each one holds makes it easier to debug links, redirects and API calls. The table below maps every card to its meaning using the example https://api.example.com:8443/v1/users?role=admin#list.
| Component | Holds | Example Value |
|---|---|---|
| Origin | Scheme, host and port together | https://api.example.com:8443 |
| Protocol | The scheme with a trailing colon | https: |
| Host | Hostname plus port when present | api.example.com:8443 |
| Hostname | Domain only, without the port | api.example.com |
| Pathname | The path after the host | /v1/users |
| Search and Hash | Query string and fragment | ?role=admin and #list |
When This Parser Helps
Debugging Query Strings
When a link carries a long list of tracking or filter parameters, the key-value table separates each one so you can confirm the exact values being sent without counting ampersands by hand.
Checking Encoding
Because values are decoded with the URLSearchParams API, you can paste a percent-encoded URL and immediately read what a parameter such as %20 or %2F actually resolves to.
Verifying Origin and Port
For API and CORS work, the Origin, Hostname and Port cards let you confirm whether a request targets the host and port you expect, including non-default ports like 8443.
Quick Offline Lookups
Since parsing runs in your browser with no upload, you can inspect internal, staging or localhost URLs that you would not want to send to a remote service.
Common Problems and Fixes
It says the URL is invalid
The parser uses the strict browser URL constructor, which rejects anything missing a scheme. Add a prefix such as https:// to the front of the value and try again.
My relative path will not parse
Relative URLs like /path?id=1 need a base URL for context, which this tool does not supply. Prepend a full origin, for example https://example.com/path?id=1, to parse it.
The query table is missing
The Query Parameters table only appears when the URL contains a query string after a question mark. A URL with no parameters shows the component cards only.
A value looks different than I typed
Query values are shown decoded, so percent-encoded characters are converted back to plain text and a plus sign in the query may render as a space. Compare against the raw Search card if you need the encoded form.