Skip to content

URL Parser

Break a URL down into its protocol, host, path, query parameters, and hash - useful for understanding or debugging any link.

Category: text
Use Case: Debugging a Redirect or Tracking URL, Understanding Query String Parameters, Learning URL Structure
Privacy: 100% browser-based

Recommended Settings

Pro Tips

  • A full URL needs a protocol (like https://) to be recognized - bare domains like 'example.com' will show an error
  • Query parameters are automatically decoded, so %20 shows as a space and other percent-encoded characters are readable
  • The origin (protocol + host + port) is useful for checking CORS or same-origin policy questions
  • Repeated query parameters with the same name are listed separately in the parameters table

Most Popular

Most users paste a tracking or redirect URL to see exactly what parameters it's passing

When to Use This Tool

Debugging a Redirect or Tracking URL

Break down a long URL to understand what it actually does and where it leads.

Understanding Query String Parameters

See every parameter and value encoded in a URL's query string.

Learning URL Structure

Study how a URL is broken into protocol, host, path, and query components.

Cleaning Up Shared Links

Identify tracking parameters in a URL before sharing a cleaner version.

How It Works

1

Parse the URL using the browser's native URL API

2

Break it into its protocol, host, port, path, query string, and hash components

3

Decode and list each individual query parameter and its value

100% Private

Files never leave your device. All processing happens locally in your browser.

Lightning Fast

Powered by Browser native URL API for optimal performance on modern browsers.

Open Source

Built with verified, open-source libraries. Fully transparent.

Frequently Asked Questions

Why does my URL show an error?

The URL needs a full protocol prefix, like https:// or http://, to be recognized. A bare domain like 'example.com' without the protocol won't parse correctly.

Are query parameters automatically decoded?

Yes, percent-encoded characters (like %20 for a space) are automatically decoded in the parameters table for readability.

Can this parse URLs with unusual protocols like ftp:// or mailto:?

Yes, any URL scheme supported by the browser's native URL parser will work, though host and path fields may be empty for schemes like mailto: that don't use them.

Is my data sent to a server?

No. Parsing happens entirely in your browser using its built-in URL parser.

What does 'origin' mean?

It's the combination of protocol, host, and port that defines a single origin - commonly relevant when discussing CORS or same-origin security policies.