URL Parser & Components

Key features

• Live decomposition with a quarter-second debounce: href, protocol, origin, username, hostname, port, pathname, search and hash on separate rows.
• Per-row copy buttons for every component, plus a “copy all as JSON” action for handing the whole breakdown to a colleague or a test fixture.
• Query parameters are decoded and listed individually (key and value) with their own copy controls — up to 30 with a count of the rest.
• Passwords in URLs are shown as presence-only (“set, length N”) and are excluded from JSON copies — no secrets leak into your clipboard.
• Malformed input gets a helpful rescue action: one tap retries the parse with an https:// prefix, which fixes the most common typo.

How it works

1. 1

   Paste a URL

   Any absolute URL parses live. Relative or scheme-less strings are flagged with a clear error instead of guessing.

2. 2

   Read the component table

   Each row is one URL property from the WHATWG URL spec — what you see is exactly what fetch() and <a> elements will use.

3. 3

   Copy what you need

   Grab a single value, the decoded query parameters, or the whole component set as JSON.

Tips for better results

• 💡An empty Port row means the URL uses the scheme default (443 for https, 80 for http) — that's normal, not an error.
• 💡The search row shows the raw query string; the parameter list below shows it decoded, so %20 arrives as a space where it belongs.
• 💡Hash fragments (#section) never reach servers — use them for client-side routing or in-page anchors, not for analytics.

Frequently asked questions