URL Parser

What normalizing changes

The browser's URL standard lowercases the scheme and host, converts international domain names to their xn-- Punycode form, drops a port that matches the default, resolves . and .. segments in the path, and percent-encodes spaces and other characters that URLs cannot contain. Two URLs that normalize to the same text are the same address, which makes the normalized form the one to compare.

Parts the server never sees

The fragment after # stays in the browser; it is not sent with the request, so servers, logs, and redirects cannot read it. Single-page apps use it for routing, and some sign-in flows put tokens there for that reason.

In a query string + means a space only in form-encoded data, while in a path it is a literal plus sign. When a value contains &, =, or # and splits in unexpected places, it was not encoded before being added; the URL encoder fixes the value.

How to use it

1. Paste a URL or hostname.
2. Choose Parse URL.
3. Inspect each decoded component and copy the normalized URL.

Privacy & limitations

Parsing runs entirely in your browser and the URL is never requested. Credential-bearing URLs are flagged; avoid sharing URLs that contain usernames, passwords, or sensitive query values.