Skip to content
tecuy
Developer & Data

URL Parser & Query Inspector

Break a URL into protocol, host, path, query, and fragment, with every query parameter listed individually — duplicates preserved, never merged.

Scope

This tool only parses http:///https:// web page URLs, using your browser's built-in URL parser — never a hand-rolled one — so behavior exactly matches how a real browser or server would interpret the same URL, including IPv6 hosts and internationalized domain names.

Parsed entirely in your browser — nothing you enter here is sent to a server.

Break a URL into its protocol, hostname, port, path, query string, and fragment, with every query parameter listed individually — duplicate keys are shown as separate entries, never merged into one. Edit, add, or remove parameters and see the URL rebuilt live.

Built entirely on your browser's native URL parser (never a hand-rolled one), so it correctly handles IPv6 addresses and internationalized domain names the same way a real browser would.

How to use the URL Parser & Query Inspector

  1. Paste a complete URL, including http:// or https://, into the input box.
  2. Read the Components list: Protocol, Hostname, Port, Pathname, Query string and Fragment, each with its own Copy button.
  3. Edit any key or value under Query parameters, click the x to remove one, or click Add parameter to append a new one.
  4. Copy the updated address from Rebuilt URL.

Example: Dropping one of two duplicate parameters

Paste https://shop.example.com:8443/search?q=red%20shoes&tag=sale&tag=new#results. Components show Port 8443, Pathname /search and Fragment #results, and Query parameters (3) lists q = red shoes, tag = sale and tag = new. Removing the last row changes Rebuilt URL to https://shop.example.com:8443/search?q=red+shoes&tag=sale#results.

Questions about the URL Parser & Query Inspector

Why did %20 turn into a plus sign in the rebuilt URL?
Parameter values are shown decoded, then re-encoded with the browser's standard form encoding, which writes spaces as +. Servers decode both %20 and + in a query string as a space, but the text will differ from your original.
Why does the Port show (default)?
The URL either has no port or uses the scheme's default (443 for https, 80 for http), which the browser's parser drops. For example HTTPS://Example.COM:443/a/../b is normalized to https://example.com/b, and a note says the URL was normalized.
What happens to a username and password in the URL?
A warning says the URL contains embedded credentials, and they are left out of the Components list and the Rebuilt URL, so the rebuilt link will not carry them.
Why is my URL rejected?
It must parse as a complete address with a scheme, so example.com alone fails with "Enter a valid, complete URL, including http:// or https://." Other schemes such as ftp: or mailto: are refused because the tool only handles web page URLs.