🧑‍💻

URL Parser

🔒 In your browser

Break a URL into host, path, query params & hash.

How it works

Paste any URL and it's split into its parts, with query parameters decoded into a table — handy when debugging a link, a redirect, or a tracking URL.

https://host:port/path?query#hash

Try an example

Protocolhttps
Hostshop.example.com
Port8443
Path/products/shoes
Queryq=blue%20suede&page=2&sort=price
Fragmentreviews
Originhttps://shop.example.com:8443

Query parameters (3)

KeyValue (decoded)
qblue suede
page2
sortprice

About the URL Parser

A URL packs a lot into one string — protocol, host, port, path, query parameters and hash. This free URL parser breaks any URL into those parts, decodes each query parameter, and lays them out clearly, which is perfect for debugging links, redirects and UTM tracking.

Parsing happens in your browser; nothing is uploaded.

How to parse a URL

  • Paste any URL.
  • See the protocol, host, port, path, query parameters and fragment separated out.
  • Query values are URL-decoded so you can read them directly.

What each part of a URL means

  • Protocol — https or http, how the browser connects.
  • Host and port — the server (port is usually implied).
  • Path — which resource on the server.
  • Query string — parameters after the ?, like search terms and UTM tags.
  • Fragment — the part after #, handled by the browser, never sent to the server.

Frequently asked questions

What does a URL parser show?

It splits a URL into its components — scheme/protocol, hostname, port, path, each query parameter and the hash fragment — with values decoded for readability.

Can I use it to read UTM parameters?

Yes. Marketing parameters like utm_source and utm_campaign appear as individual, decoded query parameters.

Is my URL uploaded?

No. The URL is parsed locally in your browser.

What's the difference between the query and the fragment?

The query string (after ?) is sent to the server and typically drives what content is returned. The fragment (after #) stays in the browser — it's used for in-page anchors and client-side routing and is never sent in the request.

Related searches

url parserparse url onlineurl inspectorquery parametersutm parseranalyze urlurl breakdown

Related Developer tools

🔗 Embed this tool on your website — free

Copy this and paste it into your page's HTML. The tool runs in the visitor's browser, just like here. Change height to fit, or add the optional auto-resize snippet below. Add ?theme=dark to the URL for dark mode.

<iframe src="https://toolhq.dev/embed/url-parser/" title="URL Parser — ToolsHub" width="100%" height="520" style="border:1px solid #e5e7eb;border-radius:12px;max-width:680px" loading="lazy"></iframe>
Optional: auto-resize the iframe height

Add this once on the same page so the iframe grows to fit the tool:

<script>
addEventListener("message", function (e) {
  if (e.data && e.data.type === "toolshub:resize") {
    document.querySelectorAll('iframe[src*="/embed/"]').forEach(function (f) {
      if (f.contentWindow === e.source) f.style.height = e.data.height + "px";
    });
  }
});
</script>