ToolVaults

URL Parser & Analyzer

Break any URL into its protocol, host, port, path, query parameters, and hash. Uses the browser's native URL parser for spec accuracy.

Runs 100% in your browser — nothing is uploaded.
  • Protocolhttps:
  • Usernameuser
  • Passwordpass
  • Hosttoolvaults.net
  • Hostnametoolvaults.net
  • Pathname/text-tools/case-converter/
  • Search?in=hello+world&to=camel
  • Hash#result
  • Originhttps://toolvaults.net
Query parameters
KeyValue
inhello world
tocamel

How to use

  1. 1
    Paste a URL

    Any absolute URL — http/https, mailto, tel, ws, ftp, whatever the browser understands.

  2. 2
    Read every component

    Protocol, host, port, path, query params (decoded), and hash — all broken out into their own rows.

  3. 3
    Copy the piece you need

    Each component has its own copy button. Great for pulling one query parameter out of a long tracking URL.

Examples

A tracking URL
Input
https://example.com/products/shoe-42?utm_source=twitter&utm_campaign=fall_sale&size=10#reviews
Output
protocol: https · host: example.com · path: /products/shoe-42 · query: {utm_source: twitter, utm_campaign: fall_sale, size: 10} · hash: reviews
Every UTM parameter broken out separately. Copy the ones you need.
A URL with encoded query
Input
https://api.example.com/search?q=hello%20world&filter=active%2Bnew
Output
query: {q: "hello world", filter: "active+new"}
Percent-encoding decoded automatically. Both the raw and decoded forms are shown.
A URL with non-standard port
Input
https://dev.example.com:8443/api/v2/users/42
Output
protocol: https · host: dev.example.com · port: 8443 · path: /api/v2/users/42
The port is broken out separately from the host — useful for debugging local dev.

Frequently asked

What parser does this use?

The browser's native URL constructor — WHATWG URL spec compliant. Same code path that fetch(), XHR, and navigation use.

Does it decode query values?

Yes — query params are shown decoded. The raw search string with encoding is also visible.

Related tools