Parse and decode any URL into its components — protocol, host, path, query parameters, fragment and port. Build and encode URLs from individual parts.
Paste any full URL — including complex URLs with query strings, fragments, auth credentials and encoded characters.
Each component is displayed separately: protocol, hostname, port, path, query parameters as a key-value table, and fragment.
Switch to Builder mode to construct a URL from scratch — add components individually and copy the encoded result.
The parser breaks a URL into all standard RFC 3986 components: scheme/protocol, username and password (if present), hostname, port number, pathname, query string, individual query parameters as a key-value table, and the fragment/hash. Percent-encoded characters are decoded and displayed alongside the raw encoded value.
URL encoding converts special characters to % followed by two hex digits — spaces become %20, ampersands become %26. Paste the URL and the decoded value is shown alongside the raw encoded form for each component. The Query Parameters table decodes both keys and values, making complex query strings from tracking URLs or API calls easy to read.
Yes — the Query Parameters table shows each key-value pair as an editable row. Add new parameters, edit values inline or delete parameters. As you change values the full URL in the builder updates automatically. Copy the updated URL with all parameter changes applied.
Builder mode lets you construct a URL from scratch by filling in individual fields: protocol, hostname, port, path and query parameters via a table. The tool assembles these in the correct order, properly percent-encodes special characters, and displays the final assembled URL for copying.
The parser validates URLs against the WHATWG URL Standard used by browsers. If valid all components display correctly. If invalid an error explains the issue — missing scheme, invalid hostname, illegal characters or malformed port. Common issues include missing protocol, spaces in URLs and double slashes in paths.
Yes — mailto URLs are parsed to show the email address and query parameters (subject, body, cc, bcc). Data URLs are parsed to show the MIME type, encoding and data payload. File URLs extract the local file path. FTP URLs extract credentials, host and path.
In https://example.com/products?color=red#reviews: the path /products identifies the resource on the server, the query string color=red passes parameters to the server in the HTTP request, and the fragment reviews is processed only by the browser — it is never sent to the server and is used to scroll to page elements or by SPA routers.
Yes — the Compare tab shows two URL inputs side by side. The tool parses both and highlights differences in each component: which path segments changed, which parameters were added or removed, and whether protocol, host or port differs. Useful for debugging redirect chains and comparing staging vs production URLs.
Yes — UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) appear in the parsed parameters table with decoded values. Verify all five parameters are present and correctly spelled, check encoding errors, add missing parameters in Builder mode and copy the corrected URL.
No — URL parsing uses the native WHATWG URL API built into all modern browsers (the URL() constructor). No URL is sent to any external server. This is important when URLs contain sensitive information — API keys as query parameters, authentication tokens and internal addresses are parsed locally and privately.
