Free tool

URL parser

Break down, edit and clean URLs: parameters in a table, the real destination of redirects and security warnings.

Real destination after unwrapping redirects

www.google.com → https://shop.example.com/es/zapatillas?color=negro&talla=42&utm_source=newsletter&utm_medium=email&fbclid=IwAR3x#opiniones

  • Tracking parameters: ved.
  • Carries another URL inside the parameter: url.
  • It is a redirect link from a known service: the real destination is inside.
1. url

Query parameters (0)

Rebuilt URL

Limits
  • Redirects are unwrapped only by reading the URL (Google, Facebook, Instagram, Outlook Safe Links, YouTube, LinkedIn, DuckDuckGo, Bing, Yahoo and others). No link is visited, so shorteners such as bit.ly cannot be resolved.
  • The tracking list covers the most common parameters; review each case, as some sites use names like si or trk for other purposes.
  • Batch cleaning keeps the original encoding of parameters that are not removed.
  • Everything happens in your browser: URLs are never sent to a server.

Built by

Miguel Ángel Colorado Marin (MACM)

Full-Stack Developer · Guadalajara, España

I develop web apps, digital tools and full projects — from design to deployment.

GitHubLinkedInBuy me a coffee
Contact me

The URLs we copy every day are rarely clean: they carry utm_source, fbclid or gclid, arrive wrapped in Google or Outlook redirects and sometimes hide tricks such as https://bank.com@malicious-domain.net. This parser splits every piece of the URL, decodes the parameters into a table you can edit and rebuilds the address with the encoding you choose. It also extracts the real destination of the most common redirect links without visiting them and warns you about signals used in phishing, useful both when debugging an integration and before clicking a dubious link.

Features

  • ✓Protocol, username, password, host, effective port, path segments, query and fragment
  • ✓Editable parameter table: enable, rename, reorder, add and delete, with the URL rebuilt instantly
  • ✓Detects and strips tracking parameters: utm_*, fbclid, gclid, msclkid, _ga, mc_eid and more
  • ✓Unwraps Google, Facebook, Instagram, Outlook Safe Links, YouTube, LinkedIn, DuckDuckGo, Bing and Yahoo redirects, even nested
  • ✓Security warnings: credentials before @, IP as host, suspicious punycode, double encoding and javascript: schemes
  • ✓Configurable encoding: spaces as + or %20 and strict RFC 3986 mode
  • ✓Batch cleaning of URL lists keeping the original encoding
  • ✓Exports parameters as JSON with repeated keys grouped into arrays

How do I parse and clean a URL?

  1. 1

    Paste the URL

    Paste the full address. If it is relative, enable the base URL option.

  2. 2

    Check warnings and real destination

    See whether it is a redirect, which parameters are tracking and whether there are risk signals.

  3. 3

    Edit the parameters

    Disable, rename, reorder or add parameters and adjust path, host or fragment.

  4. 4

    Copy or batch clean

    Copy the rebuilt URL or paste a list in batch mode to clean them all at once.

Frequently asked questions

What are utm and fbclid parameters?

They are tracking parameters. utm_* tell the site's analytics which campaign you came from, and fbclid, gclid or msclkid identify the click on Facebook, Google Ads or Microsoft Ads. They do not change the page you see, so you can remove them when sharing a link.

Why can a URL containing @ be dangerous?

Everything before @ in the host part is read as a username and password. In https://yourbank.com@phishing.net the browser visits phishing.net, even though it looks like the bank at first glance.

How is the destination of a Google or Facebook link obtained?

Those services wrap the destination in a parameter such as url, q or u. The tool recognizes it, decodes it and repeats the process when there are several layers, without opening the link. Shorteners such as bit.ly do not carry the destination in the URL and cannot be resolved without visiting them.

Spaces as + or %20?

In HTML form query strings a space is encoded as +, and elsewhere in the URL as %20. Nearly every server accepts both in the query; pick + to mimic a form and %20 to follow RFC 3986.

Is the URL visited or sent?

No. All analysis happens in your browser with the standard URL API; no link is opened or shared.

Related tools

URL Encoder

Encode and decode URLs instantly.

Redirect Checker

URL redirect chain with status code and time.

Fake Domains

Homoglyphs and punycode.

Phishing URL Checker

Fake links before you click.

Embed URL Parser and Cleaner on your site

Add URL Parser and Cleaner to any web page with a simple iframe. Free, with attribution to miguelacm.es.

<iframe
  src="https://miguelacm.es/embed/url-parser"
  width="100%"
  height="700"
  frameborder="0"
  title="URL Parser and Cleaner — miguelacm.es"
></iframe>
View embed in new tab →
View source on GitHub