ToolHive

Parse and Build URL Query Strings

Break query strings into editable key-value rows, then rebuild an encoded query string for debugging, redirects, and API requests.

query string parserquery string builderurl query paramsurl params editoredit query string

Interactive Converter

Raw Query String
Parsed Parameters
0 rows ยท Repeated keys are preserved in order and empty rows are skipped during output generation.
No parameters yet. Add a row or paste a query string above.
Built Query String
The result is encoded with URLSearchParams and does not include a leading question mark.
No parameters yet. Add a row or paste a query string above.

Intro

This query string parser and builder is useful when a full URL parser is too broad and you need to focus specifically on search parameters.

It keeps repeated keys, supports encoded characters, and helps you move quickly between raw query strings and a structured editor view.

How to use

  1. Paste a raw query string
    Add a query string with or without a leading question mark.
  2. Review and edit parameters
    Adjust keys and values in the row editor, add new parameters, or remove old ones.
  3. Copy the rebuilt result
    Use the generated query string in redirects, API requests, campaign URLs, or debugging sessions.

Examples

Parse multiple parameters
Inspect and rebuild a query string with repeated keys.
Input
?tag=dev&tag=tools&sort=desc
Output
tag=dev&tag=tools&sort=desc
Handle encoded values
Useful when redirect targets or names are already URL-encoded.
Input
?name=Alex%20Chen&redirect=%2Fdocs%3Ftab%3Dapi
Output
name=Alex+Chen&redirect=%2Fdocs%3Ftab%3Dapi

FAQ

Does this tool support repeated query keys?

Yes. Parameters are stored as ordered rows so values like tag=dev&tag=tools are preserved instead of being collapsed into a single key.

Does the rebuilt result include a leading question mark?

By default, the built result does not include a leading question mark so you can reuse it in different contexts. The UI also provides a copy action that includes ? when you need the full query string form.

How are spaces and encoded values handled?

The tool rebuilds the output with URLSearchParams. That means spaces may be normalized during encoding, and existing encoded values are preserved as query-safe output.

What is the difference between this and a full URL parser?

A full URL parser focuses on protocol, host, and path structure. This tool focuses on editing and rebuilding the query string itself.

Related tools

Related guides

  • No related guides in the current seed set.