Skip to main content
ToolsHub

URL Parser

Paste a URL to split it into its components and read every query parameter in a table.

Updated

Files never leave your browser

Paste a full URL to break it into protocol, host, path, query, and hash.

URL breakdown appears here

Paste a URL to see its protocol, host, path, query parameters, and hash.

How to use URL Parser

The URL parser breaks any absolute URL into its component parts and lays them out clearly: protocol, hostname, port, path, hash fragment, and origin, plus a table of every query parameter with its value already percent-decoded. It is the fastest way to make sense of a long tracking URL, debug a redirect, or confirm exactly which parameters a link is carrying. Parsing uses the browser’s own URL engine, so results match what a browser actually sees, and nothing is uploaded.

  1. Paste an absolute URL into the input.
  2. Read the protocol, host, port, path, and hash.
  3. Review the query parameters in the table.
  4. Copy the summary if you need it.

Your data never leaves your device — 100% private processing.

Anatomy of a URL

Every URL follows the same structure, even when it looks like an unreadable wall of characters. The protocol (https) says how to fetch the resource. The hostname (example.com) says which server, optionally followed by a port when it is not the protocol default. The path (/products/42) identifies the resource on that server. Everything after a question mark is the query string, a set of key–value pairs the server or page reads as input. Finally, anything after a hash is the fragment, which never reaches the server and is used by the page itself to scroll to a section or drive client-side routing. Separating these parts makes a confusing URL immediately legible.

Parts of https://example.com:8080/path?q=hi#top
PartValueMeaning
ProtocolhttpsHow to fetch it
Hostnameexample.comWhich server
Path/pathWhich resource

Query strings and encoding

Query parameters carry data in the URL, and because URLs may only contain a limited set of characters, anything else must be percent-encoded: a space becomes %20, an ampersand inside a value becomes %26, and so on. This is why raw URLs are so hard to read. The parser decodes each value for you, so you see the real text rather than the escaped form. It also splits repeated keys correctly and preserves their order, which matters when a system reads only the first or last occurrence. The fragment after the hash is shown separately because it behaves differently — it is never sent to the server, so it cannot be a parameter the backend reads.

Worked examples

Full URL

Inputs: https://example.com/p?q=hi#top

Result: https · example.com · /p · q=hi · #top

Decoded

Inputs: ?q=a%20b

Result: q = "a b"

Port

Inputs: http://localhost:3000/x

Result: port 3000

Glossary

Protocol
The scheme such as http or https that says how to fetch the resource.
Query string
The part after ? carrying key–value parameters.
Fragment
The part after #, used by the page and never sent to the server.
Percent-encoding
Escaping special characters as % followed by hex digits, e.g. %20 for a space.

Related reading

Free · No spam

Get weekly tool tips & updates

New tools, power-user tips, and productivity hacks — delivered free every Friday.

No spam, ever. Unsubscribe with one click.

Related Developer Tools

Explore all Developer Tools.