URL Parser
This free URL parser takes an address apart and shows every component on its own line: the protocol, the host, the explicit port (or the note that the default applies), the path, the query string and the hash fragment — plus the query parameters decoded into a readable key-value table.
How to use
- Paste a full absolute URL, scheme included, into the input below.
- Each component — protocol, host, port, path, query, hash — appears on its own line instantly.
- Read the decoded query parameters in the key-value list; copy nothing anywhere — your input never leaves the page.
Frequently asked questions
Is my URL fetched or visited?
No. Parsing happens entirely in your browser with the built-in URL implementation — no HTTP request is made to the address, so internal hostnames, tokens in query strings and localhost URLs are all safe to inspect.
Why does my URL need a scheme (https://)?
The parser resolves absolute URLs only. example.com/path without a scheme is ambiguous — is it a host, a path, or something else? — and rather than guess, the tool reports a clear error. Add the scheme and it parses.
What does an empty port mean?
When the URL omits the port (or uses the scheme default, like 443 for https), the port line shows "(default)". An explicit port such as :8443 is displayed as the number itself. Both forms describe the same fully qualified address.
Are query parameter values decoded?
Yes. The parameter table shows the decoded values: %20 appears as a space and %E4%BD%A0%E5%A5%BD as 你好, matching what server-side code sees after standard query parsing. The raw search line above it keeps the original encoding for reference.
Related tools
About this tool
This free URL parser takes an address apart and shows every component on its own line: the protocol, the host, the explicit port (or the note that the default applies), the path, the query string and the hash fragment — plus the query parameters decoded into a readable key-value table. Debugging a routing rule, a redirect, an analytics tag or an API call usually comes down to one question: what exactly is in this URL? Reading it out of a log line or an encoded redirect target by eye invites mistakes, because %-encoding hides what the server actually receives; the parser uses the same WHATWG URL implementation browsers themselves use, so what you see is what the runtime sees. Values like %20 arrive already decoded in the parameter table. Relative strings and other malformed input fail fast with a clear error instead of a guessed result — a URL without a scheme has no unambiguous meaning. Everything is parsed locally in your browser: no request is ever made to the address you paste, and nothing is stored. Paste a URL below to take it apart.