Break any URL into protocol, host, port, path, query, and fragment, with the query string decoded into readable key/value pairs — all client-side.
Updated
Quick start
Paste a URL, read its parts and parameters — nothing leaves your browser.
Drop a full absolute URL, including the https:// scheme, into the input.
See protocol, host, port, path, query, and fragment, plus decoded parameters.
Copy any single part with its Copy button to reuse elsewhere.
In-depth guide
A URL packs a surprising amount of structure into one string: scheme, credentials, host, port, path, query, and fragment. This tool uses the browser's standard URL parser to split any absolute URL into those components and to decode the query string into readable key/value pairs — useful for debugging links, tracking parameters, and redirect chains.
Take https://user:pass@host:8443/path?q=1#top. The parser identifies the protocol (https:), optional username/password, the hostname and port, the path, the query (everything after ?), and the fragment (after #). It also reports the origin — scheme + host + port — which is the security boundary browsers use.
https://) into the input box./path?a=1 alone is not a valid absolute URL.%20 or +.xn-- form, which is what is actually sent — that is correct, not a bug.The URL is parsed by the browser's built-in engine inside the page. Nothing is sent to a server, logged, or stored, so you can safely inspect links that carry session tokens, signed parameters, or credentials. The tool works offline after loading and forgets everything when the tab closes.
No. Parsing uses the browser's native URL API in the page — nothing is requested or logged. You can dissect URLs containing tokens or session IDs safely; confirm in DevTools → Network that no calls fire.
Protocol, username, password, hostname, port, path, query string, fragment (hash), and the computed origin. It also decodes the query string into individual key/value pairs so you can read each parameter without manual percent-decoding.
The parser needs an absolute URL with a scheme. "example.com/path" is rejected because it has no protocol; add https:// to make it valid. This matches how the WHATWG URL standard and real browsers behave.
Yes. Percent-encoding and + (space) in the query string are decoded, so q=hello+world shows as "hello world". The component view, by contrast, shows the raw encoded query string so you can see exactly what was transmitted.
Yes — userinfo like https://user:pass@host is split into separate username and password fields. Embedding credentials in URLs is discouraged for security, but the parser surfaces them so you can audit links that contain them.
The URL API normalises internationalised hostnames to their Punycode (xn--) form, which is what is actually sent on the wire. That lets you see the ASCII-compatible encoding a browser would use for a Unicode domain.
Keep exploring
Hand-picked utilities that pair well with the one you're on — all free, client-side, and zero-signup.
Convert Unix epoch ↔ ISO 8601 / human dates with timezone support.
Decode cron expressions into plain English, preview upcoming run times, and verify 5/6/7-field crontab schedules before deployment.
Parse a UA string into browser, OS and device details.
Shrink PDF file size without uploading to a server.
Body Mass Index with metric / imperial inputs and WHO category bands.
Combine multiple PDFs into one in your browser.
Split a PDF by pages or page ranges, download as zip.