URL Query Builder - QuickToolFlow

Continue Workflow

Related tools to try next

All tools

URL Parser

Parse URLs into protocol, host, path, query parameters, hash, and decoded components.

URL Encoder & Decoder

Encode or decode URL strings for safe web transmission using standard percent-encoding.

UTM Builder

Build campaign URLs with UTM source, medium, campaign, term, and content parameters.

Example

Build a filtered search URL

The builder encodes spaces and special characters so query values remain parseable.

Input


                        https://example.com/search
q=json formatter
sort=recent

Output


                        https://example.com/search?q=json+formatter&sort=recent

Use repeated keys for filters

Repeated keys are common in filter URLs and API requests. This tool keeps each repeated line as its own parameter.

Input


                        https://example.com/tools
tag=json
tag=csv
tag=formatter

Output


                        https://example.com/tools?tag=json&tag=csv&tag=formatter

Encode reserved characters safely

Encoding prevents one value from accidentally becoming multiple query parameters.

Input


                        https://api.example.com/search
q=name=Alice & role=admin
redirect=https://example.com/callback?ok=true

Output


                        A URL where equals signs, ampersands, spaces, and nested URLs are percent-encoded inside values.

Practical Notes

Use UTM Builder for campaign tracking URLs. Use this tool for general query parameters.
Repeated keys are valid in URLs and are useful for filters such as tag=js and tag=css.
Avoid placing secrets, tokens, or private data in URLs because URLs can appear in logs and browser history.
Sort parameters when you need stable URLs for documentation, snapshots, or code review comments.
Keep existing query parameters only when you intentionally want to merge new values into a pasted URL.
For API testing, copy the parsed parameter lines into your notes so reviewers can see exactly which options changed.

How to Use

1. Enter a base URL, with or without existing query parameters.
2. Add one parameter per line using key=value format.
3. Click Build URL to encode and append the query string.
4. Use Parse Existing URL to turn a pasted URL into editable parameter lines.
5. Copy the final URL when it is ready.

Features

Build URLs from a base URL and key-value parameter lines
Automatically percent-encodes query keys and values
Parses existing URL query strings back into editable rows
Supports repeated query keys by using repeated lines
Sorts parameters for more stable testing and documentation
Runs locally in your browser with copy-ready output

Use Cases

Building API request URLs for docs, testing, and debugging
Preparing non-UTM query strings for product or search pages
Encoding special characters inside query parameter values
Normalizing long URLs before sharing them in tickets or examples
Rebuilding filter URLs for QA cases where repeated parameters and sort order matter
Parsing pasted URLs into key-value lines before comparing two request examples

Frequently Asked Questions

What is a URL query parameter?

A query parameter is a key-value pair after the question mark in a URL, such as ?q=search&page=2. Parameters are commonly used for filters, search terms, tracking, and API requests.

Does this tool encode special characters?

Yes. It uses the browser URLSearchParams API to encode keys and values so spaces, ampersands, equals signs, and other special characters are handled safely.

Can I use duplicate parameter names?

Yes. Add the same key on multiple lines to create repeated query parameters.

Is this the same as a UTM builder?

No. A UTM builder is specialized for analytics campaign parameters. This query builder is for general URL parameters.

What happens if my base URL already has parameters?

If Keep existing query is enabled, the new parameters are appended to the existing ones. If it is disabled, the final URL is built from the parameter lines only.

Should I put API keys in query strings?

Avoid it when possible. URLs can be stored in logs, browser history, analytics tools, and referrer headers, so private tokens are safer in headers or server-side configuration.

Why does a space become a plus sign or percent code?

Query strings must encode spaces and reserved characters. Different encoders may use + or %20 depending on context, but both represent a space in query values.