URL Parser
WebParse a URL into protocol, host, path, query, hash components with query parsing. Break links apart for redirects, analytics and quick debugging.
httpsexample.com8080/path/to/page#sectionuser••••••••https://example.com:8080q=hellolang=entag=devAbout URL Parser
A full URL is made of scheme, user info, host, port, path, query string, and fragment (hash). Picking long links apart by eye easily misses parameters. Built on the browser's native URL API, this tool parses a pasted address into its components locally and breaks the query string into a key-value table, automatically percent-decoding values so you can verify tracking parameters, callback URLs, or auth tokens. The whole parse runs in the browser, and the link content is never uploaded to any server. Tip: Bookmark this tool for quick access during your web development work. All processing happens locally in your browser with no installation required.
How to Use
- Open the URL Parser tool page
- Enter or paste your data into the input area
- View the real-time results and use the copy button to get the output
Use Cases
- Verify callbacks — Break down an OAuth redirect_uri to confirm code and state are passed correctly.
- Strip tracking — See utm_source, gclid, and other marketing params to decide what to keep or remove.
- Debug redirects — Analyze each hop's query string to find where a parameter is lost or mis-encoded.
- Parse deep links — Open app deep links or custom schemes to inspect path and parameter structure.
- Encoding checks — Detect doubly percent-encoded values that break server-side parsing.
- Debug webhook payloads — Parse the URL from a webhook POST to verify the path and query params match the expected endpoint signature.
- Inspect hash routing — Break down a SPA hash URL (#/path?param=value) to debug client-side routing behavior.
FAQ
Is the hash sent to the server?
No. The fragment identifier is client-only; browsers do not send the # and everything after it with requests. It is commonly used for frontend routing and in-page anchors.
Does + mean space in a query?
In application/x-www-form-urlencoded context, + means a space, but in a path or standard percent-encoding, + is a literal plus. The tool decodes per spec, so mind the source context.
What about repeated parameter names?
URLs allow duplicate keys like ?tag=a&tag=b. The tool lists them all; how the server reads them depends on its framework (first, last, or array).
Why do some chars show as %E4%B8%AD?
That is percent-encoded UTF-8, common for non-ASCII like Chinese. The tool tries to decode it to readable text, leaving it as-is if the encoding is invalid.
Can it build a URL in reverse?
This tool focuses on parsing. To assemble or encode query parameters into a new URL, pair it with our URL encoding tools for the reverse operation.
Any browser compatibility requirements?
This tool works in all modern browsers (Chrome, Firefox, Edge, Safari). No plugins or extensions required.
Can I use it offline?
After initial load, most features work offline. The core logic runs entirely in your browser with no network dependency.
Comments
Comments are stored locally in your browser. Configure Giscus for cloud-based comments.