URL Parser
Parse and inspect every component of a URL.
Paste a URL and get every component broken out — scheme, host, port, path, each query parameter listed separately, fragment — with percent-encoding decoded so you can see what each piece actually contains.
Common use cases: debugging OAuth redirect URLs, inspecting tracking links to see exactly what UTM parameters are attached, validating that a URL produced by your code has the structure you expect, and decoding the obscure-looking strings in analytics URLs.
Frequently asked questions
What components does a URL have?
Scheme (
https), host (example.com), port (443), path (/api/users), query string (?id=42), and fragment (#section). The parser splits each component out and decodes percent-encoded values so you can see exactly what each piece contains.How does it handle query strings with repeated keys?
Repeated keys are common (
?tag=foo&tag=bar) and the parser preserves all values, listing them in order. This matches how the WHATWG URL spec and most web frameworks treat them.What's the difference between origin, host and authority?
Origin = scheme + host + port (used for browser security checks). Host = hostname + optional port. Authority = optional user info + host (rarely useful in modern URLs since userinfo in URLs is deprecated).
Why does the parser sometimes flag an URL as invalid?
Usually because of unescaped reserved characters in the path or query, an unknown or malformed scheme, or invalid characters in the hostname. The error message points to the specific problem so you can fix it before passing the URL to code that might behave unpredictably.