Articles · Developer Tools
Parse, encode, build UTM links, and strip trackers
A support ticket, an analytics export, and a campaign brief all argue about the same URL. One person needs the host. Another needs utm_campaign. Someone else pasted a string that is still percent-encoded. Doing that in the address bar is how you drop a fragment or double-encode a query. One toolkit with parser, query editor, encode/decode, UTM builder, and tracking cleaner keeps the work in one place without a shortening API.
Why this is worth doing in the browser
The browser URL API is enough when you stay on http and https. DevNestro’s URL Toolkit parses protocol, host, port (or Default), path, query pairs including duplicates, and fragment. The query editor adds, edits, and deletes rows, then rebuilds the URL. Encode and decode distinguish full-URL escaping (keeping : and /) from query-component escaping. UTM builder fills source, medium, name, term, and content on a website URL you supply. The tracking cleaner lists known keys such as utm_*, fbclid, and gclid and removes only the ones you tick. Unknown parameters stay. No shortening network, no API key.
How to use the tool
Paste a URL, parse, edit rows, regenerate. Use encode tabs when a value must survive a query string. Build a campaign URL from fields. Review tracker checkboxes before you clean. Copy the result. Pair with the QR generator when the next step is a printed code, or Scam Checker when the link itself is the question.
- Parse before you edit so you can see duplicate keys.
- Use component encode for values, not for an entire https URL, unless you intend to escape the scheme.
- Fill UTM fields you actually use; empty fields are omitted.
- Uncheck a tracker if you need to keep it for a test.
Privacy
Parsing and encoding run in the page session. URLs you enter here are not sent to a link API. Analytics does not record the URL contents.
Stop rewriting query strings in a notebook. Open the URL Toolkit, parse once, and copy a URL you meant to ship.