Break any link into its protocol, host, port, path, hash and each query parameter, decoded and listed one per row.
Runs in your browser — nothing is uploaded
A URL has several parts, and a small mistake in one of them sends people to the wrong place. Seeing the protocol, host, port, path, query and fragment on separate lines makes it easy to spot a typo, a missing scheme, or an unexpected port.
Query parameters are decoded for display, so percent-encoded spaces and symbols appear as they were meant. Duplicate keys each get their own row, which helps when a tracking or filter parameter is repeated by mistake.
A URI is the general identifier format, and a URL is a URI that also says how to locate a resource, such as https://. In everyday use the terms are interchangeable, and this parser accepts either as long as it has a scheme.
Characters such as spaces, ampersands and non-English letters are percent-encoded in URLs, for example %20 for a space. The parser decodes them for display, but the original link still needs the encoded form.
The URL standard requires a scheme so the parser knows how to interpret the rest. Without it, text like example.com is treated as a relative path and cannot be split into a host.
No. It only reads the text you paste. It does not connect to the site, so private or internal addresses are never contacted.
The hash, or fragment, is the part after #. Browsers do not send it to the server, and it is often used to jump to a section or to pass client-side state.
No. The link is parsed in your browser and nothing is saved or sent.