URL Parser

Paste a URL and see its scheme, host, port, path, query parameters and fragment in a table.

URL parser
Parts
Query parameters (decoded)

What this tool does

Paste a URL and it is split into its parts: scheme, username, password, host, port, path, query string, fragment and origin. Each query parameter is decoded into its own row so you can see names and values clearly, including repeated ones. Copy the result as JSON or download it as a CSV file.

Parses a URL with the browser's URL parser and lists every component.

Decodes the query string into name and value rows, including parameters that repeat.

How to use it

  1. Paste a URL into the box. A scheme is assumed if you leave it out.
  2. Read the parts table and the decoded query parameters.
  3. Press Copy as JSON or Download CSV to keep the result.

Why use this tool

Splits a URL into scheme, host, port, path, query and fragment and decodes every query parameter into a clean table. Long URLs with tracking parameters, encoded characters and fragments are hard to read by eye. Splitting them shows exactly where the domain ends, what is in the path and which parameters are being sent.

Why we built it

We built the URL parser to decode each query parameter into its own row and to use the browser's own URL parser, so results match how the web treats the address. Encode values with the URL encoder and decoder and build tagged links with the UTM builder.

Who this tool is for

  • Developers reading query strings
  • Marketers checking tracking parameters
  • Security-aware users inspecting suspicious links

When to use it

  • Checking tracking parameters such as utm_source in a link.
  • Debugging a redirect, an API request or a callback URL.
  • Extracting the domain or path from a list of links.
  • Reading an encoded URL to see what it really contains.

How it works

The input is passed to the standard URL parser, which splits it into its components. The query string is read by URLSearchParams, which decodes percent-escapes and plus signs and keeps repeated names as separate rows. Userinfo, if present, is shown separately so you can see it is part of the address.

Links containing a username and password can be used to disguise a destination. Check the Host row, not the start of the address.

What you give it, and what you get back

Input and output of URL Parser
ItemDetails
URLA full URL, or one without a scheme (https:// is assumed).
PartsScheme, username, password, host, port, path, query string, fragment, origin.
ParametersEach query parameter's decoded name and value.
ExportJSON copy or CSV download.

Issues you may run into

Common problems with URL Parser
What you seeWhy it happensWhat to do
"Not a valid URL"The text is not a full address or contains spaces.Include the scheme and remove spaces.
Port shows (default)No port is written, so the scheme's default is used.Normal; 80 for http and 443 for https.
A parameter value looks oddIt was percent-encoded, or used a plus for a space.The decoded value is shown; check the raw query string row.

Assumptions and limitations

Frequently asked questions

How do I get the domain from a URL?

Paste the URL and read the Host row. The origin row shows scheme, host and port together.

How do I see query parameters?

They are listed in a table with decoded names and values.

What is a URL fragment?

The part after #, used to jump to a place in a page. It is not sent to the server.

Does it work without https://?

Yes. If no scheme is given, https:// is assumed and a note says so.

Why do repeated parameters appear twice?

A name can occur more than once in a query, and each is listed in order.

Is the URL uploaded?

No. Parsing is done in your browser.