Query String Parser

Parse a URL query string into readable parameters, or build one from key-value pairs — free.

About

About the Query String Parser

Splits a URL or query string into readable parameters, and builds a query string back from key=value pairs.

Developers use it to see exactly what parameters a long, encoded URL is carrying, while marketers use it to assemble a campaign link with several UTM parameters without making a typo. It's one of many free data tools on Toolapt, and like every tool here, it's free to use with no sign-up and no limit on how many times you run it.

Choose what to view about this tool

Guide

Using the Query String Parser

  1. 1

    Step 1

    Paste a full URL or just a query string into the first field.

  2. 2

    Step 2

    Click "Parse" to see each parameter and its decoded value in a table.

  3. 3

    Step 3

    Edit the auto-filled key=value lines below, or start a fresh list.

  4. 4

    Step 4

    Click "Build query string" to assemble it, then "Copy" to copy the result.

  • Parses either a full URL or a bare query string
  • Decodes each parameter's value and shows it in a clear table
  • Automatically fills the builder with the parsed parameters for quick edits
  • Builds a properly encoded query string from simple key=value lines
  • Reports how many key=value lines were skipped for having no key
  • Works entirely in your browser — nothing you paste is sent to a server
  • Free to use, with no sign-up and no limit on how many times you run it

Developers

Developers use the Query String Parser for seeing exactly what parameters a long, encoded URL from a log or bug report is carrying.

Marketers

Marketers use the Query String Parser for assembling a campaign link with several UTM parameters without making an encoding mistake.

QA engineers

QA engineers use the Query String Parser for checking that a redirect or tracking URL contains exactly the parameters it should.

Support teams

Support teams use the Query String Parser for reading the parameters out of a link a customer pasted into a ticket.

Examples

Query String Parser examples

3 worked examples

01

Parsing a search URL

Paste https://example.com/search?q=blue+shoes&page=2 and click Parse to get a table showing q = "blue shoes" and page = "2", decoded from their URL-encoded form.

02

Building a campaign link

Enter utm_source=newsletter, utm_medium=email and utm_campaign=fall+sale on separate lines, then click Build query string to get utm_source=newsletter&utm_medium=email&utm_campaign=fall%2Bsale ready to append to a URL.

03

Skipping a malformed line

Include one line with no equals sign, like just "oops", among otherwise valid key=value lines; the builder skips that line and reports it was skipped instead of breaking the whole result.

FAQ

Frequently asked questions

Quick answers to common questions about the Query String Parser.

What does the Query String Parser do?

It splits a URL or query string into its individual, decoded parameters, and separately builds a query string back from a list of key=value lines.

Is the Query String Parser free to use?

Yes. It's free, with no sign-up, no watermark and no limit on how many times you use it.

Is my URL safe when I use this tool?

Yes. Parsing and building both happen entirely on your own device using the browser's built-in URLSearchParams support — nothing you paste is sent to a server.

Can I paste a full URL, or does it need to be just the query string?

Either works. If you paste a full URL, the tool finds the part after the ? automatically and ignores any # fragment.

What happens after I click Parse?

The parameters are shown in a table, and the same key=value pairs are written into the builder section below so you can tweak them and rebuild.

What does the builder do with duplicate or malformed lines?

Each line needs an = sign to be treated as a key=value pair; lines without one are skipped, and the result tells you how many were skipped.

Can I use this tool on my phone?

Yes. The page is fully responsive and works on mobile, tablet and desktop browsers alike.

Does this tool have any limitations?

It's built for standard query strings using the & separator and = key/value pairs, which covers the vast majority of real-world URLs.

Still have a question? Contact us

Report a problem

Query String Parser

What went wrong?
    or paste a screenshot