URL Parser / Inspector

Break any URL into its components — protocol, host, port, path, query parameters and fragment.

The URL Parser breaks any link into its individual parts — protocol, host, port, path, query string parameters and fragment — and lists every query parameter as a decoded key–value table. Paste a messy URL from logs, an API or the address bar to read it at a glance, then copy the whole breakdown as JSON.

  • Decodes and lists every query parameter
  • Shows protocol, host, port, path and hash
  • Copy the full breakdown as JSON
  • 100% private — uses your browser's URL engine

URL Components

ComponentExampleDescription
ProtocolhttpsThe scheme used to access the resource
Hostapi.example.comDomain or IP of the server
Port8443Network port (defaults: 80 http, 443 https)
Path/v2/searchLocation of the resource on the server
Query?q=json&page=2Parameters passed to the server
Fragment#resultsClient-side anchor, never sent to server

Where URL Parsing Helps

  • Debugging a redirect or webhook URLPaste a long, percent-encoded URL from logs and instantly see the real host, path and query values instead of decoding it by eye.
  • Reviewing tracking and UTM parametersBreak a marketing link into its query parameters to verify utm_source, utm_campaign and similar values before sending a campaign.
  • Inspecting an API request URLConfirm exactly which query parameters a client is sending — including ones hidden by encoding — while debugging an integration.
  • Auditing third-party linksCheck the actual destination host and path of a shortened or obfuscated URL before clicking it.

UTM Parameters Reference

UTM (Urchin Tracking Module) parameters are the standard query parameters marketing tools and analytics platforms — Google Analytics included — use to attribute traffic to a specific campaign, source, and medium. Paste any marketing link here to see exactly which ones are set:

ParameterRequired?Purpose
utm_sourceRequiredWhere the traffic comes from, e.g. newsletter, google, twitter
utm_mediumRequiredThe marketing medium, e.g. email, cpc, social
utm_campaignOptionalThe specific campaign name, e.g. summer_sale_2026
utm_termOptionalPaid search keyword being tracked
utm_contentOptionalDifferentiates similar content or links within the same ad/campaign
utm_idOptionalA campaign ID, used to tie the link to an ads platform's own tracking

Frequently Asked Questions

Paste the full URL. Every query parameter is listed in the Query Parameters table as a decoded key–value pair, so you can read percent-encoded values easily.

The parser needs a scheme. Add https:// (or another protocol) to the front of the address. Relative paths like /foo?bar=1 cannot be parsed on their own.

No. The fragment is used only by the browser/client and is never transmitted in the HTTP request. It is shown here for completeness.

No. Parsing uses the browser's built-in URL API entirely on your device — nothing is uploaded.

Repeated keys are both preserved and shown as separate entries in the query parameters table — the URL spec allows a key to appear more than once, and it's up to the receiving server to decide whether to treat it as a list or use only the last value.

utm_source and utm_medium are the two that matter most for basic attribution — they tell analytics tools where a visitor came from and through what channel. utm_campaign, utm_term, utm_content, and utm_id are optional and add more granular tracking detail.

Paste the finished link here — every utm_ parameter appears as its own row in the query parameters table with the decoded value, so you can confirm the source, medium, and campaign name are exactly what you intended before the link goes out.

Related Tools