Toolono
Developer Tools
View All Developer ToolsDate & Time
View All Date & Time ToolsText Tools
View All Text ToolsOnline Converters
View All Online ConvertersQuery Param Merger
Merge parameters from one full URL or raw query string into another while preserving the final output order and replacing older matching keys.
Merge query parameters without rebuilding the full result by hand
Paste two query sources, merge them, and copy the final result with updated values.
Merge one query source into another and keep the result copy-ready
Use Query Param Merger when you need to combine two query sources, such as a copied URL and a new filter set, or a saved callback example and a new tracking block. The first input defines the output format, and matching keys from the second input replace older values before the merged result is returned.
Paste both query sources to merge the second input into the first.
Merged query result
Review the merged URL or query string, confirm how many parameters were replaced or appended, and copy the final output when it is ready.
Ready
Your merged URL or query string will appear here.
The result card will show the merged output and replacement summary as soon as both inputs are complete.
Merged result Copy-ready merged output
Your merged URL or query string will appear here.
How to use Query Param Merger
- Paste the primary full URL or raw query string into the first field.
- Paste the second query source you want to merge into the primary input.
- Review the merged URL or merged query string in the result card.
- Check how many existing parameters were replaced and how many final parameters remain.
- Use Copy Result when the merged output matches the parameter set you want to keep.
Query Param Merger examples
-
Merge page=1&view=grid into a copied search URL
-
Apply updated utm_source and utm_campaign values to an existing tracking link
-
Merge one raw query string into another without reordering the remaining pairs
-
Replace old ref values with a newer ref block from another URL
-
Combine a saved callback example with a new query parameter set
What this Query Param Merger does
This tool merges one query source into another and returns a copy-ready result. The first input defines the output type, so a full URL stays a full URL and a raw query string stays a raw query string. When the second input includes a key that already exists in the first input, the newer values replace the older matching keys before the final output is rebuilt.
When merging query parameters is useful
Merging query parameters is useful when you want to apply a new filter block to a saved search link, update one campaign block inside a tracked URL, merge callback parameters from two test cases, or combine repeated query parameters without rewriting the whole string by hand. It is especially helpful when the second input contains the latest values you want to keep.
Query Param Merger vs URL Query Editor
Query Param Merger is for one-step combination: paste two query sources, merge them, and copy the result. URL Query Editor is better when you need to inspect every parameter row manually, change values one by one, or add and remove keys interactively.
Query Param Merger FAQs
Can I merge a full URL with a raw query string?
Yes. The first input can be a full URL or a raw query string, and the second input can also be either one. Only the query parameters from the second input are merged in.
What happens when the same key appears in both inputs?
Matching keys from the second input replace older matching keys from the first input, and the incoming pairs are then appended in their original order. If the second input repeats the same key more than once, those repeated pairs stay together in the merged result.
Does this keep repeated parameter keys?
Yes. Repeated keys from the merge input are preserved, and repeated keys in the primary input remain unless they are replaced by the same key from the merge input.
Does Query Param Merger keep the fragment from the full URL?
Yes. When the primary input is a full URL, the output keeps its original path and fragment while rebuilding only the query portion.
How is the final parameter order determined?
The final result keeps the original order of primary parameters that were not replaced. Parameters from the merge input are then appended in the same order they appeared there.
Does this match parameter keys exactly?
Yes. Parameter keys are matched exactly as written, so `utm_source` and `UTM_SOURCE` are treated as different keys.