URL Parser

Parse any URL into its components free online. See protocol, domain, path, query parameters, and fragment broken down individually, with each parameter listed separately.

Browser only.

How to Use This Tool

Paste any URLAdd the full URL you want to break down

See it parsed instantlyEach component is identified and labeled

Review query parameters individuallyEvery key-value pair is listed separately

A URL Is Several Pieces of Information Packed Into One String

A URL like https://example.com/products/shoes?color=blue&size=42#reviews looks like a single string, but it's actually carrying distinct pieces of information: which protocol to use, which server to contact, which resource path to request, what query parameters to pass along, and which page section to jump to. Reading this at a glance gets harder as URLs accumulate more tracking parameters and configuration flags.

This parser breaks any URL into its named components and lists every query parameter individually, turning a dense string into a readable structure.

Why Query Parameters Deserve Individual Attention

Marketing links often chain together utm_source, utm_medium, utm_campaign, and several other tracking parameters into one long query string. Seeing each one labeled separately, with its decoded value, makes it immediately clear what tracking or configuration data a link is actually carrying -- useful both for debugging your own links and for understanding what data a link you've received might be transmitting.

The Fragment's Often-Overlooked Role

The portion after # never gets sent to the server at all -- it's handled entirely by the browser, traditionally for jumping to a page anchor, but increasingly used by modern JavaScript frameworks for client-side routing state. This distinction matters when debugging why server logs don't show fragment data that's clearly visible in the browser's address bar.

Frequently Asked Questions

Protocol (https://), host/domain, port (if specified), path, query string (everything after ?), and fragment (everything after #). Each serves a distinct purpose in how a browser or server interprets the address.

A URL with several tracking or configuration parameters chained together with & symbols becomes hard to read at a glance. Breaking each one into its own key-value pair makes it immediately clear what each parameter actually does, useful for debugging API calls or understanding a marketing link's tracking tags.

Everything after the # symbol, traditionally used to jump to a specific section within a page (like a heading anchor). Modern single-page applications also commonly use the fragment for client-side routing state that never gets sent to the server.

Yes, it decodes percent-encoded characters in parameter values so you see the actual intended value rather than the encoded form, which is much easier to read for debugging purposes.

Standard ports (80 for HTTP, 443 for HTTPS) are implied and don't need to be written explicitly. A URL with a non-standard port (like a local development server on :3000) needs to specify it, which this parser surfaces clearly as its own component.