How to use this tool
- Paste a complete HTTP(S) URL or select query-string mode.
- Choose whether a plus sign should decode as a form-space.
- Parse and inspect the component summary and parameter table.
How the operation works
Complete URLs are parsed with the browser’s URL implementation. Query parameters are retained as ordered pairs rather than collapsed into an object. Values are percent-decoded once with strict UTF-8 handling. Embedded credentials are reported as present but are redacted in the output. The destination is not fetched.
What the parser extracts
Complete HTTP(S) URLs are split into scheme, host, port, path, search and fragment using the browser’s URL implementation. Query parameters stay as an ordered list of pairs rather than a collapsed object, so tag=a&tag=b shows two entries. Values are percent-decoded once with strict UTF-8 handling.
Embedded credentials (user:pass@) are reported as present but redacted in the output. The destination is never fetched. Query-string mode parses a bare ?a=1&b=2 or a=1&b=2 fragment without requiring a full address.
Plus signs and form-style spaces
In form-style query decoding, + means space and %2B means a literal plus. In component mode, an unescaped + stays a plus. Select the mode used by the source system—guessing wrong changes search terms and names without producing a syntax error.
?q=green+tea form mode → q = “green tea” ?x=a+b component → x = “a+b”
Example parse
https://user:secret@example.com:8443/search?q=green+tea&tag=a&tag=b#results
Reported: scheme https, host example.com, port 8443, path /search, fragment results. Credentials flagged and redacted. Query table: q → green tea (form mode), tag → a, tag → b. Two tag pairs remain separate.
This structure is useful before cleaning tracking fields (URL Cleaner) or building a campaign link (UTM Builder).
What parsing does not do
Parsing does not visit the link, verify certificates, detect malware or normalize the query into a unique object. Duplicate keys are legitimate in many systems. Host and path spelling may still be normalized by the browser’s URL implementation even when query pairs are preserved.
Pasted input with spaces or non-ASCII characters may need encoding first—use URL Encoder / Decoder for component values.
A worked example
?tag=a&tag=b&q=green+tea
Two tag pairs remain separate; q becomes “green tea” with form mode enabled.
A query can legitimately contain the same key more than once. Converting it directly to a simple object may lose values. Parsing does not verify the destination or detect malware.
What URL parsing preserves
The parser reports the scheme, host, port, path, query and fragment without rewriting the URL through a normalizing serializer. Repeated query keys remain separate pairs, and unrecognized pairs keep their raw encoded spelling and order. Credentials in the authority are flagged and redacted in the report so a password is not copied into a screenshot or ticket.
Default ports may be omitted by the browser or shown explicitly depending on the input. Percent escapes are decoded only where the selected mode says so. The tool does not fetch the URL, resolve redirects or test whether the destination exists.
Parsing a query string on its own
Query-only mode treats the input as the part after ?. Form mode decodes + as a space; URL mode keeps + literal. Use query mode when you copied parameters from a form, a log line or a tracking template, and full-URL mode when you need the host and path as well.
Repeated keys are common in filters and tags; they are not collapsed into one value. If you need to remove tracking fields, use URL Tracking Parameter Cleaner rather than deleting pairs by hand.
Processing and privacy
URL Parser inspects the pasted URL in the page; the address and its query values are not uploaded. Input stays in browser memory until you reset or leave the page. Copy and download run only when you choose them. No tool input is sent to a processing service. Website pages and scripts still make ordinary hosting requests; the privacy policy separates those from tool processing.
Frequently asked questions
Does the parser visit my link?
No. It inspects the supplied string locally and does not request its destination.
Why keep duplicate query keys?
Many APIs and pages accept repeated keys. Collapsing them into an object would lose values.
Can I parse a relative path?
Use query-string mode for bare query text. Full component parsing expects an absolute HTTP(S) URL.
Are credentials shown in the output?
They are reported as present but redacted. Do not paste production credentials into shared examples.
What if the URL has Unicode characters?
Percent-encoded sequences are decoded once with strict UTF-8. Invalid sequences produce an error rather than replacement characters.
Does the parser decode the URL more than once?
No. Apply decoding deliberately; repeated decoding can turn an encoded value into a different string.
Are credentials shown in the result?
They are detected and redacted in the report so a password is not exposed in copied output.
How this tool was checked
URL Parser was checked with repeated query keys, plus-as-space form mode, credentials that must be redacted, fragments, default ports and malformed percent escapes. See the testing method or report a failure.