Updated · Built and checked by the PlinzoTools team, formulas tested against published sources
Build a URL query string from a list of key-value parameters.
Your query string will appear here.
The reverse of the URL Query String Parser -- builds a properly URL-encoded query string from a list of key-value pairs you enter, handling special characters, spaces, and symbols correctly.
Enter each parameter as key=value, one per line. The generated, properly-encoded query string appears instantly.
Instead of a single text box, the tool gives you paired Key and Value fields, one pair per parameter. Use the Add parameter button to add rows and the small remove button beside a row to delete it. The output updates as you type and appears as one line you can copy. There is no leading question mark in the result, so you add the question mark yourself when you append it to an address. Rows where the key is empty (or only spaces) are skipped entirely, and keys are trimmed of surrounding spaces, but values are kept exactly as typed.
The generator uses the browser's form-style encoding. Letters, digits and a few safe symbols pass through, a space becomes a plus sign, and other special characters become a percent sign followed by two hex digits, applied to the UTF-8 bytes of the character. For example, an ampersand inside a value becomes the code for ampersand so that it cannot be mistaken for a separator, and an accented letter becomes two percent groups. Both keys and values are encoded, and pairs are joined with an ampersand in the order of your rows.
Enter these hypothetical rows: q with the value red shoes & socks, page with 2, and city with Zurich or an accented spelling if you like. The output is: q=red+shoes+%26+socks&page=2&city=Z%C3%BCrich. Because the ampersand in the search phrase was encoded, a server reading the link sees one q parameter, not the start of a new one. If you paste the same result into the Query String Parser on this site, you get your original rows back.
Many people expect spaces to become percent-twenty. This generator produces a plus sign, which is correct for the query part of an address and for form submissions and is understood by virtually every server framework. If a system you work with insists on percent-twenty for spaces, replace the plus signs in the output for space-derived characters manually. Take care not to touch a literal plus in your data: a real plus sign in a value is encoded as percent-2B, so it stays distinguishable from a space.
Yes -- values are passed through standard URL encoding, so spaces, ampersands, and other special characters in your values won't break the resulting URL.
No. Enter plain text and the tool encodes it. Pre-encoded values would be encoded a second time.
That is the standard form encoding for query strings, and servers decode it back to a space. A real plus sign in your text is encoded as percent-2B instead.
No. Add the question mark yourself when attaching the result to an address.
It is skipped, so blank rows do not create stray equals signs.
Reference: MDN Web Docs