Developer

URL Parser

Paste a URL to see each part separately — scheme, host, port, path, query parameters and fragment — with values already decoded.

Developer

URL parser

Local only

URL

Part	Value
Protocol	`https:`
Hostname	`www.tooltouse.com`
Port	`(default)`
Path	`/tools`
Query string	`?q=pdf%20compress&sort=popular`
Hash	`#results`
Origin	`https://www.tooltouse.com`
Username	`—`

Query parameters

Key	Decoded value
`q`	pdf compress
`sort`	popular

As JSON

{
  "protocol": "https:",
  "hostname": "www.tooltouse.com",
  "port": "",
  "pathname": "/tools",
  "hash": "#results",
  "params": {
    "q": "pdf compress",
    "sort": "popular"
  }
}

Parsed on your device

The browser's built-in URL parser is used — the address is never requested or sent anywhere.

Anatomy of a URL

A URL combines a scheme (https:), an authority (host and optional port), a path, an optional query string and an optional fragment. Each part has its own escaping rules, which is why manual string splitting so often goes wrong.

Why values look different

Query values are shown decoded, so pdf%20compress appears as pdf compress. Use the URL Encoder tool if you need the encoded form back.

Good to know

Frequently asked questions

Why do I need to include https://?

A URL without a scheme is relative, so the parser cannot tell the host from the path. Add the scheme and it parses correctly.

Is the URL requested?

No. Nothing is fetched — the address is only parsed as text in your browser.

Are repeated query keys supported?

Repeated keys are listed individually in the parameter table; the JSON view keeps the last value for each key.

Does it decode the values?

Yes. Percent-encoded characters and plus signs in query values are decoded for readability.

URL parser

Query parameters

Anatomy of a URL

Why values look different

Frequently asked questions

Related tools

UUID Generator

JSON Formatter & Validator

Base64 Encoder & Decoder