Does it matter if I paste a full URL or just the query part?

No. The parser looks for a ? and reads everything after it (up to any # fragment), so pasting https://example.com/page?a=1&b=2 or just a=1&b=2 both work the same way.

Does parsing decode percent-encoded and + characters?

Yes. It uses the browser's URLSearchParams, so %20 and + both decode to spaces, and other percent-encoded bytes are converted back to their original characters automatically.

What happens with repeated keys, like tag=a&tag=b?

Both are kept. The parsed table shows one row per key/value pair, so a repeated key like tag appears twice with its two values — nothing is collapsed or overwritten.

How does the builder handle special characters in values?

Values are percent-encoded automatically as you type, using the same encoding the browser uses for URLSearchParams — so spaces, ampersands, and other reserved characters come out safe to drop straight into a URL.

Is anything I paste sent to a server?

No. Both parsing and building run locally with the browser's built-in URLSearchParams API — nothing you type or paste leaves your machine.

QUERY STRING TOOL

Parse a URL's query parameters into a table, or build a query string from key/value rows. All in your browser.

URL or query string

Parameters (3)

Key	Value
q	hello world
page	2
sort	relevance

How to use the query string tool

1
Switch between Parse a URL and Build a query string with the tab at the top.
2
To parse, paste a full URL or a raw ?key=value string and read off the decoded parameters.
3
To build, add key/value rows and the query string updates live.
4
Copy the parsed table's values or the built query string with the Copy button.

Questions

Does it matter if I paste a full URL or just the query part?: No. The parser looks for a ? and reads everything after it (up to any # fragment), so pasting https://example.com/page?a=1&b=2 or just a=1&b=2 both work the same way.
Does parsing decode percent-encoded and + characters?: Yes. It uses the browser's URLSearchParams, so %20 and + both decode to spaces, and other percent-encoded bytes are converted back to their original characters automatically.
What happens with repeated keys, like tag=a&tag=b?: Both are kept. The parsed table shows one row per key/value pair, so a repeated key like tag appears twice with its two values — nothing is collapsed or overwritten.
How does the builder handle special characters in values?: Values are percent-encoded automatically as you type, using the same encoding the browser uses for URLSearchParams — so spaces, ampersands, and other reserved characters come out safe to drop straight into a URL.
Is anything I paste sent to a server?: No. Both parsing and building run locally with the browser's built-in URLSearchParams API — nothing you type or paste leaves your machine.