Standards-based decoding
The default mode follows application/x-www-form-urlencoded behavior: split on &, percent-decode UTF-8, and treat + as a space.
Pairs—
Unique keys—
Duplicate rows—
Bytes—
Source—
Round-trip—
Parameter stream
Every row stays in original order. Raw fields show the query text before percent-decoding.
| # | Raw key | Raw value | Decoded key | Decoded value | Review |
|---|
Review flags
Canonical form query
Flat JSON view
Bracket-notation projection
Interpretation is opt-in and blocks prototype-pollution-shaped keys.
Parameters
Serialized output
Query A
Query B
| Line | Pairs | Unique | Duplicates | Warnings | Canonical |
|---|
Duplicates stay duplicates
tag=a&tag=b is not collapsed. Order and repeated keys remain visible, because both can be meaningful to servers.
Bracket notation is not a web standard
Keys such as user[name] are common framework conventions. The structured view is therefore separate from the standards-based pair stream and blocks dangerous object-path names.
Raw versus decoded
%2B, + and spaces are easy to confuse. Side-by-side raw/decoded fields make those distinctions explicit.
Privacy flags
Token-, secret- and password-like parameter names are flagged heuristically. Tracking parameters are also surfaced. The audit is a review aid, not a security guarantee.
Local only
No URL is visited and no query is uploaded. All parsing, serialization, comparison and exports happen in your browser.