A full URL (https://...) or just the query string portion (?key=value&...).

Are encoded values decoded?

Yes. All percent-encoded values and + signs are decoded automatically.

Is there a limit to the number of parameters?

The table lists every parameter URLSearchParams finds, so URLs with hundreds of parameters work. Your browser's memory is the only practical limit.

What happens to repeated keys?

Each occurrence gets its own row, in the order it appears, so ?tag=a&tag=b lists tag twice with the values a and b.

Query String Parser

Paste a URL or query string and see every parameter neatly decoded in a table. Handy for debugging API calls and analytics URLs.

Input

Output

Parsed key/value pairs appear here…

URL TOOLS

Query String Parser

Parses a URL query string into individual key/value pairs. Paste the full URL or just the query portion.

Runs entirely in your browser

How it works

The tool keeps everything after the first ? (or the whole input when there is none), drops any #fragment, and hands the rest to URLSearchParams. URLSearchParams splits on &, decodes percent-escapes, reads + as a space, and returns each key and value in order, including repeated keys. A full URL with no ? has no parameters to show.

Processing runs in your browser

All encoding, decoding, and parsing happens inside your browser tab. Our servers are not involved at any point. You can see this yourself in your browser's DevTools Network tab.

Technical specification

Percent-encoding (URL encoding) is defined in RFC 3986 §2.1 (IETF, 2005). Each octet is written as % followed by two uppercase hexadecimal digits. Unreserved characters (A-Z, a-z, 0-9, -._~) never need encoding, and reserved characters (:/?#[]@!$&'()*+,;=) are encoded when they appear inside a value. This tool uses JavaScript's encodeURIComponent and decodeURIComponent, defined in the ECMAScript standard (ECMA-262). encodeURIComponent also leaves ! ' ( ) * as they are, so a system that expects strict RFC 3986 output may need those five escaped. Query string parsing uses URLSearchParams from the WHATWG URL Standard, which reads + as a space.

Standard: RFC 3986. Uniform Resource Identifier (URI): Generic Syntax
Encoding unit: One octet → %XX (two uppercase hex digits)
Space encoding: %20 per RFC 3986; + in HTML form data (RFC 1866)
Browser API: encodeURIComponent() / URLSearchParams

Related operations

To encode binary blobs as text, try Base64. For escaping reserved markup characters, use HTML entities. To inspect the encoded query body of a JSON request, see the JSON formatter.

Frequently asked questions

What can I paste in?: A full URL (https://...) or just the query string portion (?key=value&...).
Are encoded values decoded?: Yes. All percent-encoded values and + signs are decoded automatically.
Is there a limit to the number of parameters?: The table lists every parameter URLSearchParams finds, so URLs with hundreds of parameters work. Your browser's memory is the only practical limit.
What happens to repeated keys?: Each occurrence gets its own row, in the order it appears, so ?tag=a&tag=b lists tag twice with the values a and b.

Last reviewed September 30, 2026

Other pages for this tool

Related tools

Background reading: Complete guide to data tools