Why parse URL query parameters
Reporting UIs, admin consoles, and API debugging often produce very long URLs, for example:
https://localhost:44301/Web/Reporting/Report.aspx?NoSelect=1&ToolsSelect=21d611b2-...%2Cbb6c33f3-...&FacilityId=7fe11ef1-...&ExportType=pdf
Reading each parameter by eye is hard. Editing a GUID list or export flags is easy to break—missing &, forgetting decode, or treating %2C as plain text.
ComTools URL Params (Tools/Developer/UrlParams) turns the query string into a key / value table, entirely in the browser.
Supported input
| Type | Example |
|---|---|
| Full URL | https://example.com/page?a=1&b=2 |
| No scheme | example.com/page?a=1 |
| Query only | ?a=1&b=2 or a=1&b=2 |
After paste you can see Path / base chips. Enable auto-parse to refresh the table as you type.
Features
1. Table + decode
One row per parameter; values are URL-decoded (e.g. %2C → ,). Optionally show the raw encoded column.
2. Multi-value line breaks
If a value has more than two comma-separated items, the cell shows them on separate lines; copy / rebuild merges them back to commas.
3. Edit, filter, add, delete
- Edit keys and values; filter by key or value
- Add a row or delete with ×
- Modified rows are highlighted
4. Copy helpers
| Action | Result |
|---|---|
| ⧉ Copy value | Normalized comma-separated value |
| IN | SQL IN (N'guid1', N'guid2') (or numbers / bools) |
| Copy JSON | All params as a JSON object |
| Copy TSV | Paste into Excel |
| Copy / Open URL | Rebuild the link from the table |
Steps
- Copy a URL from the address bar or logs.
- Open URL Params and paste (or Sample).
- Inspect, filter, or edit the table.
- Use IN for database checks; Copy URL / Open URL to test.
vs encode / decode tools
| Tool | Use when |
|---|---|
| URL Params | Understand / edit / rebuild the whole query |
| URL Encode | Percent-encode one string |
| URL Decode | Decode one string |
Privacy
Parsing and copying stay local—useful for intranet or tokenized links (still avoid public machines).
Related
FAQ
Only a=1&b=2 with no ??
Yes—treated as a bare query string.
Duplicate keys in JSON?
Same keys become an array.
Is the hash (#...) in the table?
Usually not; rebuild tries to keep the hash on full URLs.