Read any monstrous URL. Tweak it. Rebuild it.
Paste a giant OAuth, redirect or UTM link to break it into protocol, host, path and params, decode the percent-encoded query string into an editable table, and watch the URL rebuild itself as you edit. UTM and click-id trackers get flagged. It all happens in your browser — nothing is uploaded.
Query parameters
No query parameters.
| key | value | decoded | tag |
|---|
Encode / decode a single value
FAQ
Is my data sent anywhere?+
No. The URL you paste is parsed, decoded and rebuilt entirely in your browser — it is never sent to a server, and neither are the values you type into the encode/decode box. We count anonymous, aggregate usage on our own server (a page view, that a URL was inspected) — never your URL, its params, or anything you type.
What counts as a "parameter", and why decode them?+
Everything after the ? is the query string: key=value pairs joined by &, where keys can repeat and order matters. To survive transport, special characters are percent-encoded (a space becomes %20 or +, a slash becomes %2F). This tool decodes each value so you can actually read it, lets you edit the table, and re-encodes everything when it rebuilds the URL — so an edited café ✓ goes back out as valid caf%C3%A9+%E2%9C%93.
What are the UTM and tracking tags?+
Marketing links carry campaign params (utm_source, utm_medium, utm_campaign…) and ad click-ids (gclid, fbclid, msclkid and friends) that identify where a click came from. We flag them with a tag so you can spot — and delete — the tracking cruft before sharing a clean link. It's all local; we never log which params you had.