AZ Tools

URL Parser

Developer

Paste any URL and see every part labeled — protocol, origin, hostname, port, pathname, search string, and fragment. Embedded credentials (user:pass@) show separately. Query parameters are decoded and listed as key/value rows so you can spot duplicates and check encoding. Uses the browser's WHATWG URL parser, the same one Fetch and XHR use, so what you see is what your code will see.

Protocol

https:

Origin

https://example.com:8080

Hostname

example.com

Port

8080

Pathname

/path/to/page

Search

?q=hello&lang=en

Hash

#section

Username

user

Password

pass

Query parameters

KeyValue
qhello
langen

Parsing uses the browser's native URL API.

How to use

  1. Paste a URL (must include a scheme, e.g. https://).
  2. Read off the parts and copy any piece individually.
  3. Scan the query-params table to verify each value.

Frequently asked questions

Why does my input fail?
URLs need a scheme. `example.com/path` is not parseable; `https://example.com/path` is. Relative paths and protocol-relative URLs (`//example.com`) won't parse either.
Why is `port` empty for https://example.com?
When the port is the protocol default (80 for http, 443 for https), `URL.port` is intentionally empty. The browser would still connect to 443.
Are query params decoded?
Yes. `%20` shows as space, `%2F` as `/`. Copy a key or value to get the decoded form. If you need percent-encoded text, look at `search` instead.
Does this send the URL anywhere?
No. Parsing happens entirely in your browser via the WHATWG URL API.

Related tools