Introducing the URL Parser — Break Any URL Into Parts

URLs look simple until you have to pull one apart. Is the port the default or a custom one? How many path segments are there really? Which query parameter is breaking your API call? Squinting at a long string in the address bar is a slow, error-prone way to find out. So we built the URL Parser to do it for you — instantly.

What it does

Paste any URL and the tool breaks it into every component the WHATWG URL standard defines:

• Scheme / protocol — https:, http:, ftp:, and friends
• Username and password — the deprecated-but-still-valid userinfo
• Host and hostname — with and without the port, so the difference is obvious
• Port — including showing when the default is being used
• Path and path segments — the full path plus each /-separated segment listed out
• Query string and parameters — rendered as a clean key/value table, with repeated keys preserved
• Fragment / hash — everything after the #

That query parameter table alone saves a surprising amount of time. Instead of mentally splitting ?role=admin&active=true&tag=a&tag=b on every & and =, you get a tidy list — duplicate keys and all. Values are decoded for you too, so %20 shows up as a real space and %C3%A9 becomes é, exactly as the server would receive them.

Why it runs in your browser

The tool uses the browser’s native URL and URLSearchParams APIs — the exact same parser the browser itself uses to load pages. That has two big benefits. First, the breakdown is 100% accurate: it normalizes ports, resolves dot-segments, and handles punycode exactly the way a real request would. Second, nothing leaves your machine. Your URL — which might contain tokens, internal hostnames, or credentials — is never uploaded. There is no server, no logging, and no sign-up.

Who it’s for

If you build or debug anything on the web, this is for you: API developers checking why a request 404s, frontend engineers untangling SPA routes, SEO folks auditing tracking parameters, and anyone who has ever lost a fragment in a redirect. Paste, read, done.

Learn the components

Want to understand what each part actually means and how browsers and servers treat it? Our companion guide How to Parse a URL walks through every component with worked examples and common debugging scenarios.

Give the URL Parser a try the next time a URL is misbehaving — it is free, private, and instant.