URL Parser
Break any URL into protocol, hostname, path, query params, hash, and origin.
Understanding a URL's structure is essential for debugging links, building API integrations, and analysing web traffic. This parser breaks any URL into its constituent parts — protocol, hostname, port, path, query parameters, and fragment — making it easy to inspect and modify individual components.
Paste a URL to inspect its parts.
How to Parse a URL
- Enter a URL — paste any URL you want to analyse.
- Click Parse — the tool breaks it down into all its constituent parts.
- Review components — see the protocol, hostname, port, path, query parameters, and fragment.
Frequently Asked Questions
What are the components of a URL? ▼
A URL (Uniform Resource Locator) consists of: protocol (https://), hostname (www.example.com), port (:443), path (/blog/article), query string (?page=2&sort=date), and fragment (#section). Not all parts are required — at minimum, a URL needs a protocol and hostname.
What is the difference between URL and URI? ▼
A URL (Uniform Resource Locator) is a specific type of URI (Uniform Resource Identifier) that includes the access mechanism (protocol). All URLs are URIs, but not all URIs are URLs. In practice, the terms are often used interchangeably in web development.
What is the fragment (hash) in a URL? ▼
The fragment starts with # and identifies a specific section within a page (e.g., #introduction). Fragments are not sent to the server — they are processed client-side by the browser. Single-page applications use fragments for routing (e.g., #/dashboard).
What is the difference between path and query string? ▼
The path identifies a resource (e.g., /products/shoes) and is part of the URL structure. The query string (after ?) passes parameters to that resource (?color=red&size=10). Paths are hierarchical; query strings are key-value pairs for filtering or configuration.
Why would I need to parse URLs? ▼
Common use cases: debugging API endpoints, understanding redirect chains, analysing tracking parameters, building URL manipulation utilities, extracting domains from link lists, and reverse engineering third-party integrations.
Is my data stored? ▼
No. All parsing happens in your browser. No URL data is sent to any server.