URL Parser
Split any URL into protocol, host, port, path, query parameters, and fragment. Spot encoding issues instantly.
Processed locally in your browser — nothing is uploaded.
URL Parser
0 characters
About URL Parser
See every component of a URL at a glance: protocol, username, host, port, path segments, decoded query parameters, and fragment. Useful when a URL is long, heavily encoded, or behaving unexpectedly.
Common uses
- Debug redirect chains and callback URLs
- Verify which host and port a request actually targets
- Decode percent-encoded paths and parameters
Example
Input
https://user@api.example.com:8443/v1/search?q=caf%C3%A9#results
Output
protocol: https · host: api.example.com · port: 8443 · path: /v1/search · q: café · fragment: results
Frequently asked questions
Does this URL parser send the URL to a backend?
No. The URL is parsed locally in your browser using the standard URL API and is never transmitted or stored, so callback URLs carrying session tokens or personal data stay private.
What's the difference between the host and the origin of a URL?
The host is just the domain name (like api.example.com), while the origin is the scheme, host, and port together (https://api.example.com:8443). Browsers use the full origin for security decisions like CORS and cookie isolation.
Why does the parser show a port when my URL doesn't have one?
When no port is written, the scheme's default applies — 443 for https, 80 for http — and the tool shows it labeled "(default)" so you can see which port a request would actually target.
Can I parse a URL that doesn't start with http:// or https://?
Yes. If you paste something like example.com/path, the tool assumes https:// and shows a notice that it did, so the components still break down correctly.
Is the fragment part of a URL sent to the server?
No. Everything after # stays in the browser — servers never receive it. That's why fragments are used for in-page anchors, client-side routing, and OAuth implicit-flow tokens.