Are keys and values automatically URL-encoded?

Yes. Encoding uses the browser's built-in URLSearchParams API. Spaces become %20, ampersands become %26, equals signs become %3D, and full Unicode (including emoji) is escaped to its UTF-8 percent form. The output is safe to append to any URL without further escaping.

Does it handle repeated keys for array-style parameters?

Yes. Add the same key on multiple rows — the builder includes each row's value as a separate parameter in the output (e.g., tag=alpha&tag=beta). This matches what Express's qs parser, Rails strong parameters, and most modern backends consume by default.

Can I parse an existing query string back into rows?

Not in this tool — it's a builder, not a parser. To break a query string apart, use our URL Parser, which decomposes the full URL (protocol, host, path, query, hash) and lists every parameter with auto-labeled UTM and tracking tags. Build here, parse there.

What's the difference between this and the UTM Builder?

This tool is a generic any-parameter builder — keys and values are freeform. The UTM Builder is purpose-built for Google Analytics campaign URLs with named fields (Source, Medium, Campaign, Content, Term) and validation specific to UTM conventions. Use UTM Builder if you only need campaign URLs; use this when you need arbitrary query parameters for APIs, filters, or deep links.

Does the tool support empty values or empty keys?

Empty values output key= (a key followed by an equals sign and nothing). Empty keys are skipped — a row with no key contributes nothing to the output. To remove a parameter, delete the row instead of clearing one of its fields.

Is my data sent to a server?

No. Everything runs locally in your browser. The URLSearchParams API is built into every modern browser, and the tool never makes a network request with the keys, values, or generated query string. Safe for URLs containing tokens, session IDs, or proprietary parameters.

Will the output work with my framework's query parser?

For repeated keys (arrays), yes — Express qs, Rails strong parameters, Spring @RequestParam List, ASP.NET model binding, and Go's url.Values all accept the standard ?key=a&key=b format. PHP defaults are an exception: you may need ?key[]=a&key[]=b — type the brackets explicitly in your key field if so.

Web & SEOTeil von Web- & SEO-Tools →

Query-String-Builder

URL-Query-Parameter erstellen und analysieren.

Ihre Daten bleiben auf Ihrem GerätKein Upload, kein ServerFunktioniert offline

Query parameters

KeyValue

Filled params

Preview

?tool=json-formatter&lang=de

Encoded query string

Warum dieses Tool verwenden

Query-Strings aus Schlüssel-Wert-Paaren generieren und vorhandene Query-Strings analysieren.

Vereinfacht das Bearbeiten von URL-Parametern.

Unterstützt sowohl das Erstellen als auch das Analysieren von Query-Strings.

So wird's verwendet

01Schlüssel-Wert-Paare hinzufügen oder Query-Text einfügen.

02Den generierten Query-String kopieren.

Schnellcheck vor dem Kopieren

Confirm the input is the format you intended.

Scan the result before using it in a document, URL, config, or message.

Copy only the output you need.

FAQ

Werden Werte URL-enkodiert?

Ja. Schlüssel und Werte werden sicher enkodiert.

Kann ein vorhandener Query-String analysiert werden?

Ja. Einen Query-String einfügen und das Tool teilt ihn in bearbeitbare Schlüssel-Wert-Zeilen auf.

Werden doppelte Schlüssel verarbeitet?

Ja. Derselbe Schlüssel kann in mehreren Zeilen erscheinen und jede Instanz wird in der Ausgabe einbezogen.

Query-String-Builder

Warum dieses Tool verwenden

So wird's verwendet

Schnellcheck vor dem Kopieren

FAQ

Verwandte Tools

URL-Parser

UTM Builder

Campaign URL Workspace

Query-String-Builder

URL-Parser→

UTM Builder→

Campaign URL Workspace→

URL-Parser

UTM Builder

Campaign URL Workspace