URL Parser

A long URL is a packed suitcase: protocol, host, port, path, a query string full of parameters and sometimes a fragment, all zipped into one line. This parser unpacks it for you. Paste any URL and see every component in its own clearly-labelled row, with the query string exploded into a parameter table — keys and decoded values — so you can debug tracking links, inspect redirects, compare UTM tags or understand exactly where a link really goes before you click it. The parser doubles as a debugging instrument for the web’s most misleading class of bug: the URL that looks right. Encoded characters are the usual suspect — a %20 where a + was meant, a double-encoded %2520 from a redirect chain, an IDN domain silently punycoded. Lining a broken link and a working link up in the parameter table and comparing row by row finds these in seconds, because encoding differences hide from the eye in a full URL but stand out alone in a cell.

Quick Answer: Paste a URL and instantly see its protocol, host, port, path, hash and a decoded table of every query parameter. Click any row value to copy just that part.

Free Online Tool

URL to parse

Query parameters

How to Use the URL Parser

Paste the full URL into the input box.
Read each component in the breakdown table.
Review the query parameter table — every key with its decoded value.
Click any value to copy just that piece.
Edit the URL in the box and watch the breakdown update live.

Key Features

Full breakdown: protocol, host, hostname, port, path, hash and origin
Query string decoded into a clean key–value table
Click any component to copy it alone
Live updates as you edit the URL
Free, local and no sign-up

Best Practices and Tips

Check the host row carefully on suspicious links — phishing hides in look-alike domains and long subdomains.
UTM parameters live in the query table: utm_source, utm_medium and utm_campaign tell you how a visit was tracked.
A missing port row means the default (80 for http, 443 for https) is in use.
Encoded values (%20, %26) are shown decoded here; the raw URL keeps its encoding.
The hash/fragment never reaches the server — it is read only by the browser.
When a shared link misbehaves, delete tracking parameters (utm_*, fbclid) and test the bare URL — half of “the link is broken” reports are a mangled parameter, not a dead page.

Common Mistakes to Avoid

Assuming the first part of a long hostname is the real domain — read the host from the right: the registrable domain sits just before the path.
Confusing the path with the query string; parameters start after the question mark.
Sharing a URL whose query table contains session or reset tokens.
Thinking the fragment is sent to the server — it is not.

Frequently Asked Questions

What are the parts of a URL?

Protocol (scheme), host (which may include a port), path, query string and fragment. This tool shows each one separately plus the combined origin.

What does the query table show?

Every parameter after the question mark, split on ampersands, with values percent-decoded so encoded characters read naturally.

Can it parse URLs without a protocol?

A scheme is required for a reliable parse; if your text lacks one, the tool assumes https:// and notes that it did so.

Is any data sent anywhere?

No. Parsing happens entirely in your browser.

Is this parser free?

Yes — free, unlimited and no sign-up required.

Why does the same parameter appear twice in the table?

Because it appears twice in the URL — legal, and common with tag-style parameters. Servers differ on whether the first or last value wins, which the parser makes visible.