URL Parser
Break a URL into its parts and list query parameters.
Your URLs are parsed locally in your browser and nothing is uploaded, so links containing credentials or tokens never leave your device.
Need to encode or decode a URL string? Try the URL Encoder.
About URL Parser
The URL parser breaks any URL into its individual parts so you can inspect exactly what a link contains. Paste a full address and it splits out the origin, protocol, hostname, port, path, hash, and any username or password, then lists every query parameter as a clear key/value pair. It is built for developers, QA engineers, and API testers who need to debug redirects, verify tracking parameters, or read a complex query string at a glance. Because it uses your browser's native URL engine, parsing matches what your code will actually see at runtime. Use it as a quick url inspector, a url query string parser, or to extract query parameters from long campaign links. Everything runs locally in your browser, so the URLs you paste never leave your device.
Features
- Splits a URL into origin, protocol, hostname, port, path, and hash
- Surfaces embedded username and password credentials when present
- Lists every query parameter as a readable key and value pair
- Counts query parameters so you can spot duplicates or missing keys
- Decodes percent-encoded values using the browser's native URL engine
- Validates input and flags malformed URLs or a missing scheme
- Parses instantly as you type, with no submit step
How to use the URL Parser
- Paste or type a full URL into the URL box, including its scheme like https://.
- Read the parsed origin, protocol, hostname, port, path, and hash rows.
- Scroll to the query parameters section to inspect each key and value.
- Edit the URL in place to test variations and watch the breakdown update live.
Example
Input
https://example.com:8443/path/to/page?q=search&lang=en#section
Output
Origin: https://example.com:8443
Protocol: https:
Hostname: example.com
Port: 8443
Path: /path/to/page
Hash: #section
Query parameters · 2
q = search
lang = en
A URL split into its parts with query parameters listed.
Common errors & troubleshooting
- Pasting a URL without a scheme like example.com/path returns an invalid URL error. — Add a scheme such as https:// so the parser can read it, e.g. https://example.com/path.
- Query parameters look garbled or contain %20 and other codes. — The values are percent-encoded in the source URL; the parser decodes them automatically, so read the decoded value shown in each row.
- A repeated parameter only seems to appear once at a glance. — Check the parameter count in the section header, which lists every occurrence including duplicate keys.
- The port row is missing for an https URL. — Default ports like 443 for https and 80 for http are omitted by the URL engine; only non-default ports are shown.
Frequently asked questions
- What is the URL Parser and what does it show?
- The URL Parser breaks a URL into origin, protocol, hostname, port, path, hash, and any embedded username or password, plus a full list of query parameters as key/value pairs.
- How do I fix an invalid URL error in the URL Parser?
- Include a complete scheme such as https:// or another protocol, for example https://example.com/path?q=1, and the URL Parser will read the link and clear the error.
- Does the URL Parser decode percent-encoded query values?
- Yes. Query parameter values are decoded using the browser's native URL engine, so you see the human-readable value rather than %20 escapes.
- Can the URL Parser handle multiple values for the same key?
- Yes. Each occurrence is listed separately and the header shows the total parameter count, so duplicate keys are easy to spot.
- Are the URLs I paste into the URL Parser kept private?
- Yes. The URL Parser processes everything locally in your browser and nothing is uploaded to a server, so even URLs with credentials stay on your device.
Related tools
All ArrayKit tools