DDevsDrill

URL Parser & Diff

Break a URL into parts, edit query params, rebuild it — or paste two URLs and see exactly what changed.

KeyValue

Why parse and compare URLs?

Tracking links, API endpoints and UTM campaigns often differ by a single query param. A local URL parser and diff makes those differences obvious without sending links to a third party.

Parse mode splits a URL into editable parts and a query table you can rebuild after edits. Compare mode shows field-by-field and param-by-param differences between URL A and URL B, which catches missing UTM tags, wrong environments, encoding issues and accidental http versus https mismatches before you ship a broken redirect.

After rebuilding, copy the URL or JSON representation into tickets or chat. Pair with curl-to-code when the same endpoint appears in a captured request. Keep private signed URLs and one-time tokens off shared screens, and clear the form when you finish on a shared machine.

UTM typos, duplicated keys and mixed encoding (%20 vs +) create noisy analytics and broken deep links. A local parser keeps customer or internal URLs off third-party servers while you reconcile two versions. Combine with curl-to-code when the same request must become Fetch or Python next.

When to use

Reach for the URL parser and diff when campaign links, API endpoints, deep links or redirect chains disagree. Marketing sheets, mobile configs and backend tables often drift by a single query parameter or encoding difference that is hard to see in a long string.

Step by step

  1. Paste one URL to inspect protocol, host, path, query and hash.
  2. Paste a second URL when you need a side-by-side diff of parts.
  3. Note which parameters differ, which are missing, and which are only encoding changes.
  4. Fix the source of truth (sheet, CMS or config) and re-check.

FAQ

Does it call the network?

No. Parsing is local. It does not fetch the URL or follow redirects.

Can it decode punycode hosts?

It uses browser URL parsing. Display details depend on the runtime’s URL implementation.

What about malformed URLs?

Invalid strings may fail to parse. Add a scheme (https://) if the browser requires it.

Are fragment identifiers compared?

Hash/fragment differences are included in parts comparison when present.

Does it follow redirects?

No. It analyzes the strings you paste. Use your browser or curl -I to inspect redirect chains.

Are tracking parameters removed?

Nothing is stripped automatically. You decide what to keep after you see the parsed parts.

How it works

Paste a URL and click Parse to split protocol, host, path, query and hash. Edit parts or query rows and Rebuild. Switch to Compare, paste two URLs, and see field-by-field and param-by-param differences.

Is my data safe?

Yes. Parsing and comparison run entirely in your browser with the URL API. Nothing is uploaded to DevsDrill servers.