Network & web

URL Query Builder and Parser

Build, parse, edit, encode, and copy URL query parameters locally in your browser.

Runs locally in your browser
Parameters2
Query stringcategory=seo&utm_source=newsletter
https://lumio.pw/tools?category=seo&utm_source=newsletter#top

How to use this tool

Enter a base URL or paste a full URL with existing query parameters.

Use Parse current URL to split an existing URL into editable parameters.

Add, edit, remove, and encode query parameters, then copy the complete URL or only the query string.

Query strings and URL encoding

A query string starts after `?` and stores key-value pairs such as `category=seo&utm_source=newsletter`.

Browsers encode spaces, symbols, and non-ASCII characters so the final URL remains valid.

This builder uses the browser URL API, so repeated parameters, empty values, and special characters are handled consistently.

Repeated parameters and hash fragments

Some APIs and search pages use repeated parameters such as `tag=seo&tag=tools` to represent arrays.

A hash fragment starts after `#` and is not normally sent to the server with an HTTP request.

Use the hash for client-side anchors or app state only when that behavior is intentional.

When to use this instead of UTM Builder

Use URL Query Builder when you need arbitrary query parameters for APIs, filters, redirects, or debugging.

Use UTM Builder when you specifically need campaign parameters such as `utm_source`, `utm_medium`, and `utm_campaign`.

For decoding or escaping individual strings, use URL Encode and Decode.

Examples

Filter URL

Input
https://example.com/search + q=online tools + page=2
Output
https://example.com/search?q=online+tools&page=2

Repeated array-like parameter

Output
https://example.com/articles?tag=seo&tag=privacy

FAQ

Can a URL contain the same query parameter more than once?

Yes. Repeated parameters are valid and are often used for filters or arrays, but each backend decides how to interpret them.

Is the hash fragment sent to the server?

Usually no. The part after `#` is handled by the browser and is not sent in normal HTTP requests.

Does this upload my URL?

No. Building and parsing runs locally in your browser.

Will special characters be encoded?

Yes. The browser URL API encodes spaces and special characters in query parameter names and values.