Parsing a query string
Paste a full URL, a query string starting with ?, or a bare key=value&key2=value2 string. Each pair is percent-decoded, a + in a value is treated as a space (standard application/x-www-form-urlencoded behavior), and keys that repeat — like a multi-select filter sending tags=a&tags=b — are grouped into a single row with all their values, matching how most web frameworks parse them into an array.
FAQ
Why does a key with no value show as empty?
A bare key like flag with no =, or a key with an = but nothing after it like page=, both parse to an empty string value — that distinction (present-but-empty vs. absent) is exactly what a server would see too.
What happens with a malformed % sequence?
Only the affected value is left undecoded and flagged; every other parameter still decodes normally.
Can I get the parsed result as JSON?
Yes — the JSON panel mirrors what Object.fromEntries over the parameters would produce, except keys with multiple values become an array instead of the last value silently overwriting the earlier ones.