URL Query String Parser

Paste a full URL or just the part after the question mark. The tool takes everything after the first ?, or the whole input if there is no ?, decodes it with the browser's standard URLSearchParams, and prints the result as JSON. The sample URL https://example.com/search?q=running+shoes&size=42&color=red&color=blue&page=2 gives:

Three things happen along the way. A + becomes a space. Percent codes are decoded, so %E2%82%AC becomes € and c%26d becomes c&d. A key that appears more than once turns into an array, in the order it appeared.

Every value in the output is a string. size=42 is "42", not the number 42, and active=true is the text "true". That's how query strings actually arrive at a server, so it's what your code has to deal with. If a handler compares page === 2, it will fail on real requests until it converts the value.

A key with no value comes out as an empty string. ?debug&verbose=&x=1 gives "debug": "" and "verbose": "", so a check for whether a flag is present has to test for the key, not for a truthy value.

The tool doesn't strip the part after #. Paste https://example.com/p?id=7&ref=mail#reviews and the result shows "ref": "mail#reviews". Browsers never send the fragment to the server, so delete it before parsing if you want to see what the server receives.

Also check what you pasted when the output looks odd. A URL with no ? at all, such as https://example.com/path, is treated as a query string, so you get a single key containing the whole address and an empty value.

Parsing follows the plain web standard, not any framework's extensions:

• Brackets are part of the key. ids[]=1&ids[]=2 gives a key called ids[] holding ["1", "2"], and user[name]=Ada stays as the key user[name]. PHP and some Node libraries build nested objects from these; this tool doesn't.
• Only & separates parameters. a=1;b=2 is one parameter whose value is 1;b=2.
• A stray percent sign is kept. f=100% comes through as "100%" rather than causing an error.