100% client-side, nothing ever leaves your browser
Parse a URL
Break any URL down into its protocol, host, port, path, query parameters, and fragment — instantly, using your browser's native URL parser.
Parsed components
Query parameters
| Key | Value (decoded) |
|---|
This URL has no query parameters.
How URL parsing works
The browser's native URL and URLSearchParams APIs break your URL into its component parts, exactly as the browser itself interprets it.
Paste a URL
Paste any complete, absolute URL including its protocol.
Automatic parsing
Every component is extracted immediately, and query parameters are decoded and listed individually.
Copy what you need
Copy any individual value, or copy the entire parsed result as JSON.
Privacy note: parsing happens entirely in your browser using native JavaScript APIs. The URL you enter is never sent to a server.
Common uses
Debugging redirect chains
Break down a long redirect or tracking URL to see exactly what parameters it's carrying.
Inspecting UTM parameters
Quickly read utm_source, utm_medium, and other campaign parameters out of a marketing link.
Understanding API endpoints
See the host, path, and query parameters of an API URL at a glance while debugging requests.
Extracting a single value
Pull one specific query parameter's decoded value out of a long, hard-to-read URL.
Frequently asked questions
Why do I need to include the protocol in the URL?
The browser's URL parsing API requires a complete, absolute URL to determine components reliably. Add https:// or http:// (or another scheme) to the front of the address if it's missing.
How are repeated query parameters handled?
If the same parameter name appears more than once in the query string, each occurrence is listed as its own row in the query parameters table, in the order it appears in the URL.
Are query parameter values decoded automatically?
Yes. Percent-encoded characters in query values, such as %20 for a space, are decoded automatically so you see the actual intended value rather than the raw encoded text.
What is the difference between origin and hostname?
The hostname is just the domain, like example.com. The origin combines the protocol, hostname, and port into the base identity of the URL, such as https://example.com:8080.
Is my URL sent anywhere?
No. Parsing happens entirely in your browser using the native URL and URLSearchParams APIs. Nothing is sent to a server.
Why does parsing fail for my URL?
The most common reason is a missing protocol or an unescaped invalid character. Check that the URL starts with a scheme like https:// and doesn't contain raw spaces or unencoded special characters.
More tools
Additional utilities from the same toolkit.