URL Parser

A URL has a scheme/protocol (like https), optional username and password, a host (hostname plus optional port), a path, an optional query string after ? holding key-value parameters, and an optional fragment after #. In https://www.example.com:8080/path?q=1#top: https is the protocol, www.example.com the hostname, 8080 the port, /path the path, q=1 the query and top the fragment. Only the scheme and host are required — the path, port, query string and fragment can all be left out.

The query string is the part after ?, carrying name=value pairs joined by &, such as ?page=2&sort=name. This tool splits and URL-decodes them, so hello%20world shows as "hello world", and lists every parameter — including repeated keys, which some apps use for multi-value fields. Reserved characters in values are decoded so you can read them as they were intended.

The hostname is just the domain (www.example.com); the host is the hostname plus the port if present (www.example.com:8080). When no port is written, the browser assumes the scheme default — 443 for https, 80 for http — so the port field may look empty. The origin combines scheme, hostname and port and is used for same-origin security checks.

No — the URL is parsed entirely in your browser with the built-in URL API — nothing is uploaded, logged or stored, and no request is made to the address, so it's safe for URLs containing tokens or private parameters. There is no sign-up, and it works offline once loaded. Reloading the page resets the field to the built-in example URL, since nothing you type is saved to a cookie, localStorage, or any server between visits.