URL Parser & Query String Builder
Break a URL down into protocol, host, path, and query parameters, then add, edit, or remove parameters and get a correctly-encoded URL back — all in your browser.
Breakdown
| Field | Value |
|---|---|
| Protocol | https: |
| Username | (none) |
| Password | (none) |
| Host | shop.example.com:8443 |
| Hostname | shop.example.com |
| Port | 8443 |
| Pathname | /products/search |
| Hash | #reviews |
| Origin | https://shop.example.com:8443 |
Query parameters (editable)
Rebuilt URL
https://shop.example.com:8443/products/search?category=shoes&sort=price_asc&page=2#reviews
About this tool
How to use it
- Paste a full URL, including its protocol (https:// or http://), into the input.
- The breakdown table shows protocol, host, port, path, hash, and any credentials — and each query parameter appears as its own editable row below.
- Edit any parameter's key or value, remove one, or click Add Parameter to add a new one — the rebuilt URL at the bottom updates live and handles all the encoding for you.
- Click Copy to grab the final URL.
Why it matters
Query strings are easy to get subtly wrong by hand — a space that needs to become %20, an & inside a value that needs escaping so it isn't read as a second parameter, or a stray parameter left over from a copy-pasted tracking link. Using the browser's own URL and URLSearchParams objects to parse and rebuild means the encoding is always correct, not approximated.
When to use it
Cleaning tracking parameters out of a shared link before posting it somewhere. Building a test URL with specific query parameters for an API call or a bug report. Understanding exactly what a long, unfamiliar URL actually points to and what parameters it's passing.
Good to know
Parsing and rebuilding both use the browser's native URL and URLSearchParams APIs — the same parser your browser itself uses to navigate — not a hand-written regex. A password in the URL is detected and its presence noted, but never displayed, since URLs with embedded credentials are already a legacy, insecure pattern most modern software rejects. Rebuilding a parameter list always produces standard application/x-www-form-urlencoded percent-encoding, matching what URLSearchParams itself performs.
Common questions
Why do I need to include https:// for it to parse?
A URL's protocol is what tells a browser (and this tool's parser) where the host name starts and how to interpret everything else — without one, "example.com/search?q=x" is ambiguous between a URL and a relative path. Add the protocol and it parses correctly.
Will editing a parameter properly encode special characters?
Yes — rebuilding uses the browser's native URLSearchParams, which handles percent-encoding for spaces, ampersands, and any other reserved characters exactly the way a browser would when you submit a form.
Why does the password field say '(hidden — present)' instead of showing the actual password?
This tool never displays a credential embedded in a URL, even though it can detect one is there — showing it back on screen risks it ending up in a screenshot, a shared link, or a support ticket. Copy the original URL directly if you need the credential.
Is my URL sent anywhere?
No. Parsing and rebuilding both happen with the browser's own URL API, entirely in your browser tab — nothing is uploaded, logged, or stored.
What if the same parameter name appears more than once in the URL?
Each occurrence becomes its own editable row, in the order it appeared — repeated parameter names are valid and common (e.g. `?tag=a&tag=b`), and editing one occurrence doesn't affect the others.
If my URL has a username and password in it, does the rebuilt URL include them?
No — the rebuilt URL is intentionally built from the origin, path, hash, and query parameters only, never re-embedding credentials. If you need the original URL with its credentials intact, copy it directly rather than the rebuilt output.