URL Parts Parser

Separate absolute or relative URLs into serialized components while preserving duplicate query parameters and credential boundaries.

URL or Relative Reference

Browser URL parsing can normalize the serialized result. The source is not fetched or contacted.

Parsing Options

Output

Query & Path Segment Values

Resolve relative referencesUse the base URL below for paths such as ../users?page=1 or //cdn.example.com/a.js.Hide URL userinfo credentialsRemove username and password from copied full-URL and JSON output. Query-string secrets are not automatically removed.

Base URL for Relative References

Must itself be an absolute URL. Relative resolution follows browser URL rules, including dot-segment removal.

Parsed Output

Parsed URL output will appear here.

URL parsing stays in your browser. No DNS lookup, HTTP request, redirect follow, or server validation is performed.

Browser URL parsing is more than splitting on punctuation

A browser URL parser resolves relative references, normalizes special-scheme URLs, handles IPv6 brackets, separates userinfo from the host, removes dot segments during resolution, and serializes the result back into a canonical form. Reading those components through the platform URL API avoids many mistakes that come from a single regular expression.

Relative references only make sense with a base

A reference such as ../users?id=7 does not identify one absolute URL on its own. The selected base supplies the scheme, authority, and path context needed for resolution. Network-path references beginning with // inherit the base scheme but provide their own authority.

Serialized and decoded values answer different questions

The serialized pathname remains percent-encoded so the displayed component does not invent new separators. Individual path segments can be decoded separately. Query decoding follows URLSearchParams form rules, where percent escapes are decoded and + represents a space. Serialized query mode keeps the browser-serialized pair text instead.

Duplicate query names are not collapsed. Each occurrence stays visible because APIs often assign meaning to repeated fields and their order.

Fragments, credentials, and secret-looking query data

A #fragment is a separate URI component used by the client; it is not part of the HTTP request target sent to an origin server. Username/password userinfo is shown separately and can be removed from copied full-URL output. That setting does not claim to find every secret hidden in query parameters, so token-like query names are surfaced as a caution instead of silently rewritten.

Standards behind the component model

Browser parsing and serialization follow the WHATWG URL Standard. The broader scheme, authority, path, query, fragment, and relative-reference model is described in RFC 3986.