Is the URL sent anywhere?

No. Parsing uses the browser's built-in URL API locally. Nothing is transmitted or stored.

Why does it add https:// to my input?

A bare domain like example.com/page is not a complete URL. Rather than reject it, https is assumed, since that is what a browser would do.

Why are some values still percent-encoded?

Because they are doubly encoded — common in redirect parameters that themselves contain a URL. Paste that inner value back in to decode the next layer.

URL Parser

Runs in your browser

Break a URL into protocol, host, port, path, fragment and every query parameter — decoded and listed. Runs in your browser.

URL

Protocol: https
Hostname: snaptools.in
Port: (default)
Path: /pdf-compressor
Fragment: faq
Username: (none)

Query parameters (2)

utm_sourcenewsletter
utm_mediumemail

About this tool

Long URLs hide their structure. A tracking link with a dozen UTM parameters, an OAuth redirect carrying encoded state, or an API call with nested filters are all hard to read as one string and easy to read as a table. This parser uses the browser's own URL implementation — the same one that will handle the link in production — and decodes each query parameter so percent-encoded values are shown as their real content.

How to use

Paste a URL. A bare domain works too; https is assumed.
Read the component table and the decoded query parameters.

When to use this tool

Reading the UTM parameters on a campaign link.
Debugging an OAuth redirect and its state parameter.
Checking which query parameters an API call is really sending.
Confirming a redirect target is encoded correctly.

Tips

Query values are shown decoded; use the URL Encoder if you need to re-encode one.
Repeated parameters are listed separately rather than collapsed, because servers treat them differently.
The fragment after # is never sent to the server — it exists only in the browser.

FAQ

Is the URL sent anywhere?: No. Parsing uses the browser's built-in URL API locally. Nothing is transmitted or stored.
Why does it add https:// to my input?: A bare domain like example.com/page is not a complete URL. Rather than reject it, https is assumed, since that is what a browser would do.
Why are some values still percent-encoded?: Because they are doubly encoded — common in redirect parameters that themselves contain a URL. Paste that inner value back in to decode the next layer.