Devs Forge
Developer Utilities

Query String Parser

Query String Parser

Parse URL query parameters into a table and rebuild percent-encoded query strings for API debugging.

Query String Parser workspace

Loading interactive tool...

Parse URL query strings into keys and values, then rebuild encoded query strings for API debugging—without leaving the browser.

Related developer tools

Encoding & URLs

Continue your workflow with these free utilities on developer utilities and adjacent tasks—all browser-based, no upload required.

Browse all developer tools →

Query strings in API workflows

Redirects, search endpoints, and OAuth callbacks pack state into query parameters. A query string parser online turns opaque URLs into tables you can scan, then rebuilds percent-encoded output for tests.

How parsing differs from URL encoder

The URL encoder tool transforms entire strings. This parser splits parameters so you can inspect each key and value, then copy a rebuilt query string.

How it works

  1. 1Paste a full URL or raw query string starting with `?`.
  2. 2Keys and values appear in a table with decoding applied by URLSearchParams.
  3. 3Copy the rebuilt query string after inspecting or mentally editing values.

Examples

Search API URL

https://api.example.com/search?q=dev+tools&page=2&sort=desc

OAuth-style callback

?code=abc123&state=csrf-token-9

Pagination params

?limit=50&offset=100&fields=id,name

Tracking query

?utm_source=newsletter&utm_campaign=launch

When to use this tool

  • Inspect redirect URLs from authentication flows.
  • Debug search API filters and pagination params.
  • Compare staging vs production query parameters.
  • Rebuild query strings after editing values.
  • Document webhook callback parameters.
  • Pair with JWT decoder when debugging tokens in URLs.

Frequently asked questions

Can I paste a full URL?

Yes. The tool extracts the query portion automatically.

Are duplicate keys supported?

URLSearchParams preserves multiple values per key where present.

Is data uploaded?

No. Parsing is local.

How is encoding handled on rebuild?

Rebuilt strings use standard percent-encoding via URLSearchParams.

Does this replace URL encoder?

Use URL encoder for whole-string encode/decode; use this tool for structured parameter editing.

What about hash fragments?

Hash fragments are ignored; only the query string is parsed.