Developer tools
URL parser
Paste any URL to split it into its scheme, host, port, path, query parameters, and fragment, all decoded and easy to read. Everything runs in your browser - nothing is uploaded.
Components
Query parameters
How it works
Paste a URL and see it broken into its parts: the scheme (such as https), the host name and port, the path, every query parameter, and the fragment after the hash. The query string is split into a readable table of name and value pairs with the percent-encoding decoded, so a parameter like name=Ada%20Lovelace shows as the plain text it represents instead of the escaped form.
The parsing uses the browser native URL API, the same engine that powers the address bar, so it follows the real rules for what is a host, what is a path, and how query strings are structured rather than guessing with a regular expression. An invalid URL is flagged clearly instead of producing wrong parts. Everything runs in your browser, so nothing you paste is uploaded.
Example. Paste https://user@example.com:8080/path/to/page?q=hello+world&lang=en#section and the tool lists the scheme https, the host example.com, the port 8080, the path /path/to/page, two query parameters (q = "hello world" and lang = "en"), and the fragment section, each decoded and ready to read.
FAQ
What parts of a URL does it show?
It splits a URL into the scheme (protocol), any user info, the host name, the port, the path, the query string, and the fragment. The query string is further broken into individual parameters as name and value pairs. Each part is decoded so you read the real values rather than the percent-encoded form.
Are the query parameters decoded?
Yes. Each parameter value is percent-decoded, so %20 and a plus sign both become a space and an encoded character like %C3%A9 becomes its accented letter. That lets you read exactly what a parameter carries. The tool lists every parameter separately, including repeated keys, which some URLs use to pass a list of values.
Why does my URL show as invalid?
The parser uses the browser native URL engine, which requires a valid absolute URL with a scheme, such as https:// at the front. A bare host like example.com/path with no scheme, or a string with illegal characters in the host, is rejected rather than parsed into misleading parts. Add the scheme and it will parse.
Is my URL sent anywhere?
No. Parsing happens entirely in your browser with the built-in URL API. Nothing you paste is uploaded, logged, or stored, so it is safe to inspect URLs that contain tokens or other private query parameters.