How to parse a URL query string
Ad links and search result URLs trail a long string after the question mark that nobody can read at a glance. Paste the whole address here and the tool takes only the part after the question mark, splits it into keys and values in a table, and builds ready-to-use JSON alongside. It is handy for checking tracking parameters or reviewing an API request.
Repeated keys are handled properly. Tags and filters often repeat the same key, so the table lists every occurrence in order while the JSON groups that key into an array. The result also names which keys repeated. An item with a name but no equals sign is given a null value.
Percent encoding in values is decoded by default, and plus signs are read as spaces the way form submissions encode them. If a value contains a real plus sign, turn that option off. Broken percent encoding does not throw an error; the value is kept exactly as written and the result says how many were affected. Anything after a # is dropped, because a fragment is never sent to the server, and that is reported too.
Frequently asked questions
Yes. If there is a question mark, only what follows it is parsed; otherwise the whole input is treated as a query string. Anything after a # is cut off automatically.
No. Every occurrence is listed in the table in order, and in the JSON that key becomes an array holding all of its values, so nothing is discarded.