Loading Query String Parser...
Please wait a moment

How to Parse Query Strings - Step by Step Guide

Step 1

Paste URL or Query String

Paste either a full URL or only the query portion. The parser supports structures defined in RFC 3986 query syntax and works with browser behavior described in the WHATWG URL Standard.

If you need to generate parameters first, use Query String Builder and then validate with this parser.

Accepted Input Formats

  • - Full URL: `https://example.com/search?q=api&page=1`
  • - Query with question mark: `?q=api&page=1`
  • - Query only: `q=api&page=1`
  • - Repeated keys: `tag=seo&tag=analytics&tag=tracking`

Example Input

https://api.example.com/search?query=running%20shoes&brand=nike&brand=adidas&page=2
Step 2

Decode and Inspect Parameters

The tool decodes encoded keys and values using rules similar to decodeURIComponent() and lets you inspect every pair quickly.

For encoding checks, pair this page with URL Encode and URL Decode.

What You Get

  • - Raw key/value tokens exactly as they appear in the URL
  • - Decoded key/value pairs for readability
  • - Grouped JSON output for repeated keys

Decoded Output Example

Input value `query=running%20shoes` is decoded into a readable pair:

RawDecoded
query=running%20shoesquery=running shoes
city=New%20Yorkcity=New York
Step 3

Validate Key Repetition and Ordering

Repeated keys are common in filter URLs and supported by URLSearchParams. This parser preserves those repetitions so you can confirm your request format.

If the full URL looks suspicious, use URL Parser to inspect protocol, host, and path structure too.

Common Repeated-Key Patterns

filter=color&filter=size&filter=brand
tag=seo&tag=analytics&tag=campaign
category=shoes&category=running
Step 4

Export Parsed JSON

Copy parsed data for API debugging, QA documentation, or log analysis. You can also download the output as JSON and compare requests in tools like Chrome DevTools Network tab or Node.js URL utilities.

Useful Workflows

  • - Compare frontend and backend query formats during API testing
  • - Validate encoded values before writing cURL commands
  • - Inspect marketing links before publishing campaigns
  • - Export parsed output for bug reports and QA tickets

Frequently Asked Questions

Can I parse a full URL instead of only query text?

Yes. You can paste either a complete URL or only the query part. The parser extracts the parameter section automatically.

Does it decode encoded characters like %20 and %26?

Yes. Encoded values are decoded for readability, while the raw tokens are also preserved for debugging.

How does it handle duplicate keys?

Duplicate keys remain visible and are grouped in JSON output. This is useful for filters and faceted search URLs.

Can I remove tracking parameters after parsing?

Yes. Use Remove UTM Parameters to clean URLs and keep only essential parameters.

Is this query parser free?

Yes, it is free with unlimited usage and no sign-up requirement.