URL Parser

Parsed https://example.com:8443 into 2 query parameter(s).

How it works

• Applied the WHATWG URL parser to the absolute URL.
• Read the scheme, user information, host, port, path, query and fragment.
• Percent-decoded the path, parameter values/names and fragment.
• Listed 2 query parameter(s) in order.

• Internationalized hostnames are normalized by the platform parser (IDNA/punycode).

Methodology

1. Apply the WHATWG URL parser to the input; a value without a scheme or host fails the standard's absolute-URL requirement.
2. Read the serialized components from the parsed URL object: protocol, username, password-presence, hostname, port, pathname, search and hash.
3. When decoding is enabled, percent-decode the path, each parameter name and value, and the fragment with a replacement-safe decoder.
4. List query parameters in document order using the URLSearchParams iterator (decoded) or a raw split on '&' and the first '=' (undecoded).

Usage

1. Paste an absolute URL (including http:// or https://).
2. Choose whether to percent-decode the path, parameters and fragment.
3. Read each component and the ordered query parameter list.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Decode a URL with a query and fragment

{
  "value": "https://user@example.com:8443/a%20b/c?q=hello%20world&lang=en#section%201",
  "decode": true
}

Keep the raw encoding

{
  "value": "https://example.com/path%2Fwith%20chars?x=1",
  "decode": false
}

Simple URL

{
  "value": "https://example.com/",
  "decode": true
}

Limitations

Absolute URLs only

A URL is absolute when it has a scheme and a host. Relative references such as /a/b or ../c depend on the document they appear in, so this tool refuses them rather than inventing a base. The WHATWG parser also normalizes the host (lower-casing and IDNA) and resolves dot segments in the path, which is why the parsed form can differ from the input spelling.

Decoding versus raw form

The raw form is what would be transmitted; the decoded form is what a receiver interprets. Both are useful: use the raw form to inspect encoding and signatures, and the decoded form to read parameter values. Decoding never changes the reported raw query string.