URL Components

Paste a URL or hostname. Ordinary inputs update directly; above 32,768 characters or with more than 64 query segments, use Split URL (Ctrl/⌘+Enter in the editor). Parsing is local and never opens or fetches the address. Other schemes, including mailto/data/file, are shown as text.

HTTPS is added for a bare hostname, bracketed IPv6, a // authority, or a dotted hostname/localhost with a numeric port. Ambiguous intranet names with ports need an explicit https:// prefix; other explicit schemes retain their meaning. Relative paths are not resolved against this website.

The browser WHATWG URL API normalizes hostnames, international names, default ports and dot segments. Output is the normalized URL, not an exact reproduction of input. Paths and fragments remain raw, with a separate decoded text view where possible; decoding %2F does not change the parsed path structure. An empty normalized port is omitted.

Query entries retain order, duplicate names and empty names/values. + is a space and %2B a plus in form decoding. Raw query is available in details. Invalid percent escapes/UTF-8 produce a note; query replacement rules follow URLSearchParams, while undecodable component text stays raw.

Password masking covers result fields and the copied normalized URL until Show password is selected. The input itself, query tokens and fragment remain visible. Copy masked URL copies the displayed *** placeholder. Revealing resets on edit, new analysis or navigation. Your exact raw URL and hostname-recognition choice stay locally in this browser, including invalid text and any credentials you entered; masking does not protect that stored input. No parsed results, reveal state or open details are saved. Nothing is uploaded or added to the page URL. Large restored inputs wait for Split URL. No trust or reachability check. Limits: 65536 input characters and 512 query entries; browser storage limits still apply.

Disable automatic hostname recognition to parse an explicit opaque scheme such as com.example:1234 without HTTPS inference. URL normalization edge cases can differ between browser engines.