URL Parser & Query String Viewer
Paste a URL to split it into protocol, host, port, path, query string and fragment, plus a decoded table of every query parameter. Everything runs locally in your browser.
About this tool
The URL Parser breaks any URL into its parts — protocol, host, port, path, query string and fragment — and expands the query into a decoded table of every parameter. It is the fastest way to understand a long, messy link full of tracking parameters or encoded values without squinting at it character by character.
Because it runs entirely in your browser, URLs containing session tokens, API keys or personal identifiers are never sent anywhere. It is ideal for debugging redirects, inspecting OAuth callback links and checking how query parameters are actually encoded.
How to use
- Paste the full URL into the input field.
- The parser immediately splits it into protocol, host, port, path and fragment.
- Scroll the query parameter table to see each key and its decoded value.
- Spot percent-encoded characters that have been turned back into readable text.
- Copy any individual part or the whole breakdown for your notes or bug report.
Features
- Splits a URL into protocol, host, port, path, query and fragment.
- Decoded table listing every query parameter as key and value pairs.
- Automatically decodes percent-encoded characters into readable text.
- Handles duplicate parameter keys without dropping any of them.
- Works with relative fragments, ports and unusual schemes.
- Fully local — URLs with tokens or personal data never leave the browser.
Frequently asked questions
Are the URLs I paste logged or sent to a server?
No. Parsing runs in your browser, so a URL containing tokens, keys or personal data stays entirely on your device.
How does it handle repeated query parameters?
Each occurrence of a parameter is listed separately, so URLs that pass the same key multiple times keep every value visible.
What does decoding a query parameter mean?
Query values are often percent-encoded, so a space becomes %20 and a slash becomes %2F. The tool converts these back to their original characters so the values are readable.
Can it parse a URL without a protocol?
A well-formed URL needs a scheme like https:// to be split reliably. If the protocol is missing, add it first so the host and path are detected correctly.
What is the fragment part of a URL?
The fragment is the section after the # symbol. It is used by the browser to jump to an anchor or by single-page apps for client-side routing and is never sent to the server.