Is Compare Two URLs free?
Yes. This tool is free to use with no sign-up, and it runs entirely in your browser.
Are the URLs sent to a server?
No. Both URLs are parsed and compared locally in your browser, so they never leave your device.
Does parameter order affect the comparison?
The comparison normalizes parameter order for the main diff, but it still keeps repeated-key differences visible where order and count matter.
Can I use it for campaign QA?
Yes. It is useful for checking whether a final campaign URL still matches the intended destination and tracking setup.
What differences does it show?
It shows differences in origin, path, and fragment, plus added, removed, and changed query parameters between the two URLs.
The two URLs look different to me but the tool says nothing changed. Why?
Most likely you are looking at a parameter-order difference or an encoding difference. Both are normalized: keys are compared as a set, and values are compared after percent-decoding. To a server those two URLs really are equivalent, even though the strings are not identical.
Are trailing slashes treated as a difference?
Yes. /pricing and /pricing/ are two different paths and the tool reports the path as changed. Most sites redirect one to the other, but the redirect can drop a query string on the way, which is exactly why the difference is worth surfacing.
What counts as a repeated-key difference?
It is flagged when a key appears more than once on either side and the list of values for that key is not identical in the same order. A URL with ?id=1&id=2 versus ?id=2&id=1 will be reported, because a back end that takes the first value will behave differently for each.
Can I use this to check a redirect kept my tracking params?
You can compare the URL you sent against the URL you landed on, but you have to get the landing URL yourself: open the link, copy the final address bar contents, and paste it as the second URL. The tool does not follow redirects.
Do the URLs get uploaded anywhere?
No. Both URLs are parsed and compared in your browser, and the summary and JSON downloads are generated from memory. Campaign URLs often carry click IDs and user identifiers, so keeping the comparison local avoids leaking either.
What does the JSON export contain that the summary does not?
The JSON carries the full parsed structure of both URLs, including every parameter with its utm, tracking, repeated, and hasValue flags, alongside the comparison result. The text summary is the four booleans plus the added, removed, changed, and repeated-key key names.