MMaxTools

URL Parser

Break any URL into protocol, host, path, query parameters and hash.

The URL Parser takes any full URL apart and shows every component clearly: protocol, host, port, path, query string, hash, origin — and each individual query parameter with its value. Every part is copyable, which makes the tool perfect for debugging links, inspecting webhook URLs, or learning how URLs are structured.

URLs hide surprising structure: a fragment after # never reaches the server, the query string starts after the first ?, port 443 is the default for https, and identical-looking parameters can repeat. Seeing the breakdown removes the guesswork when something is not routing, not authenticating or not being tracked the way you expect.

Parsing uses the standard URL API and happens locally in your browser — paste internal URLs and tokens without worry. The parser accepts only absolute URLs, so include the scheme (https://…).

Protocolhttps:
Hostmaxtools.app
Hostnamemaxtools.app
Port(default)
Path/dev-tools/json-formatter
Query string?tab=format&limit=10
Hash / fragment#usage
Originhttps://maxtools.app

Query parameters (2)

tab= format
limit= 10

How to use the URL Parser

  1. Paste a full URL including https:// or http://.
  2. Read each component in the breakdown table.
  3. Scan the query parameters list with their decoded values.
  4. Copy any part — a parameter value, the origin, or the path.
  5. Edit the URL and watch the parse update live.

Frequently asked questions

What is the difference between host and hostname?

The host includes the port (example.com:8080); the hostname is just the domain (example.com). This parser shows both, plus the port separately, so redirects and proxy debugging are unambiguous.

What are query parameters used for?

They carry data in the URL — ?utm_source=google&page=2. Marketers use UTM parameters to track campaigns, developers use them for pagination and filters, and every form with GET submits its values this way. The parser lists each key-value pair decoded.

Why does my URL need a scheme?

An absolute URL requires a scheme (https, http, ftp…) to be unambiguous — the parser needs to know the string is a URL and not just a path. If you only have a path like /api/v1/users, you are looking at a relative reference, not a complete URL.