Skip to content
M2TOOLKIT

Web · free tool

URL Parser

Break a URL into its parts and see every query parameter decoded.

Use it as often as you like — it's free, with no sign-up and no limits.

  • Web
  • Free
  • No sign-up
  • Runs in your browser
  • Updated

Parts

Protocol
https:
Username
user
Host name
shop.example.com
Port
8080
Path
/products/shoes
Query string
?color=blue&size=42&utm_source=newsletter
Fragment
#reviews
Origin
https://shop.example.com:8080

Query parameters (3)

NameValue (decoded)
colorblue
size42
utm_sourcenewsletter

Everything you type is processed in your browser. Nothing you enter is sent to our servers or stored by us.

How to use the URL Parser

  1. Paste a URL.
  2. Read the parts and the decoded parameters.
  3. Copy any part you need.

What does this tool do?

The parser uses your browser's standards-compliant URL engine, the same one it uses to load pages, so results match real browser behavior exactly.

Every part of a URL, explained

Take https://user@shop.example.com:8080/products/shoes?color=blue&size=42#reviews. The protocol is https:. The username is user (rare today). The host name is shop.example.com and the port is 8080; when there's no port, the default for the protocol is used (443 for https, 80 for http). The path is /products/shoes. The query string is ?color=blue&size=42, and the fragment is #reviews. The origin, https://shop.example.com:8080, is what browsers use for security rules.

Below the parts, each query parameter is listed with its decoded value, so %20 becomes a space and a + in the query becomes a space too, exactly as a web server would read it. Parameters that appear twice (?tag=a&tag=b) are listed twice, in order.

Edge cases the parser handles

Paste a link without a protocol, like example.com/page, and it's read as https://example.com/page. International domain names are shown in their Punycode form (münchen.de becomes xn--mnchen-3ya.de), which is how they actually travel over the network. Because the parser uses the browser's own URL engine, anything it rejects as invalid would also fail in a browser's address bar.

Related: UTM Builder · UTM Cleaner

Why use it?

  • Debug tracking and redirect links.
  • Inspect long URLs from emails or ads.
  • Extract parameters for spreadsheets.

Use cases

  • Debugging redirects and tracking links.
  • Reading long query strings from APIs and ad platforms.
  • Checking which domain a suspicious link really points to.
  • Teaching how URLs are built.

Parts of a URL

In https://shop.example.com:8080/products?color=blue#reviews — the protocol is https, the host shop.example.com, the port 8080, the path /products, the query color=blue and the fragment reviews.

Common mistakes

  • Trusting the text of a link instead of its host name: login.example.com.evil.net belongs to evil.net.
  • Assuming the #fragment is sent to the server. It isn't; only the browser sees it.

Privacy

Everything you type is processed in your browser. Nothing you enter is sent to our servers or stored by us. There's no account to create and nothing to install.

Frequently asked questions

Is the part after # sent to the server?

No. The fragment (after #) stays in the browser. It's used to jump to a section of the page or by single-page apps, so servers and their logs never see it.

What's the difference between the host and the origin?

The host is the domain plus any port (example.com:8080). The origin adds the protocol (https://example.com:8080). Browsers use the origin for security rules such as CORS and storage.

Content last updated . See how M2Toolkit works.

Other tools people use alongside the url parser.