URL Parser
Break a URL into scheme, host, port, path, query parameters and fragment, with IDN support and an editor that rebuilds the URL.
How to use
- Paste a URL into the input, or click “Example” to try it. Every part is listed below as you type.
- Internationalized domains are shown in both Unicode and Punycode (xn--). Path segments, query parameters and the fragment are shown decoded.
- Edit, add or remove entries under “Query parameters” and the URL above updates to match.
- Passwords in the URL are hidden unless you check “Show password”.
- Click “Copy” to grab the full normalized URL.
FAQ
Is my URL uploaded?
No. Parsing uses the browser’s built-in URL support and runs entirely on your device; the URL is not saved in browser storage either. URLs often carry tokens or passwords, so check before you share one.
Why does the result differ from what I typed?
Browsers normalize URLs: the scheme and host become lowercase, default ports (443 for https, 80 for http) are dropped, an empty path becomes /, internationalized domains turn into Punycode, and characters such as spaces are percent-encoded. This tool shows the URL exactly as the browser uses it.
What is Punycode?
The domain name system only supports ASCII letters, digits and hyphens, so a domain such as 例子.台灣 is sent as Punycode starting with xn--, here xn--fsqu00a.xn--kpry57d. Both forms point to the same site.
Why does it say the scheme is missing?
A complete URL starts with a scheme such as https://. With just example.com the browser cannot tell which scheme to use, so this tool suggests adding https:// with one click. Input like localhost:3000 is read as the scheme “localhost”, and you get the same hint.
Why do spaces become + after editing parameters?
When the URL is rebuilt, parameters are encoded as HTML form data (application/x-www-form-urlencoded): spaces become + and Chinese text becomes escapes such as %E5%8F%B0. That is the standard URLSearchParams behavior, and servers decode it correctly.