Skip to content

URL Parser - Split a URL and Edit Query Parameters

Break a URL Into Its Parts

Long URLs from analytics links, OAuth redirects and API calls are hard to read. This parser splits a URL into its components and lists every query parameter in a table with the percent-encoding removed. You can then change values, add or remove parameters, and the URL is rebuilt for you with correct encoding.

Anatomy of a URL

Take this URL: https://admin:[email protected]:8443/search/red%20shoes?q=size+9&sort=price&tag=sale&tag=new#results. It breaks down as follows:

PartValue
Protocolhttps:
Username / passwordadmin / s3cret
Hostshop.example.com
Port8443
Path/search/red%20shoes
Query?q=size+9&sort=price&tag=sale&tag=new
Hash#results

The query parameters decode to q = size 9, sort = price, tag = sale and tag = new. The decoded path is /search/red shoes. The hash (fragment) is never sent to the server; the browser keeps it for in-page navigation or for single-page apps.

How to Use the URL Parser

  1. Paste a full URL into the box at the top.
  2. Read the components and decoded parameters below it.
  3. Edit a key or value in the table, or use + Add and × to change the list.
  4. Copy the updated URL from the input box or the Normalised URL panel.

Common Tasks

  • Strip tracking parameters. Delete the utm_source, utm_medium, fbclid or gclid rows and copy a clean link.
  • Debug OAuth redirects. Check redirect_uri, state and scope values. redirect_uri is a whole URL encoded inside another one, which is hard to read raw and easy to get subtly wrong.
  • Build test URLs. Start with a base URL, add parameters in the table and let the parser handle encoding of spaces, ampersands and Unicode.

Repeated Keys and Arrays

A query string can contain the same key more than once, as in tag=sale&tag=new. The parser keeps each occurrence as its own row, in order, because servers handle duplicates differently: PHP keeps only the last tag unless the key is written tag[], Express (with its default qs parser) returns an array, and other frameworks keep only the first value. Keys with brackets, such as filter[color]=red, are shown exactly as written so you can see what the server receives. Order is preserved when the URL is rebuilt, which matters for signed URLs where the signature covers the exact query string.

Encoding Notes

When the URL is rebuilt, parameters are written in application/x-www-form-urlencoded form, the same format HTML forms and URLSearchParams use. Spaces become + and reserved characters become %XX. To encode or decode a single value, or to see which characters need encoding, use the URL encoder and percent-encoding table.

Related Tools

Frequently Asked Questions

How do I see the query parameters in a URL?
Paste the URL into the box. Every parameter after the ? is listed as a key and value, already decoded, so %20 and + show as spaces and %26 shows as &. Repeated keys such as tag=a&tag=b appear as separate rows in their original order.
Can I edit parameters and get the new URL?
Yes. Change any key or value, add a row or delete one, and the URL box updates immediately with the values correctly encoded. Copy it from the URL box or the Normalised URL panel.
Why did my URL change slightly after parsing?
The parser uses the same WHATWG URL rules as browsers, so it normalises the URL: the scheme and host are lower-cased, default ports such as :443 are dropped, and unsafe characters are percent-encoded. When you edit parameters, values are form-encoded, so spaces become +.
What if my URL has no http:// or https://?
If you paste something like example.com/page?id=1, the parser assumes https:// and tells you it did. Relative URLs such as /page?id=1 are also parsed this way, with the first path segment treated as the host, so add a real host for accurate results.
Is the URL sent to a server?
No. Parsing happens in your browser with the built-in URL API. Nothing is fetched or logged, so it is safe to paste URLs that contain tokens, but remember those tokens are still visible on your screen.