URL Splitter

Parse URLs into their individual components

URL Splitter

This simple free tool helps you parse an URL into its individual components, like schema, protocol, username, password, hostname, port, domain, subdomain, tld, path, query string, hash and more. It further splits the query string into human readable format and takes care of decoding the parameters.

Enter a URL to see its components

How to use the URL Splitter

  1. •Paste a URL into the input field. It can be any URL: web addresses, API endpoints, deep links, or even data URIs.
  2. •View the parsed components that appear instantly below the input. Each component (protocol, hostname, port, path, query parameters, hash) is displayed separately.
  3. •Inspect query parameters which are broken out into individual key-value pairs in a readable table format, with URL-decoded values.
  4. •Edit components individually if you want to experiment with constructing or modifying a URL by changing specific parts.
  5. •Copy any component or the full reconstructed URL to your clipboard.

What is a URL?

A URL (Uniform Resource Locator) is a reference to a web resource that specifies its location on a network and the mechanism for retrieving it. URLs are defined by RFC 3986 and are the fundamental addressing system of the web. Every link you click, every API you call, and every resource your browser loads is identified by a URL.

A URL has several components:

  • •Scheme/Protocol (https:): Identifies the protocol used to access the resource. Common schemes include http, https, ftp, mailto, and file.
  • •Authority (//user:password@hostname:port): Contains optional authentication info, the hostname (domain or IP address), and an optional port number.
  • •Hostname (www.example.com): The domain name or IP address of the server. Can be further broken down into subdomain (www), domain (example), and TLD (com).
  • •Port (:8080): The network port. Defaults to 80 for HTTP, 443 for HTTPS.
  • •Path (/api/v2/users): Identifies the specific resource on the server. Path segments are separated by forward slashes.
  • •Query string (?key=value&other=123): Contains key-value parameters separated by &. Values are URL-encoded.
  • •Fragment/Hash (#section): Identifies a secondary resource or location within the primary resource. The fragment is not sent to the server.

Understanding URL structure is essential for web development. Query parameters control filtering, pagination, and search in APIs. Path segments define resource hierarchies. Fragments enable deep linking within single-page applications. Correctly encoding special characters in URLs prevents bugs and security issues.

Common use cases

  • •Debugging API endpoints: When an API call fails, splitting the URL reveals whether query parameters are correctly formatted, encoded, and complete.
  • •Analyzing tracking URLs: Marketing URLs often have complex query strings with UTM parameters, redirect chains, and tracking tokens. Splitting the URL makes these readable.
  • •Understanding redirect URLs: OAuth and SSO flows use URLs with many parameters (redirect_uri, state, code). Parsing them helps debug authentication issues.
  • •Teaching and learning: URL structure is a fundamental web concept. The visual breakdown helps students and junior developers understand how URLs work.

FAQ

What is URL encoding? URL encoding (percent-encoding) replaces unsafe characters with a % followed by two hex digits representing the character's ASCII value. For example, a space becomes %20 and an ampersand becomes %26. This tool automatically decodes these for readability.

What is the difference between the path and the query string? The path (/users/123) identifies the resource hierarchically. The query string (?sort=name&limit=10) provides additional parameters that modify the request. Think of the path as "what" you are requesting and the query as "how" you want it.

Is the fragment sent to the server? No. The fragment (everything after #) is processed entirely by the client (browser). It is never included in HTTP requests to the server. This is why single-page applications use fragment-based routing for client-side navigation.

Is my data safe?

Yes. This tool runs entirely in your browser. Your data is never sent to our servers. URL parsing uses the browser's native URL API, and all processing happens locally on your device.

How to use the URL Splitter

  1. Paste a URL into the input field. It can be any URL: web addresses, API endpoints, deep links, or even data URIs.
  2. View the parsed components that appear instantly below the input. Each component (protocol, hostname, port, path, query parameters, hash) is displayed separately.
  3. Inspect query parameters which are broken out into individual key-value pairs in a readable table format, with URL-decoded values.
  4. Edit components individually if you want to experiment with constructing or modifying a URL by changing specific parts.
  5. Copy any component or the full reconstructed URL to your clipboard.

What is a URL?

A URL (Uniform Resource Locator) is a reference to a web resource that specifies its location on a network and the mechanism for retrieving it. URLs are defined by RFC 3986 and are the fundamental addressing system of the web. Every link you click, every API you call, and every resource your browser loads is identified by a URL.

A URL has several components:

  • Scheme/Protocol (https:): Identifies the protocol used to access the resource. Common schemes include http, https, ftp, mailto, and file.
  • Authority (//user:password@hostname:port): Contains optional authentication info, the hostname (domain or IP address), and an optional port number.
  • Hostname (www.example.com): The domain name or IP address of the server. Can be further broken down into subdomain (www), domain (example), and TLD (com).
  • Port (:8080): The network port. Defaults to 80 for HTTP, 443 for HTTPS.
  • Path (/api/v2/users): Identifies the specific resource on the server. Path segments are separated by forward slashes.
  • Query string (?key=value&other=123): Contains key-value parameters separated by &. Values are URL-encoded.
  • Fragment/Hash (#section): Identifies a secondary resource or location within the primary resource. The fragment is not sent to the server.

Understanding URL structure is essential for web development. Query parameters control filtering, pagination, and search in APIs. Path segments define resource hierarchies. Fragments enable deep linking within single-page applications. Correctly encoding special characters in URLs prevents bugs and security issues.

Common use cases

  • Debugging API endpoints: When an API call fails, splitting the URL reveals whether query parameters are correctly formatted, encoded, and complete.
  • Analyzing tracking URLs: Marketing URLs often have complex query strings with UTM parameters, redirect chains, and tracking tokens. Splitting the URL makes these readable.
  • Understanding redirect URLs: OAuth and SSO flows use URLs with many parameters (redirect_uri, state, code). Parsing them helps debug authentication issues.
  • Teaching and learning: URL structure is a fundamental web concept. The visual breakdown helps students and junior developers understand how URLs work.

FAQ

What is URL encoding? URL encoding (percent-encoding) replaces unsafe characters with a % followed by two hex digits representing the character's ASCII value. For example, a space becomes %20 and an ampersand becomes %26. This tool automatically decodes these for readability.

What is the difference between the path and the query string? The path (/users/123) identifies the resource hierarchically. The query string (?sort=name&limit=10) provides additional parameters that modify the request. Think of the path as "what" you are requesting and the query as "how" you want it.

Is the fragment sent to the server? No. The fragment (everything after #) is processed entirely by the client (browser). It is never included in HTTP requests to the server. This is why single-page applications use fragment-based routing for client-side navigation.

Is my data safe?

Yes. This tool runs entirely in your browser. Your data is never sent to our servers. URL parsing uses the browser's native URL API, and all processing happens locally on your device.