URL Parser
The URL parser breaks a URL into its structural components — protocol, username, password, hostname, port, path, query string, and fragment — and displays each in a table.
URL Input
Usage
• Break out protocol, auth, host, port, path, query parameters, and fragment
• Tabular query params: add / edit / remove any param, supports repeated keys and auto encode/decode
• Edits are written back live to produce a normalized URL
Related tools
What the URL parser is for
The URL parser breaks a URL into its structural components — protocol, username, password, hostname, port, path, query string, and fragment — and displays each in a table. It also presents query parameters as an editable key-value table, and rebuilds the URL live as you modify, add, or remove parameters.
Common uses include inspecting long or encoded URLs from logs or API documentation, editing query parameters without manual string manipulation, understanding the structure of an unfamiliar URL, and constructing or validating URLs for use in API integrations or redirect rules.
Frequently asked questions
Does the parser handle encoded URLs?
Yes. Percent-encoded characters in query parameter values are decoded for display in the table. The rebuilt URL re-encodes them correctly when you export it.
What happens with repeated query parameters?
Repeated keys (e.g. ?tag=a&tag=b) are shown as separate rows in the parameter table. You can add or remove individual values.
Is authentication info in the URL safe to use?
URLs that contain usernames and passwords (e.g. https://user:pass@example.com) should be avoided in production — credentials in URLs can appear in server logs, browser history, and referrer headers. The parser displays them for inspection but flag this as a potential security concern.
Can I use this to build API request URLs?
Yes. Paste a base URL, use the parameter table to add or edit query parameters, and copy the rebuilt URL. This is faster and less error-prone than manually concatenating strings.
References and result limitations
Local results depend on the input and selected options. Retain the input example, format and processing rules when citing a result, and verify the output. Keep keys and other sensitive material out of public examples.
These references explain protocol or format rules; they do not endorse results produced by this site.