URL Parse
Break a URL into its parts — protocol, host, port, path segments, query parameters, fragment. Handles relative URLs and preserves duplicate query keys.
About URL Parse
URL Parse breaks a URL into its component parts: protocol, host, port, path segments, query parameters, and fragment. It handles relative URLs and preserves duplicate query keys instead of collapsing them, which matters when a key legitimately appears more than once. Reach for it when debugging a redirect, auditing tracking parameters, or understanding a messy link. Parsing happens in your browser.
- Category
- inspect
- Input
- Accepts: */*.
- Output
- Outputs: application/json.
- Cost
- Free, runs in your browser
- Memory
- low
Common uses
- Pull apart a long marketing URL to see every UTM and tracking parameter
- Debug a redirect by inspecting the exact host, path, and query it points to
- Check whether a query string carries a duplicate key that a naive parser would drop
- Decode and read a fragment or path segment buried in a complex link
- Verify the protocol and port of an endpoint before wiring it into a config
- Audit a callback URL for unexpected parameters during an OAuth flow
Frequently asked questions
Does it keep duplicate query parameters?
Yes. If a key appears multiple times in the query string, all values are preserved rather than collapsed to one, which matters for arrays and repeated flags.
Can it parse relative URLs?
Yes, it handles relative URLs as well as absolute ones, returning whatever components are present.
What does the output look like?
A JSON object with the protocol, host, port, path segments, query parameters, and fragment broken out separately.
Is the URL sent anywhere?
No. Parsing is done entirely in your browser; the URL stays on your device.
Does it decode percent-encoded values?
It surfaces the query parameters so you can read them. For round-trip percent encoding or decoding of a full string, use the URL Encoder tool.
Keywords
- url
- parse
- query
- host
- path
- protocol
- fragment
- split