We use essential storage to make the site work. If you accept, we also use Google Analytics to understand usage and Google AdSense to show ads, which may set cookies. You can change your choice any time with Cookie settings in the footer. Privacy Policy
URL Parser
Parse any URL into protocol, host, port, path, query parameters, and hash. Decode encoded query strings instantly. 100% private. 100% free and private.
How to use
Paste a URL — Drop in any absolute URL with query string and hash.
See the Parts — Protocol, hostname, port, path, and origin appear in a grid.
Read Query Params — Each key/value pair is decoded and listed cleanly.
Copy What You Need — Tap any field to copy and reuse in code or docs.
Frequently asked questions
Is decoding handled automatically?
Yes. We use the browser's native URL API which decodes percent-encoded values like %20 to space.
Does it support data: or blob: URLs?
Partially. The protocol and pathname will appear, but query parsing is only meaningful for http(s) URLs.
What about international domain names (IDN)?
The browser converts them to punycode in hostname. The visible URL bar still shows the Unicode form.
Why is port shown as 'default'?
When the URL omits a port, the browser uses 443 for https and 80 for http. We show '(default)' to indicate it wasn't explicit.
Does it handle IDN (international) domains?
Yes — Unicode domains are shown in both Unicode and Punycode form.
What about query strings with duplicate keys?
Both occurrences are listed; servers vary in which one wins.
Are URL fragments sent to the server?
No — fragments stay client-side only.
Does the tool follow redirects?
No. Use the URL Redirect Checker for that.
Is my URL stored?
No. Parsing happens in your browser.
Free URL Parser
Decode any URL into protocol, origin, hostname, port, pathname, hash, and individual query parameters. Built on the browser's native URL API so the results match what your code will see.
Common Uses
Debug tracking links and UTM parameters
Inspect deep links shared in apps
Validate redirect URLs in OAuth flows
Extract API endpoints from documentation
Teach how URLs are structured
How It Works
We pass your input into the browser's native URL constructor, which performs RFC 3986 parsing and decoding. Each query parameter is read through URLSearchParams so repeated keys and encoded values are handled correctly.
Privacy
Parsing is entirely client-side. Your URLs are not logged or transmitted.