Is my URL sent to a server?

No. Parsing uses the browser URL API and runs entirely on your device.

What if the URL has no scheme?

The tool tries https:// as a prefix so host-only or path-only inputs can still parse when valid.

Runs in browser

Parse URLs into protocol, host, path, query params, and hash.

Parse any URL into protocol, host, port, path, query parameters, and hash. Copy components individually or export everything as JSON.

URL

Breakdown

Component	Value
Protocol	https:
Host	api.example.com:8080
Port	8080
Path	/v1/users/profile
Query · `id`	id=123 Decoded value: `123`
Query · `token`	token=abc Decoded value: `abc`
Query · `format`	format=json Decoded value: `json`
Query · `debug`	debug=true Decoded value: `true`
Hash	#settings

🔒 Runs in your browser · No uploads · Your data never leaves your device

Paste a URL
Use the sample URL or paste your own — http(s), ports, paths, query strings, and hashes are supported.
Read the breakdown
Review protocol, host, port, path, and hash in the table; expand query parameters for key/value copy buttons.
Copy or export
Copy any cell with its row button, or copy the full structure as JSON for scripts and docs.

Debugging API request URLs — Break down a complex API URL to inspect each query parameter, path segment, and auth token separately during debugging.
Extracting query parameters — Quickly extract and copy individual query parameters from URLs shared in logs, tickets, or error reports.
Validating URL structure — Confirm that a URL's protocol, host, path, and fragment are correctly formed before using it in code or configuration.

Non-default port and multiple query keys.

Input

https://api.example.com:8080/v1/users/profile?id=123&token=abc#settings

Output

Structured protocol, host, port 8080, path, params id and token, hash #settings.

Is my URL sent to a server?: No. Parsing uses the browser URL API and runs entirely on your device.
What if the URL has no scheme?: The tool tries https:// as a prefix so host-only or path-only inputs can still parse when valid.

Query string: The portion of a URL after the ? character, containing key=value pairs that pass data to the server.
URL fragment: The part after # in a URL, used client-side for section anchoring or SPA routing — not sent to the server in HTTP requests.
Origin: The combination of protocol, host, and port that identifies where a resource comes from (e.g., https://api.example.com:443).

You might find these useful too.