About URL Parser

Parses any URL into its parts, entirely in your browser, using the same WHATWG URL engine browsers use — so the result matches how a browser actually interprets the URL. It breaks out the protocol, username/password (if present), hostname, port, path, hash fragment, and origin, and lists every query parameter in a table with values URL-decoded (so %20 shows as a space). Repeated keys are kept as separate rows. A bare domain like example.com/path is assumed to be https. Useful for debugging redirects, API calls, tracking links, and OAuth flows.

• Uses the native WHATWG URL parser — matches real browser behaviour, no custom regex
• Extracts protocol, auth (user/pass), hostname, port, path, hash, and origin
• Query parameters listed in a table with values URL-decoded
• Repeated keys (tag=a&tag=b) are preserved as separate rows
• Bare domains are assumed https; truly invalid URLs show a clear error
• Runs fully client-side — the URL never leaves the browser

Frequently Asked Questions

Are query parameter values decoded?

Yes — values are URL-decoded for readability, so q=hello%20world is shown as “hello world”. Repeated keys are kept as separate rows rather than collapsed, matching how servers usually read them.

What if I paste a URL without http(s)://?

A bare domain like example.com/path?x=1 is treated as https://example.com/path?x=1. If the input can’t be interpreted as a URL at all, you get a clear “Invalid URL” message instead of a wrong parse.

How is this different from a URL encoder/decoder?

An encoder/decoder transforms a string to or from percent-encoding. This tool dissects a whole URL into its structural parts and parameters — what you need when debugging an API call, redirect, or tracking link.