URL Parser

中

Loading...

URL Parser — Break Down Protocol, Host, Path, Query and Hash

Paste any URL and see every component separated and labeled: protocol, host, port, path, query parameters (one per row), and hash fragment. The parser follows the WHATWG URL standard — the same one browsers use.

Use it to debug redirect URLs, inspect OAuth callback parameters, untangle tracking query strings, or figure out why two URLs that look identical behave differently. Parsing is local, so URLs containing tokens stay on your device.

How to parse a URL

  1. Paste the URL into the input.
  2. Read the component breakdown: protocol, host, port, path.
  3. Expand the query parameters into a table of name/value pairs.
  4. Check the hash/fragment section separately.

Frequently asked questions

What is the difference between the query and the fragment?

The query (?a=b) is sent to the server with the request; the fragment (#section) is processed client-side only and never leaves the browser. That is why OAuth flows put tokens in fragments — and also why they cannot be logged server-side.

Why does the same URL behave differently on different sites?

Case-sensitivity (paths are case-sensitive, hostnames are not), trailing slashes, default ports, and encoding subtleties all matter. Comparing two parsed URLs side by side exposes the difference faster than eyeballing.

Is my URL sent to a server when parsing?

No. Parsing happens locally with the browser's built-in URL engine. URLs often contain tokens or session identifiers — here they stay on your device.

Related tools

URL Encoder/Decoder
Encode/decode URLs, parse query params, convert Query ↔ JSON
HTTP Status Codes
Look up HTTP status code meanings with search and category filtering
JWT Decoder
Decode and inspect JSON Web Tokens, view Header, Payload and expiration

PureKit · url-parser · Free online tool — files processed locally in your browser, no upload.