URL Parser

What this tool does

A tracking link arrives with six query parameters, a hashed fragment and a percent-encoded redirect target buried in the middle. Reading it as one long string is a good way to miss the part that matters. This tool lays out the anatomy of a URL: protocol, host, port, path, every query parameter with both its raw and decoded value, and the hash fragment. Parsing happens as you type, and any decoded value can be copied with one click. Developers use it to debug API endpoints and OAuth callbacks, marketers use it to verify UTM tags survived an email campaign, and anyone who has been handed a suspicious-looking link can see its components before deciding whether to open it. Seeing a decoded redirect parameter is often the whole investigation.

How to use it in three steps

1. Paste the full URL into the box. The table of parts fills in as you type, with no button to press.
2. Read the query parameters in the decoded column, especially values that look like another URL or an encoded token. Compare with the raw column to see exactly what was escaped.
3. Copy any decoded value with one click when you need to paste it into a request, a ticket or a test case. Check the fragment separately from the query string, since single-page apps often store routing state there.

Questions people ask

Why are there two versions of each query value?

The raw form is what actually travels in the URL, while the decoded form is what the server will read. Showing both makes double-encoding and accidental escaping obvious at a glance.

Does parsing tell me whether a link is safe?

No. It shows you the address and its parameters, which can reveal a hidden redirect or an unexpected domain, but it does not check the destination's reputation or content. Treat the decoded parts as information, not as a verdict.

What about URLs with a username or an unusual port?

Those components are part of the standard URL structure and appear in the table alongside host and path. A non-default port is worth noting when debugging a local or staging service.

Does it show repeated query parameters with the same name?

Each parameter is listed with its own value, so a URL carrying two utm_source entries appears as two rows rather than one being silently discarded. That duplication is a common cause of unexpected attribution in analytics reports.

Privacy: URLs are split into their component parts by local JavaScript in this tab, so internal endpoints, private query values and links containing tokens are never sent anywhere or retained.