| Protocol | https |
| Username | user |
| Password | pass |
| Host | tools.seagit.com:8443 |
| Hostname | tools.seagit.com |
| Port | 8443 |
| Path | /path/to/page |
| Query string | ?q=hello&lang=en&q=world |
| Hash | #section |
| Origin | https://tools.seagit.com:8443 |
| Key | Value |
|---|---|
| q | hello |
| lang | en |
| q | world |
Parsed with the browser's native URL API — nothing is uploaded.
Break any URL into its parts, free. A URL has a defined structure (protocol, host, port, path, query, and fragment) standardized by the WHATWG URL Standard and RFC 3986. This parser splits any URL into those components and lists each query parameter as a key/value pair — entirely in your browser, using the same URL API browsers use.
It decomposes a URL into protocol, host, port, path, query and hash, and expands the query string into individual parameters you can read at a glance. 100% free, no registration, and complete privacy — everything runs locally in your browser, so your data never touches a server.
See protocol, hostname, port, pathname, search and hash split out clearly from any URL.
Each ?key=value pair is listed separately and URL-decoded, so you can inspect tracking and API params.
Parsing uses the browser's URL API locally; nothing you paste is uploaded or stored.
Unlimited parsing with no account, on desktop and mobile.
It splits the URL into protocol (scheme), hostname, port, pathname, search (query string), and hash (fragment), and lists each query parameter as a decoded key/value pair.
Yes. Percent-encoded values (like %20 or %3D) are decoded so you can read the real parameter values, including UTM and tracking tags.
No. Parsing uses the browser's built-in URL API and happens entirely on your device; the URL is never sent to a server.
The URL API needs a valid absolute URL with a scheme (e.g. https://). A bare 'example.com/path' without a protocol may not parse — add https:// and try again.
Yes. URLs can repeat a key (?id=1&id=2); the parser lists each occurrence so you don't lose any values.