Query String Builder
Build a URL query string from key/value rows with correct percent-encoding, array syntax options and a UTM preset — or parse an existing URL back into rows.
Related tools
All Data & computing tools →Query String Builder is free to use as often as you like, directly from this page. It sits under Data & computing in our catalogue, alongside JSON to query string and Query string to JSON.
How to use it
- Open the tool — no signup or install needed.
- Enter your input or adjust the available options.
- Get your result instantly, then copy or download it.
Frequently asked questions
What is Query String Builder?
Build a URL query string from key/value rows with correct percent-encoding, array syntax options and a UTM preset — or parse an existing URL back into rows.
When would I actually use this?
Finding out how big a thing will be before you make it: how many gigabytes an hour of footage takes, how long a file needs on the connection you have, how large a photo prints before it goes soft, what bitrate fits the budget you were given.
What is the most common mistake?
Taking the advertised connection speed as the transfer speed. A 100 Mb/s line is megabits, the file is in megabytes, and the eight-fold difference between them is where most download estimates go wrong — before overhead and contention take their own share.
How is Query String Builder different from JSON to query string?
They sit next to each other but answer different questions: JSON to query string is the one to open when you need it to turn a flat JSON object into a URL query string. Pick whichever matches what you're starting from — both are free.
Is there a tool for the next step?
Query string to JSON is the closest one after this: Parse a URL query string into JSON and build one back. Repeated keys become an array, tag[]= and filtre[prix]= expand into arrays and objects, + is a space and %C3%A9 is é.
What else is worth having open alongside it?
JSON String Escape / Unescape and ASCII Table Reference — they come up in the same task often enough to be worth a second tab.
Where do the figures come from?
Byte prefixes follow the IEC convention where a kibibyte is 1 024 bytes and a kilobyte is 1 000 — drive makers use the second, operating systems often report the first, and a disk that shrinks on arrival is that gap and nothing else. Print sizing assumes 300 dpi unless you change it.