URL Parser
NewParse any URL into its components: protocol, host, path, query params, and hash.
Query parameters
Supports absolute, relative, data:, and blob:| Key | Value | Action |
|---|
Frequently Asked Questions
What kinds of URLs can this parser handle?
It handles normal absolute URLs, relative paths, protocol-relative URLs that start with //, and special data: and blob: URLs. The kind label updates based on which branch of the parser matched your input.
Why do spaces in query parameters come back as + instead of %20?
For query keys and values, the tool uses encodeURIComponent and then replaces %20 with +. The path is encoded separately with encodeURI, so space handling is different there.
Can I edit the query string without rewriting the whole URL?
Yes. Parsed query parameters are shown as editable rows, and you can add or remove rows before reconstructing the URL.
Why don't I see username and password fields for URLs that include them?
Because this parser only exposes protocol, host, port, path, fragment, and query params. It does not surface auth credentials as separate editable fields.
What does the Show decoded values toggle actually change?
It changes how fields and query rows are displayed while editing. With decoding on, you see readable characters; with it off, paths are shown with encodeURI and query parts with application/x-www-form-urlencoded-style encoding.