URL Parser

Parse URLs into their parts and inspect query parameters with decoded values. All processing is done locally in your browser.

The URL Parser requires JavaScript. Enable JavaScript in your browser to use this page.

/* When JavaScript is unavailable there is no client-only island to hydrate, so hide the decorative skeleton and collapse the reserved min-height. The route-level <RequiresJavaScript> notice becomes the sole fallback UI instead of stacking a fake tool shell underneath it. */ .client-only-island-shell { min-height: 0 !important; } .client-only-island-shell__placeholder { display: none; }

What this URL parser does

Paste any full URL — like https://api.example.com/v1/search?query=hello&page=2#results — and the parser splits it into protocol, host, pathname, and search string using the browser's WHATWG URL API. Optional parts like port, hash fragment, and username appear in the breakdown table only when the URL actually carries them, so the typical request stays uncluttered. Each query parameter is shown alongside its decoded value so you can spot double-encoded segments without running them through a separate decoder.

When you need to assemble or edit a URL instead of just inspecting one, use the dedicated URL Builder page. Keeping parsing and building on separate routes makes each workflow faster to reach and easier to focus on.

URL parser examples

Inspect a redirect URL to confirm the encoded state or return_to parameter survived round-tripping.
Verify that a percent-encoded query value like hello%20world decodes to the string you expected.
Inspect how a URL containing spaces or non-ASCII characters is normalized by the browser parser before you share it.
Sanity-check that a deep link's hash fragment (#section) survives a copy-paste round trip.

How to use the URL parser

Paste a URL into the URL Breakdown input. The parts table updates instantly and the Search params table appears when the URL has a query string.
Hover over any part to reveal a copy button for that single value — useful when you only need the host or the search string.
Switch to the URL Builder when you want to modify the URL or assemble a fresh one from scratch.

URL parser FAQ

Why does my URL show as "Invalid"?

The WHATWG URL parser requires an absolute URL with a protocol. example.com/path is not a valid input, but https://example.com/path is. If you only have the path portion, prefix it with https://example.com for testing.

What is the difference between `encodeURI` and `encodeURIComponent`?

encodeURIComponent encodes every character that is not valid inside a query parameter — including /, ?, &, and #. Use it when you are encoding a single param value. encodeURI preserves the structural characters of a URL (:/?#&=) so the result still parses as a URL. The Builder uses the URL API internally, which applies the correct encoding for whichever component you are editing.

Can the same key appear more than once?

Yes. Many APIs accept repeated keys (e.g. ?tag=a&tag=b) and the parser preserves them in the order they appear. The Builder also lets you add the same key multiple times — every non-empty key in the list is appended to the reconstructed URL.

How is my URL processed?

All parsing and building happens in your browser via the WHATWG URL API. Your URL is never sent to a server. That said, URLs sometimes include sensitive query parameters (auth tokens, session ids) — avoid sharing them in public channels regardless of which tool you use.

Privacy

All URL parsing and URL building happen entirely in your browser. The input is never transmitted to any server; the WHATWG URL API runs locally in JavaScript.