Parse any URL into query parameters, edit the query string in a clear table, add, change and delete parameters, and get the rebuilt final URL instantly.
The tool automatically extracts query parameters from the URL you enter and shows them as separate «parameter — value» pairs. Values can be edited, and parameters you don't need can be removed without editing the whole URL string by hand.
Paste an address and the tool splits it into a clean URL and separate query parameter rows. The name and the value of every parameter are editable, unwanted parameters are removed with one button, new ones are appended at the end of the table, and the final URL is rebuilt on every change.
Object and array values are detected automatically and can be opened in a multi-line editor with formatting and syntax validation. A separate block returns the final URL, the clean URL, the query string and all parameters as a single JSON object with a copy button.
The Query Parameter Editor is an online tool for parsing and editing GET parameters inside an existing link. Paste a URL and it is split into a clean address without the query string and a table of parameters where every name and every value is editable. The final URL is assembled automatically, so there is no need to count ampersands by hand, watch question marks or clean up leftover parameters in a text editor.
URL parameters are widely used to pass data between pages and web applications. They set filters and sorting, search queries, identifiers, display settings, UTM tags and other service data. When working with long addresses, seeing parameters as a separate list makes it easier to understand the URL's structure and find the values you need.
A URL parameter editor is useful for marketers who need to fix a UTM tag in an already assembled link, for QA engineers testing filters, pagination and sorting, for developers debugging feature flags and A/B experiments, and for site owners analysing traffic. A separate block returns the final URL and all parameters as JSON — a ready-made snippet for a ticket, documentation or an automated test. All processing runs in the browser, with no data sent to a server.
The tool splits the address you paste into two parts: the clean URL without the query string and the list of GET parameters. Every parameter becomes a separate table row with a name field and a value field that you can change, delete or extend with new entries. The final URL is rebuilt on every edit, so the result can be copied straight into a browser, a ticket or an ad platform.
To change a parameter, edit its name or value directly in the table. The bin button on the right of the row removes the parameter together with its value. The «Add parameter» button below the table creates an empty row — type a name and a value, and the parameter appears in the final URL. The order of rows in the table matches the order in the rebuilt address.
The order of query parameters in the final URL matches the order in the table. For most sites, parameter order doesn't affect the result, but some systems may process the URL in a non-standard way, so it's worth checking the final address.
A URL can contain several query parameters with the same name, for example ?tag=free&tag=popular. Whether this is supported, and how it's handled, depends on the site or application the URL is built for.
Duplicates are preserved: if the URL contains two parameters with the same name, the tool shows two separate rows instead of merging them — this matters for array-style values such as id=1&id=2.
Yes. UTM tags are just ordinary URL query parameters, so utm_source, utm_medium, utm_campaign and other UTM parameters can be added, changed and removed the same way as any other parameter.
No. Parsing the URL, editing parameters, rebuilding the final address and generating the JSON output all happen in your browser with JavaScript. Links, tokens and internal parameters never leave your device, so the tool is also safe for staging and intranet addresses.
Common scenarios include: fixing a UTM tag in a finished link without rebuilding it from scratch; testing catalogue filters, pagination and sorting; debugging A/B experiments and feature flags passed through query parameters; checking how an application reads JSON parameters; preparing sets of test links for QA; and sharing a parsed URL with colleagues as JSON.
