Why does my input fail?

URLs need a scheme. `example.com/path` is not parseable; `https://example.com/path` is. Relative paths and protocol-relative URLs (`//example.com`) won't parse either.

Why is `port` empty for https://example.com?

When the port is the protocol default (80 for http, 443 for https), `URL.port` is intentionally empty. The browser would still connect to 443.

Are query params decoded?

Yes. `%20` shows as space, `%2F` as `/`. Copy a key or value to get the decoded form. If you need percent-encoded text, look at `search` instead.

Does this send the URL anywhere?

No. Parsing happens entirely in your browser via the WHATWG URL API.

URL Parser

Paste any URL and see every part labeled — protocol, origin, hostname, port, pathname, search string, and fragment. Embedded credentials (user:pass@) show separately. Query parameters are decoded and listed as key/value rows so you can spot duplicates and check encoding. Uses the browser's WHATWG URL parser, the same one Fetch and XHR use, so what you see is what your code will see.

—

URL

Protocol

https:

Origin

https://example.com:8080

Hostname

example.com

Port

8080

Pathname

/path/to/page

?q=hello&lang=en

Hash

#section

Username

user

Password

pass

Query parameters

Key	Value
q	hello
lang	en

Parsing uses the browser's native URL API.

How to use

Paste a URL (must include a scheme, e.g. https://).
Read off the parts and copy any piece individually.
Scan the query-params table to verify each value.

Frequently asked questions

Why does my input fail?: URLs need a scheme. `example.com/path` is not parseable; `https://example.com/path` is. Relative paths and protocol-relative URLs (`//example.com`) won't parse either.
Why is `port` empty for https://example.com?: When the port is the protocol default (80 for http, 443 for https), `URL.port` is intentionally empty. The browser would still connect to 443.
Are query params decoded?: Yes. `%20` shows as space, `%2F` as `/`. Copy a key or value to get the decoded form. If you need percent-encoded text, look at `search` instead.
Does this send the URL anywhere?: No. Parsing happens entirely in your browser via the WHATWG URL API.

Related tools

Query String to JSON Converter

Convert a URL query string to a JSON object and back, in your browser.

Developer 0 0

String Escape Converter

Escape a string for 10 contexts at once — JavaScript, JSON, HTML entities, URL, SQL, regex, Bash (single/double quote), C string, Unicode \u escapes. Copy whichever you need.

Developer 0 0

URL Query Builder

Build URLs by combining a base address with editable key-value query parameters — each pair toggleable, properly percent-encoded.

Network 0 0

Data URI Parser & Decoder

Decode a data: URI to see its MIME type, encoding, size and decoded contents, in your browser.

Developer 0 0

JSONPath Tester

Run JSONPath queries (`$.store.book[*].author`, `$..price`) against a sample document and see the matching values.

Developer 0 0

Hash Generator (SHA)

Generate SHA-1, SHA-256, SHA-384, and SHA-512 hashes from text.

Developer 0 0