URL Parser
Split any URL into protocol, host, path, params and hash
Anatomy of a URL
A URL packs five jobs into one string: the scheme says which protocol to speak, the host (plus optional port) says where, the path says what, the query string carries parameters, and the fragment points inside the page. Misreading any one part is how broken links, open redirects and mangled tracking parameters happen.
What this tool does
- 📎 Splits any URL into protocol, host, port, path, query and hash
- 🧩 Decodes every query parameter into a readable table
- 🔒 Masks embedded passwords instead of displaying them
- ⚡ Parses live as you type, missing scheme assumed https
When to use it
- Debugging why a shared link behaves differently
- Reading UTM and tracking parameters off a URL
- Checking a redirect chain target before following it
Privacy: parsing uses the browser's own URL engine locally — links you paste never leave your device.
Last updated · 2026-09-01
How parsing works
The platform URL parser (the same engine behind new URL()) splits the input per the WHATWG URL standard; searchParams yields the decoded parameter table. No regex guesswork, no network, nothing uploaded.
Why parse here?
Every component, decoded
Protocol through fragment in one table, with percent-encoded query values decoded to readable text instead of %20 soup.
Passwords masked by default
Userinfo credentials render as dots, because the whole point of pasting a URL here is inspecting it safely before sharing it onward.
Forgiving input, strict output
Bare domains gain their https automatically, while non-web schemes are refused outright instead of being sliced into nonsense rows.
Frequently asked questions
What if I paste a URL without https://?⌄
It still works: a missing scheme is assumed to be https, the way browsers treat bare domains you type into the address bar.
Are passwords in URLs shown?⌄
Never in the clear — userinfo passwords render masked, because URLs with embedded credentials get pasted into chats and tickets far too often.
Which URLs are rejected?⌄
Anything that isn't http, https or ftp, and strings no URL parser can make sense of. Non-web schemes (mailto:, javascript:) are refused rather than mis-parsed.
Frequently asked questions
What if I paste a URL without https://?
It still works: a missing scheme is assumed to be https, the way browsers treat bare domains you type into the address bar.
Are passwords in URLs shown?
Never in the clear — userinfo passwords render masked, because URLs with embedded credentials get pasted into chats and tickets far too often.
Which URLs are rejected?
Anything that isn't http, https or ftp, and strings no URL parser can make sense of. Non-web schemes (mailto:, javascript:) are refused rather than mis-parsed.