100% offline
Developer
Free · no signup
Updated

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

  1. 01

    Paste your URL

    Paste any URL into the input field.

  2. 02

    Inspect the parts

    Every section (protocol, host, path, params, hash) is shown individually with copy buttons.

  3. 03

    Edit and rebuild

    Toggle off unwanted parameters or edit any value — the rebuilt URL updates live.

When to use URL Parser vs alternatives

AlternativeUse URL Parser when…Use the alternative when…
`new URL()` in the browser consoleyou want every parameter as a visible editable row.you are already scripting.
Shortlink servicesyou only need to read the URL, not republish it.you need a shorter shareable form.

Frequently asked questions

What does the parser show me?
Protocol, username/password (if present), hostname, port, pathname, every query parameter as a key/value row, and the URL fragment (hash). Each piece is individually copyable.
Why are some characters in my URL different after parsing?
The native URL constructor normalises encoding. For example, spaces appear decoded in the parameter table but re-encoded as %20 in the rebuilt URL — which is correct per the URL spec.
Can I edit parameters and rebuild the URL?
Yes. Toggle off or change any parameter and the canonical URL updates immediately. Useful for cleaning tracking parameters before sharing a link.