🔑 URL Query String Builder
Build encoded URL query strings from simple key value pairs. Runs in your browser.
Last updated: November 8, 2026 · By the BoltQuickTools team
Turn a list of parameters into a query string
Hand-writing a test URL with several parameters means remembering to encode spaces, ampersands and accented letters. Here you list the pairs in plain text, one per line, and the encoded string is built for you.
Building the string
Type pairs into Key Value Pairs, one key=value per line. The Query String field updates as you type, and Build Query does the same on demand. Copy Query copies the result, Load Sample fills in test data, and Clear empties both fields. The counter below shows how many parameters were built.
Example with repeats, a bare flag and a nested URL
tag=a
tag=b
flag
redirect=https://x.io/a?b=1&c=2
produces, with a count of 4 parameters:
?tag=a&tag=b&flag=&redirect=https%3A%2F%2Fx.io%2Fa%3Fb%3D1%26c%3D2
Repeated keys are kept in order, a line with no equals sign becomes a key with an empty value, and only the first = on a line splits it. Non-ASCII text is encoded as UTF-8: café=crème & thé gives ?caf%C3%A9=cr%C3%A8me+%26+th%C3%A9.
Input it handles differently from what you might expect
- Do not paste encoded values. Everything gets encoded, including percent signs, so
name=a%20bbecomes?name=a%2520b. Enter the plain text instead. - One pair per line is required. Pasting an existing string such as
?a=1&b=2treats it as one parameter and produces?%3Fa=1%26b%3D2. - Spaces around the equals sign are kept. Only the ends of the line are trimmed, so
sp = acedbecomes?sp+=+aced, with a key that ends in a space. - Spaces are written as +. That is correct for query strings, but a
+used in a URL path would not mean a space. - There are no comment lines.
#c=1becomes the parameter?%23c=1, and blank lines are skipped. - It only builds the part after the question mark. Add the base URL yourself.
Reading, repeating and testing query strings
Can I go the other way and read an existing query string?
Not on this page. The Parse URL tab of the URL encoder splits a full URL into its parameters.
How should repeated keys be read by a server?
That depends on the framework. Some take the first value, some the last, and some return a list, so test yours. This page simply writes each line in the order you entered it.
How can I test the finished URL?
Add your base URL and send it from the API tester. The article on API testing without Postman covers other lightweight ways to send it.