URL Parser & Query String Inspector — Free
Runs 100% in your browser — your files never leave your device.
Long URLs hide important details in credentials, ports, repeated query parameters, and fragments. Paste a complete URL to inspect every component using the browser’s native URL parser, including query keys that occur more than once.
How it works
- 1
Paste a complete URL
- 2
Inspect every component
- 3
Review parsed query parameters
About this tool
What gets broken out
Paste any complete URL and the tool displays every component the browser's native URL parser sees: protocol, credentials if present, host, port, path segments, each query key and value — including repeated keys — and the fragment. The parse is standards-based, the same result your browser runtime produces.
Debugging with the components
Wrong redirects, lost parameters, and surprise ports all hide inside URL strings. Seeing the parsed components answers immediately: where does the path really end, which parameter repeats, is there a credential embedded, what does the fragment actually contain.
A security note on credentials
URLs of the form https://user:password@host embed credentials visibly — they leak into logs, referrer headers, and shared links. The parser surfaces them so you can spot and remove them; if you find one, rotate the credential.
Frequently asked questions
Why do repeated query parameters matter?
Frameworks disagree on handling ?a=1&a=2 — some take the first, some the last, some build arrays. The parser shows every occurrence so you know exactly what the URL carries.
Does the fragment reach the server?
No — everything after # stays in the browser and never appears in server logs or requests. That is why single-page apps use fragments for routing history.
Is the parse the same in every browser?
The URL standard is implemented consistently across modern browsers — the parse you see here matches what server-side and client-side runtimes produce for the same input.