URL Parser

Break down any URL into protocol, host, path, query params and hash

What is it and how does it work?

A URL parser breaks a web address into its parts so you can see exactly how it is built: the protocol (https), the host (example.com), the port, the path (/products/shoes), the query string (?color=red&size=10) and the fragment (#reviews). A URL looks like one continuous string, but each section has a defined role, and bugs often hide in the boundaries between them — a parameter in the wrong place, an encoded character, or a fragment mistaken for part of the path. Splitting it apart turns a dense link into a labelled structure you can read at a glance.

The most useful part for everyday work is the query string, which the parser separates into individual key–value pairs and decodes for you, so a long tracking URL with a dozen parameters becomes a clean list. This is invaluable for debugging redirects, reading UTM campaign tags, checking what an API call actually sent, or confirming that a value was encoded correctly. This tool parses the URL in your browser, so even links containing tokens or private parameters stay on your device.

Common use cases

• Reading query parameters: split a long URL into its individual key–value pairs to see exactly what each parameter is set to.
• Debugging a redirect: inspect protocol, host and path to understand where a link actually points and how it is constructed.
• Checking UTM tags: pull apart a campaign URL to verify the utm_source, utm_medium and utm_campaign values are correct.

Frequently asked questions

What is the difference between the query string and the fragment?

The query string (after ?) is sent to the server and typically carries parameters the page or API uses. The fragment (after #) stays in the browser and is not sent to the server — it usually points to a section of the page or is used by client-side apps.

Why are some characters in the URL shown as %20 or %2F?

Those are percent-encoded characters: spaces, slashes and other reserved symbols are encoded so they travel safely inside a URL. The parser decodes them so you can read the real value, while showing you where encoding was used.

What counts as the origin of a URL?

The origin is the protocol, host and port together (for example https://example.com). It is the part browsers use for security boundaries like the same-origin policy, separate from the path and parameters that identify a specific resource.

Can it parse relative URLs?

Relative URLs (like /page?x=1) have no protocol or host, so only the path, query and fragment are present. The parser still breaks out those components; resolving a relative URL to an absolute one requires a base URL to combine it with.

Developer

UUID Generator · Timestamp Converter · Base64 Encoder · Base64 Decoder · Hash Generator · Color Converter