URL Parser
Parse and decode any URL into its components — scheme, host, port, path, query parameters, and fragment. All processing in your browser.
Invalid URL
How to Use URL Parser
Parse any URL in three simple steps
Paste your URL
Enter any URL into the input field — full URLs with query strings work best.
Instant breakdown
The URL is parsed in real time into all its component parts.
Inspect parameters
View decoded query parameters in a table, and copy individual components.
What is a URL?
A Uniform Resource Locator (URL) is a web address that specifies the location of a resource on a computer network and the mechanism for retrieving it. URLs consist of multiple components including the protocol, domain name, port, path, query parameters, and fragment.
URL Structure
A URL is composed of several parts:
Protocol
The communication protocol (http, https, ftp, etc.)
Hostname
The domain name or IP address of the server
Port
The network port number (default: 80 for HTTP, 443 for HTTPS)
Path
The specific resource path on the server
Query String
Key-value parameters for dynamic content
Fragment
An anchor pointing to a specific part of the page
Frequently Asked Questions
The parser extracts scheme (protocol), hostname, port, path, query string parameters (as a table), fragment (hash), username, password, origin, and search string.
Yes. All URL-encoded characters (like %20, %3A) are automatically decoded in the output for readability.
The tool works best with absolute URLs (starting with http:// or https://). Relative URLs require a base URL which the browser supplies automatically.
URI is the umbrella term defined by RFC 3986: an identifier composed of scheme, path, query, and fragment. A URL is a URI that locates a resource (https://ezparser.com/url-parser), while a URN names one without a location (urn:isbn:0451450523). In everyday web work, URL is what you almost always mean.
Each byte that is not an unreserved character (A-Z, a-z, 0-9, - . _ ~) is written as % followed by two hex digits: space becomes %20, and e-acute in UTF-8 becomes %C3%A9. Reserved characters like / ? # & = carry meaning in URL structure, so they must be encoded when used as data. In query strings, older form encoders also map space to + - this tool decodes both forms.
https://user:[email protected]:8443/v2/users?page=2#results breaks into scheme (https), userinfo (user:pass@), host (api.example.com), port (8443), path (/v2/users), query (page=2), and fragment (#results). RFC 3986 section 3 defines the grammar; this parser labels every component for you.
Yes - RFC 3986 section 6 defines normalization: /a/./b resolves to /a/b, /a/../b to /b, and an empty segment // collapses to /. Browsers and HTTP clients apply this before sending a request, which is why URLs differing only in dot segments usually reach the same resource. Scheme-based normalization also lowercases the host and drops a default :443 port.
RFC 3986 sets no limit. In practice Chrome accepts about 2 MB, but most servers cap request lines near 8 KB (Apache's default LimitRequestLine is 8190 bytes), and APIs like Twitter/X document 2048-character limits. Keeping URLs under 2000 characters is the conventional safe zone for sharing and SEO.
Related Tools
Base64 URL Decoder Parser
Decode and encode Base64, parse URL-encoded strings, preview Base64 images, and decode JWT header or payload segments
HTML Entity Decoder
Encode and decode HTML entities — convert between special characters and entity references
Hex Decoder
Convert between hexadecimal and text — supports configurable delimiter and prefix options
Authoritative References
Primary sources behind this tool - official standards and specifications, not secondhand summaries.
RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax
The IETF standard defining URI generic syntax: scheme, authority, path, query.
WHATWG - URL Standard
The WHATWG URL Standard that browsers implement — the living specification of URL parsing.
MDN Web Docs - URL API
Mozilla reference for the URL API and URLSearchParams in the browser.
URL - Wikipedia
URL structure and the history from URIs to everyday web addresses.