URL Parser

How to use it

1. Paste a URL into the input — including scheme, port, path, query string and fragment if present.
2. The parts table lists protocol, host, hostname, port, pathname, origin and hash.
3. The parameters table shows every query parameter decoded, one row per pair; repeated names get one row each.
4. Parsing is strict: a URL without a scheme produces a clear error instead of a guess.
5. Edit the URL and the tables update automatically.

Common use cases

• Inspecting tracking links — see every parameter a marketing URL carries before clicking it.
• Debugging routing — confirm how a framework splits path and query for an incoming request.
• Reviewing API endpoints — read host, port and path components at a glance during code review.
• Teaching URL anatomy — show the difference between host and hostname, or where the fragment lives.

Why it stays private

The parse happens with the browser's own URL implementation. Links with tokens, session identifiers or internal hostnames are never sent anywhere.

FAQ

Q: Does it decode percent-encoded query values? A: Yes. The URL API decodes query parameters automatically, so %E5%A5%BD shows as its readable form in the parameters table.

Q: Why is a URL without https:// rejected? A: The URL standard requires a scheme; without one, inputs like example.com/path are ambiguous. The error tells you to add the scheme instead of guessing one.

Q: How are repeated parameters displayed? A: Each occurrence gets its own row, so tag=a&tag=b shows two rows — matching how server frameworks usually read them.