URL Decoder
Decode %20 and other percent escapes back into normal characters.
Break any URL into protocol, host, path, query and fragment.
| Parameter | Decoded value |
|---|
URL Parser takes a web address and splits it into the parts a browser sees. You get the protocol, the full host including any port, the hostname on its own, the path, the raw query string, the fragment and the origin. Below that, every query parameter is listed in a table with its value already percent-decoded.
This is the fastest way to understand a long tracking link. Campaign URLs routinely carry a dozen parameters strung together, and reading them by eye is error-prone. Seeing them as rows makes it obvious which values are set, which are empty and which have been encoded twice.
Parsing uses the browser's own URL implementation, which is the same code that resolves links when you click them. That means the breakdown matches exactly how a browser would interpret the address, including its handling of default ports and internationalised domain names.
The url parser is used by writers, developers, students, marketers and anyone else who needs the job done once without installing software. Common cases include:
A browser only reports a port when the address specifies one explicitly. Standard ports, 443 for https and 80 for http, are implied rather than written, so the field stays blank.
Hostname is the domain on its own. Host is the domain plus the port when one is present. For an ordinary https address the two look identical.
Each occurrence gets its own row, in the order it appears. That matters because some systems read the first value and others read the last.
No. The part after the hash stays in the browser and is never transmitted in the request, which is why single-page applications use it for client-side state.
A relative path has no protocol or host, so it cannot be parsed on its own. Prefix it with a domain and the tool will resolve the rest.
No. It only inspects the text of the address. Nothing is requested, loaded or logged, so parsing a private or internal link is safe.
If the url parser is not quite what you need, these other free tools solve closely related problems.
Decode %20 and other percent escapes back into normal characters.
Escape spaces, symbols and non-ASCII characters for use in URLs.
Pretty-print and validate JSON, with the exact line and column of any error.
Convert a headline into a lowercase, hyphenated URL slug ready for publishing.
Decode Base64 back to text, with friendly errors for malformed input.