Paste a URL or a query string into a browser-based query string parser and it breaks it into a readable table of parameter names and values, decoding any percent-encoding along the way. It runs on your device, so a URL carrying tokens, search terms or user ids in its parameters is never uploaded.
Free query string parser. Paste a URL or query string and see every parameter and value in a clean table, with URL decoding and repeated keys handled. Private.
Open Query String Parser → Free toolFree URL encoder and decoder. Percent-encode text for URLs or decode encoded URLs instantly. Handles query strings and special characters.
Open URL Encoder / Decoder →The part of a URL after the question mark is a run of key=value pairs joined by ampersands, and once values are percent-encoded and there are several parameters it becomes a wall of text. A parser splits it on the ampersands and equals signs, decodes each value, and lays the result out as a clean list so you can see exactly what the URL is carrying.
Reading a query string is a common step when debugging redirects, analytics links, OAuth callbacks and tracking parameters. Seeing the decoded parameters also makes it obvious when a URL is carrying more than you expected, like a token or an email address. Because the parsing is local, you can safely inspect a URL from a private system, and a companion encoder handles building or decoding individual values.
Yes. Encoded values like %40 are decoded, so you see the readable value such as an at sign.
Yes. The parser takes the part after the question mark, so a full URL or a bare query string both work.
No. Parsing happens entirely in your browser.