Skip to the content

URL Parser

Split a URL into its parts and edit the query parameters in a table.

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

The parts of a URL

Take this address:

https://ada:secret@shop.example.com:8443/coffee/menu?size=large&milk=oat#prices
PartHereWhat it is
SchemehttpsHow to talk to the server.
Username, passwordada, secretCredentials in front of the @. Rare on the web now, and best avoided: URLs end up in logs and in browser history.
Hostshop.example.comThe server, as a domain name or an IP address.
Port8443Which service on that server. Left out when it is the default: 443 for https, 80 for http.
Path/coffee/menuWhich page or resource.
Query?size=large&milk=oatExtra input, as name=value pairs with & between them.
Fragment#pricesA place inside the page.

Scheme, host and port together are the origin, here https://shop.example.com:8443. Browsers use the origin to decide which pages may read each other's data.

The splitting is done by your browser's own URL parser, so the parts you see are the parts a browser acts on when the link is followed. That is also why HTTPS://Example.com:443/a/../b comes out as https://example.com/b.

Without a scheme, as in example.com/page, https is assumed and the tool says so. A URL that starts with /, ./, ? or # is relative: it only has a meaning on the page it is written in, so only its path, query and fragment are shown.

The fragment stays in the browser

Everything from the # onwards is never sent to the server. It is not in the request, so it is not in the server's logs either. Browsers use it to scroll to a heading, and web apps use it to keep state that the server has no business knowing.

Plus sign or %20 for a space?

Characters with a special meaning in a URL, and everything outside ASCII, are written as a percent sign and two hexadecimal digits per byte. A space is %20 and é is %C3%A9.

The query has a second, older convention from HTML forms, in which a space is written as +. Servers read both as a space there, and so does the table: flat+white is shown as "flat white". The catch is that a real plus sign in a query has to be written %2B. Send ada+news@example.com or +31612345678 without encoding and the plus arrives as a space. In the path a + is just a plus.

When you change a name or value in the table it is written back with %20 for spaces, which is understood everywhere. Parameters you leave alone keep their exact spelling in the URL.

The same name twice

size=large&size=small is allowed. What it means is up to the server: some take the first value, some the last, some make a list. The table keeps every parameter in its place, and the JSON copy turns a repeated name into a list.

Domain names with accents

The domain name system only carries ASCII, so bücher.example travels as xn--bcher-kva.example. That spelling is called Punycode. When a host is written that way, both forms are shown.

Which tracking parameters are removed

The button removes parameters whose only job is to tell a site which ad, mail or share button a click came from. The page you land on is the same without them. Everything else is left alone.

FromParameters
Campaign taggingevery name that starts with utm_ (Google Analytics and most other analytics tools) or mtm_ (Matomo), and Matomo's older pk_campaign, pk_kwd, pk_source, pk_medium, pk_content
Googlegclid, gclsrc, dclid, gbraid, wbraid, gad_source, srsltid, _ga, _gl
Metafbclid, igshid, igsh
Microsoft, X, TikTok, LinkedIn, Yandexmsclkid, twclid, ttclid, li_fat_id, yclid
Mailchimp, HubSpot, Marketomc_cid, mc_eid, _hsenc, _hsmi, __hstc, __hssc, __hsfp, hsCtaTracking, mkt_tok

Nothing is sent

The URL is taken apart in your browser. It is not sent anywhere or stored, which matters when a link carries a session ID or a token.

See all 12