URL Parser & Query String Editor

See every part of a URL at a glance and edit its query parameters in a table. The rebuilt URL updates as you type.

✓ Runs locally in your browser — nothing is uploaded

Query parameters

NameValue (decoded)

In short: A URL parser splits a web address into its parts — protocol, host, port, path, query parameters and fragment — so you can read, edit or clean tracking parameters like utm_source.

About URL Parser & Query String Editor

Long URLs pack a lot into one line: the scheme, an optional username, the host and port, the path, a query string of key–value pairs and a fragment. When you are debugging a redirect, building an API request or cleaning up a link before sharing it, it helps to see each piece on its own.

This parser uses the browser’s standard URL API, the same one your front-end code uses, so the breakdown matches what browsers really do. Query parameters are shown decoded in an editable table; change a value, delete a row or add a new one and the full URL is rebuilt with correct encoding. A one-click button strips utm_ tracking parameters before you share a link.

How to use URL Parser & Query String Editor

  1. Paste a full URL including the scheme, e.g. https://.
  2. Read the parts list: protocol, host, port, path, query and fragment.
  3. Edit parameter names and values directly in the table, delete rows, or add new ones.
  4. Copy the rebuilt URL from the box at the bottom.

Examples

Cleaning a shared link

Paste a link with utm_source, utm_medium and utm_campaign, press Remove utm_* tracking, and copy the shorter URL.

Debugging an API call

A request to /search?q=red%20shoes&page=2 shows q as red shoes and page as 2, confirming the client encoded the space correctly.

Frequently asked questions

Why do I get “Invalid URL”?

The URL API needs an absolute URL with a scheme. Add https:// in front of addresses like example.com/page.

Can a parameter appear more than once?

Yes, e.g. ?tag=a&tag=b. The table shows each occurrence as its own row, and the rebuilt URL keeps them in order.

Does the fragment get sent to the server?

No. The part after # stays in the browser. Servers only see the path and query string.

Is my URL logged?

No, parsing happens locally and nothing is sent anywhere. You can check this yourself: open your browser’s developer tools, switch to the Network tab and use the tool — no request carries your input.

Updated November 2026 · Free, no signup · How we build and test tools

Related tools All developer tools →