URL Parser
A URL Parser splits any URL into its component parts — protocol, host, port, path, query parameters, and hash — and shows each parameter as an editable row, all using the browser's native URL constructor with zero network activity.
Paste a URL to break it into its components.
About URL Parser
Paste a URL — including the noisy tracking variants with a dozen utm_ parameters — and instantly see its structure. Each query parameter is decoded and shown in a table so you can read it. Edit a value or toggle a parameter off and the rebuilt URL updates live. Built on the standard `new URL()` and URLSearchParams Web APIs.
What URL Parser does
- Splits any URL into protocol, host, port, path, query, and hash
- Renders every query parameter as an editable, toggleable row
- Live-rebuilds the canonical URL as you edit
- One-click strip of UTM and other tracking parameters
- Built on the native URL and URLSearchParams APIs
When to reach for URL Parser
- Cleaning a UTM-stuffed marketing URL before sharing it
- Auditing the parameters a third-party tracker is sending
- Editing one parameter inside a long URL without retyping the whole thing
- Verifying that an OAuth callback URL encodes everything it should
How to use URL Parser
- 01
Paste your URL
Paste any URL into the input field.
- 02
Inspect the parts
Every section (protocol, host, path, params, hash) is shown individually with copy buttons.
- 03
Edit and rebuild
Toggle off unwanted parameters or edit any value — the rebuilt URL updates live.
When to use URL Parser vs alternatives
| Alternative | Use URL Parser when… | Use the alternative when… |
|---|---|---|
| `new URL()` in the browser console | you want every parameter as a visible editable row. | you are already scripting. |
| Shortlink services | you only need to read the URL, not republish it. | you need a shorter shareable form. |
Frequently asked questions
What does the parser show me?
Why are some characters in my URL different after parsing?
Can I edit parameters and rebuild the URL?
Related tools
Related reading
Engineering · 11 min read
Most punycode converters disagree with your browser. We measured it.
Punycode is only the last step of turning a Unicode domain into an xn-- label, and tools that stop there return a different domain than your address bar does. We tested a bare RFC 3492 implementation against the browser's own IDNA on seventeen realistic names: six came back wrong. Then we measured our own against ICU across 1,112,042 code points.
Security · 10 min read
IDN homograph attacks: how a domain can look exactly like another
A homograph attack registers a domain that renders identically to a real one by swapping in letters from another script — Cyrillic а for Latin a. In 2017 an all-Cyrillic xn--80ak6aa92e.com displayed as apple.com in Chrome, Firefox and Opera. Here is how the attack works, why browsers sometimes show you xn-- instead, and the defences that actually hold.