Back to All Tools

Free Online URL Parser & Builder

Instantly break any URL into its component parts — protocol, hostname, port, pathname, query parameters, and fragment. Or construct a URL from scratch using the builder.

Press Cmd/Ctrl + Enter to parse

What is URL Parsing?

URL parsing is the process of decomposing a Uniform Resource Locator (URL) into its constituent parts. A well-formed URL follows the structure defined in RFC 3986 and the WHATWG URL Standard.

Anatomy of a URL

Consider the following example URL:

https://user:pass@api.example.com:8080/v1/search?q=hello&lang=en#results

Each part has a specific role:

PartValueDescription
Protocolhttps:Communication protocol (http, https, ftp, etc.)
UsernameuserOptional auth username before the @
PasswordpassOptional auth password (rarely used in modern URLs)
Hostnameapi.example.comDomain name or IP address
Port8080Network port (omitted if default: 80 for http, 443 for https)
Pathname/v1/searchThe hierarchical path to the resource
Search?q=hello&lang=enQuery string with key-value parameters
Hash#resultsFragment identifier (scroll anchor, client-side routing)

How to Use the URL Parser

  1. Paste any URL into the input field (the https:// prefix is added automatically if omitted).
  2. Click Parse or press Cmd / Ctrl + Enter.
  3. All URL components are displayed in a structured table. Query parameters are listed individually with individual copy buttons.

How to Use the URL Builder

  1. Switch to the Build URL tab.
  2. Fill in the hostname and any other parts you need.
  3. Add query parameters with the + Add button — each parameter is automatically URL-encoded.
  4. Click Build URL to generate the complete URL and copy it.

Frequently Asked Questions

What is a query string?

A query string is the part of the URL that comes after the ?. It contains one or more key-value pairs separated by & (e.g., ?page=2&sort=asc). Query strings are commonly used to pass parameters to web servers or client-side applications.

What does the # (hash) part of a URL do?

The fragment (hash) is never sent to the server — it is processed entirely by the browser. It is used for in-page anchor links (jump to a section) or client-side routing in Single Page Applications (SPAs) built with frameworks like React or Vue.

Is my data private?

Yes. All URL parsing and building happens entirely in your browser using the standard Web URL API. No data is ever sent to a server.