Skip to content
BEAD

URL Parser

Break a URL into protocol, host, path, query parameters, and fragment.

Protocol
https
Username
user
Password
pass
Host
www.example.com:8080
Hostname
www.example.com
Port
8080
Origin
https://www.example.com:8080
Pathname
/path/to/page
Search
?id=42&q=hello%20world&tags=a&tags=b
Hash
#section
Query parameters (4)
id42
qhello world
tagsa
tagsb

Frequently asked

What does the parser actually return?

Everything you'd get from the WHATWG URL standard: protocol, host, port, pathname, search, hash, plus a flattened params object with array values for repeated keys. The output is JSON, so it pipes cleanly into JSON Formatter or any downstream workflow.

Does it decode percent-encoded values?

Query parameter values are URI-decoded for the params object, so %20 becomes a space, %3D becomes =, and so on. The raw search string preserves the encoded form so you can copy it back if needed.

What about non-HTTP URLs?

Any URL the WHATWG parser accepts works — including mailto:, ftp:, sftp:, ssh:, custom schemes, and data: URIs. Note that scheme-less URLs (no protocol) won't parse.

You might also like

Used in these workflows