29 characters · 1 words · 29 bytes (UTF-8)
Output will appear here
Click in the output to select all text
29 characters · 1 words · 29 bytes (UTF-8)
Output will appear here
Click in the output to select all text
Deconstruct URLs into protocol, host, port, path, query parameters, and hash fragment.
Test regular expressions with real-time match highlighting, flags, and capture groups.
Generate standard localhost and local development test URLs with ports and routes.
Turn any title or text string into a clean, URL-safe SEO slug.
Look up HTTP response status codes (1xx, 2xx, 3xx, 4xx, 5xx) with descriptions and specs.
This query string tool works both ways: paste a query string to parse it into readable key-value pairs, or enter individual parameters to build a properly URL-encoded query string from scratch. It's a practical url params tool for developers wiring up API requests, debugging redirect URLs, or constructing tracking links with UTM parameters. Because it handles encoding and decoding automatically, you don't need to remember which characters require percent-encoding or worry about malformed ampersands. It's useful for backend engineers, frontend developers, and marketers alike who need a reliable url query encoder without opening a code editor. As with every tool here, parsing and building happen instantly in your browser - nothing is uploaded, no signup required. Use the input below to parse an existing query string or assemble a new one parameter by parameter.
This tool focuses specifically on the query string portion and also lets you build one, while the URL parser breaks down a full URL into all its components.
Yes, repeated keys are grouped and displayed as an array of values under that key.
It uses standard percent-encoding (%20) for spaces, matching the encodeURIComponent behavior in JavaScript.
Yes, the tool will detect and extract the query string portion automatically if a full URL is pasted.
The tool supports common bracket-style array notation, but query strings are fundamentally flat key-value pairs by spec.
No, the tool generates the raw query string and you can add the leading '?' when appending it to a URL.
Yes, all reserved and special characters are properly percent-encoded to keep the resulting URL valid.