URL Parser & Query Builder
Inspect an address without visiting it. Edit query entries individually, preserve repeated keys and rebuild the URL using the browser's URL model.
Browser-based · No account required · Copy and export
Your workspace
Developer toolsQuery parameters
How to use URL Parser & Query Builder
- Paste an absolute HTTP(S) URL and parse it.
- Edit protocol, host, path, fragment and query entries. Optionally remove the documented tracking parameters.
- Rebuild, review and copy the address. Download a JSON report to retain ordered parameter pairs.
When to use this tool
Inspect a URL and edit its query parameters without losing duplicate keys. Review the reconstructed destination before opening it; removing tracking keys can change application behavior.
Repeated parameter names can be meaningful
A query is an ordered sequence of name/value pairs rather than a simple object. Repeated keys are kept in the report. Sorting uses URLSearchParams ordering and can normalize encoding. The explicit tracking action removes utm_* keys, gclid, dclid, fbclid and msclkid; it preserves unrelated parameters.
Worked example
Input: https://example.test/?tag=a&tag=b&utm_source=mail#top
After removing tracking: ?tag=a&tag=b#top
Report entries: [["tag","a"],["tag","b"]]Limits and output checks
No navigation, URL reputation check or request is made. URL parsing can normalize case, default ports, paths and escaping. Removing tracking keys can change a destination's behavior; review the result. Addresses and reports can contain sensitive query values.
Reference: URLSearchParams entries.
Frequently asked questions
Are duplicate query keys retained?
Yes. Entries are edited and exported as ordered pairs.
Does parsing contact the destination?
No. The URL constructor parses text locally.
Does removing tracking clear all parameters?
No. Only the documented tracking names are removed, and the action is explicit.