URL Parser — Split URLs and Edit Query Params
DeveloperA URL parser is a developer tool that splits an address into protocol, host, port, path, query, and fragment per the WHATWG URL Standard, and lets you edit query parameters and reassemble the URL.
What is it
A URL follows the structure scheme://host:port/path?query#fragment, where the query string is a list of key=value pairs joined by &. This tool parses the address with the browser's built-in URL API, shows each component in a table, and rebuilds a new URL — with percent-encoding applied automatically — as you add, change, or remove parameters. It is handy for cleaning UTM parameters out of long marketing links or debugging API request URLs. The URL is processed only in your browser.
How to use
- 1Paste the URL to analyze (https:// is added automatically if missing).
- 2Press parse to see the component table and the query parameter list.
- 3Edit, add, or remove parameters, then copy the rebuilt URL.
Reference
| Component | Example (https://example.com:8443/search?q=hello&page=2#results) |
|---|---|
| protocol | https: |
| hostname | example.com |
| port | 8443 |
| pathname | /search |
| query | q=hello&page=2 |
| fragment | #results |
Sources & standards
- URL Living Standard - WHATWG
- MDN Web Docs: Client-side web APIs - MDN Web Docs
FAQ
How are spaces and non-ASCII parameter values handled?
Percent-encoding is applied automatically per the URL Standard (e.g. a space becomes %20). The editing table shows decoded values, while the rebuilt URL contains the encoded form.
Can I parse an address without a protocol?
Yes — https:// is prepended automatically for inputs like example.com/path. Purely relative paths (just /path) cannot be parsed because there is no base URL.
Is the URL I paste sent anywhere?
No. Parsing and rebuilding use the browser URL API, so even URLs containing tokens never leave your device.