URL Parser & Query String Builder

Parse, normalize, inspect, and rebuild complete or relative URLs with ordered query editing and IDN details.

Workspace

Parse and normalize

URL source

Editable components

URL parts

Credentials

Credentials in a URL can be copied, logged, or shared with the URL. Remove them unless they are required.

Preserves order and duplicates

Query parameters

0 parameters

No query parameters.

Normalized result

Built URL

Guide

How to use

  1. Paste a complete, schemeless, protocol-relative, or relative URL. Relative references use the editable base URL.
  2. Review and edit protocol, credentials, Unicode or ASCII hostname, port, path, fragment, and ordered query rows.
  3. Add, remove, duplicate, reorder, sort, or bulk-replace query parameters while the normalized URL rebuilds.
  4. Copy the URL, download its component breakdown, or move the normalized value back into the source field.
Help

Frequently asked questions

Are repeated and blank query parameters preserved?

Yes. Repeated keys remain separate ordered rows, and a blank key or blank value can be edited and rebuilt without being discarded.

Does the URL need a protocol?

No. A domain-like input receives HTTPS automatically, //example.com uses HTTPS, and paths such as ../image.png resolve against the selected base URL.

Why are two hostname forms shown?

Internationalized domains can be displayed with readable Unicode characters and an ASCII Punycode form beginning with xn--. Both refer to the normalized hostname.

Can URLs contain a username and password?

Some hierarchical URLs can contain credentials, but they are easy to expose through copying, logs, browser history, and sharing. Remove them unless they are necessary.

How are spaces and special characters handled?

Editable decoded query keys and values are percent-encoded when rebuilt. The pathname insight shows a decoded reading while the built URL retains a valid encoded path.