URL Parser – Split URLs & Query Parameters Online

Parse a URL into its components

A complete URL can contain much more than a hostname. This parser separates the scheme, origin, username, password, hostname, explicit port, pathname, path segments, raw query string, individual query parameters and fragment. It also returns the normalized URL produced by the browser. Use that breakdown when debugging redirect targets, API requests, analytics links, callback URLs or canonical tags.

The parser runs entirely in the current browser tab. It reads the URL as text and does not navigate to it, resolve its hostname or contact the destination server. That makes it useful for ordinary development and QA work, but pasted URLs can still contain personal data, signed tokens or credentials that should not be copied into tickets or shared output.

Query parameters and repeated keys

Everything after the first question mark and before a fragment is the query string. Parameters normally use name=value pairs separated by ampersands. This tool returns them as an ordered array instead of a plain object, so repeated keys such as tag=tools&tag=seo are preserved rather than overwritten. Names and values are decoded according to the browser URL implementation, while the raw query remains available for exact comparison.

Repeated keys are valid and frequently used for filters, multi-select forms and tracking data. Empty values also remain visible. Parameter order can matter to signatures and cache keys even when an application treats it as irrelevant, so compare the normalized URL and raw query before editing a signed request.

Protocol, origin, host and port

The protocol is the scheme before the colon, normally https or http. The origin combines the scheme, hostname and non-default port. The hostname excludes a port, while the port field contains only an explicitly retained non-default port; browsers normalize default HTTP port 80 and HTTPS port 443 away. The pathname begins with a slash and the fragment is the part after #, which browsers normally do not send in an HTTP request.

Encoded paths versus URL components

A URL may contain percent-encoded bytes such as %20 for a space. The parser keeps the normalized encoded pathname and also lists decoded path segments when they can be decoded safely. To encode or decode one value before inserting it into a URL, use the URL Encoder & Decoder. To inspect JSON stored inside a decoded parameter, use the JSON Formatter.

Standards and security boundaries

Parsing uses the native browser URL and URLSearchParams APIs, which implement the living WHATWG URL Standard. This page accepts absolute HTTP and HTTPS URLs only. A successfully parsed URL is not necessarily safe: lookalike hostnames, embedded credentials, malicious destinations and sensitive tokens can all be syntactically valid.

Frequently asked questions