URL Parser

How to use this tool

1. Enter the source in the input field.
2. Enter an absolute HTTP(S) URL without credentials. Choose the full JSON report, decoded query name/value report or encoded query string.
3. Valid input updates after a brief typing pause. You can also use the main action button. Resolve errors before copying or downloading.
4. Clear input keeps the conversion settings; Undo input change restores the previous inputs after clear or reverse. Reset restores the example and default settings.

Understanding the output

The output uses the browser’s URL parsing rules. Query parameters are listed as an array so repeated names remain visible. Query values are decoded using URLSearchParams, while the path and fragment retain their URL representation. A default port is shown as default after normalization.

To add consistent campaign parameters to a destination, use the UTM Link Builder after checking the existing query.

Separate the destination from its parameters

The hostname identifies the host portion of the address, while the path and query can select a resource or provide input to an application. A fragment follows the hash sign and is commonly used by the browser for a location within the page. Understanding these boundaries helps diagnose a malformed link without repeatedly opening it.

The normalized URL may differ in appearance from the input. Hostnames can become lowercase, internationalized hostnames can use ASCII encoding, and default ports can disappear. These changes reflect parsing and serialization rules rather than a request to the server.

Parsing is not a trust or availability check

A well-formed URL can still lead to an unavailable or untrustworthy destination. This parser does not resolve DNS, follow redirects, inspect certificates, or assess reputation. It also refuses embedded credentials to avoid treating a sensitive login-bearing address as routine input. Review the hostname carefully before using any URL in a real workflow.

Method and supported input

The URL constructor parses an absolute HTTP or HTTPS address. URLSearchParams supplies decoded name-value pairs while preserving repeated parameter names.

The query report writes one entry per line with JSON-quoted names and values separated by a tab, preserving duplicate parameters and escaping embedded control characters. Encoded query output omits the leading question mark.

• The input is an absolute web URL, not a relative path.

Limitations

• No network verification or redirect expansion is performed.
• Parser normalization is not a byte-for-byte representation of the original string.

Common questions