URL Parser

A URL has up to nine parts: the scheme (https://), an optional username and password, the host (example.com), an optional port (:443), the path (/blog/post), an optional query string (?page=2), and an optional fragment (#section-3). Together the scheme, host, and port form the origin. This tool breaks every URL into all of these parts automatically.

A URI (Uniform Resource Identifier) is any string that identifies a resource, while a URL (Uniform Resource Locator) is a URI that also tells you how to locate it — scheme, host, and path. Every URL is a URI, but not every URI is a URL. For example, mailto:hello@example.com identifies an address (a URL), while a URN like urn:isbn:0451450523 identifies a book without a location.

The origin is the combination of the scheme, host, and port — for example https://example.com or https://api.example.com:8443. Browsers use the origin to isolate security: cookies, localStorage, and service workers are scoped per origin, and a page can only read another origin's data through explicit CORS permission. Two URLs with different origins are different security contexts.

The path (/products/shoes) identifies which resource on the server to access, while the query string (?size=42&color=red) sends parameters that modify the request — filters, pagination, search terms, or tracking IDs. The path usually maps to a file or route, while the query string is data the server uses to build a response. Both are passed to the server; only the path is required.

The fragment — also called the hash or anchor — is the part after the # character, such as #section-3. It is never sent to the server; the browser uses it to scroll to an element with that id or, in single-page apps, to drive client-side routing. Because it stays on the client, it cannot be read server-side from request logs and does not reload the page when changed.

Percent-encoding replaces characters that are not allowed in a URL — spaces, non-ASCII letters, and special symbols — with a % followed by two hex digits. For example, a space becomes %20 and a Chinese character becomes a multi-byte sequence like %E4%B8%AD. When you parse a URL, the parser decodes these back to their readable form while keeping the URL itself valid.

Every scheme has a default port — 80 for http and 443 for https — which the browser and servers assume when none is specified. This tool shows the explicit port when present and otherwise labels the implied default (80 or 443) so you can see what will actually be used. URLs like https://example.com and https://example.com:443 are functionally identical.

Yes — completely free, no registration, and 100% private. Parsing runs locally in your browser using the built-in URL API; the URL you enter is never sent to any server, stored, or logged. The tool works offline after the page loads.