URL Parser
Paste a URL to break it into its parts — scheme, host, port, path, query string and fragment — with an editable table of query parameters. Edit or add a parameter and copy the rebuilt URL. Everything runs in your browser; nothing is uploaded.
URL components
- Full URL (normalized)
-
- Scheme / protocol
-
- Username
-
- Password
-
- Host (hostname : port)
-
- Hostname
-
- Port
-
- Origin
-
- Path
-
- Query string
-
- Fragment (hash)
-
This URL has no query parameters. Use “Add parameter” to build one.
How the tool works
Paste or type a URL in the box and it is parsed the moment you stop typing. The address is fed to your browser’s built-in URL engine — the very same parser it uses to load a page — so the breakdown is exactly how the URL will be interpreted in practice, edge cases and all. Each part that exists is shown with a copy button; parts that are absent (no port, no username, no fragment) are hidden. The query string is split into an editable table so you can inspect, change, add or remove parameters, and a valid, correctly-encoded URL is rebuilt for you to copy.
The parts of a URL
| Part | Example | What it is |
|---|---|---|
| Scheme | https | The protocol used to fetch the resource — https, http, ftp, mailto, etc. It ends at the first colon. |
| Host | www.example.com:8443 | The hostname plus an optional port. The hostname is the domain (or an IP address); the port defaults to 443 for https and 80 for http when omitted. |
| Path | /blog/2026/hello-world | The location of the resource on the host, split into slash-separated segments. |
| Query string | ?utm_source=newsletter&page=2 | Everything after the first “?” — a list of key=value pairs joined by “&”. Used to pass data to the page or server. |
| Fragment | #comments | Everything after “#”. Sent to the browser, not the server — usually an on-page anchor or an SPA route. |
Reading and editing the query string
The query string is everything after the first ?: a list of key=value
pairs joined by &. This tool reads each pair into its own row with the value
decoded so you can read it in plain text — a value stored as
S%C3%A3o%20Paulo is shown as São Paulo. Edit a value, rename a key,
delete a pair, or add a new one, and the Rebuilt URL box updates live with
everything percent-encoded correctly. The scheme, host, path and fragment you pasted are kept
intact — only the query string is regenerated from the table, so you always get a valid address
back.
Duplicate and empty parameters
A query string is allowed to repeat a key — ?id=1&id=2 is valid, and some
systems read every occurrence. Each duplicate is shown as its own row so nothing is silently
merged or dropped. A key with no value, such as a bare ?debug flag, is kept with an
empty value. When rebuilding, rows with a blank key are skipped, so you can delete a
parameter just by clearing its name.
Common uses
- Inspect and clean up UTM tracking parameters on a marketing link before sharing it.
- Debug an API request by seeing exactly which query parameters and values are being sent.
- Pull apart a long redirect or OAuth callback URL to read its tokens and state.
- Change one parameter (a page number, a filter, a locale) and copy the new URL.
- Confirm that special characters in a value are being encoded the way you expect.
Privacy
The whole tool runs on your device in JavaScript — the URL you paste is never uploaded, logged or sent anywhere. That makes it safe to inspect links that contain session tokens, API keys or other sensitive query data.
Frequently asked questions
- What does this URL parser do?
- It takes any web address and splits it into its standard parts — scheme, username/password, hostname, port, path, query string and fragment — so you can read each one clearly. It also pulls the query string apart into an editable table of key/value pairs. Change or add a parameter and the rebuilt URL updates instantly, correctly percent-encoded, ready to copy. Everything is computed in your browser using the same URL engine your browser uses to load pages, so the breakdown matches exactly how the address will actually be interpreted.
- What are the parts of a URL?
- A full URL reads scheme://username:password@host:port/path?query#fragment. Only the scheme and host are always required; the rest are optional. The scheme (e.g. https) says which protocol to use; the host is the domain or IP plus an optional port; the path locates the resource; the query string carries key=value data after a “?”; and the fragment after a “#” points at a spot within the page and is never sent to the server. This tool labels each part it finds and hides the ones that are absent.
- What is a query string and how is it structured?
- The query string is the part of a URL after the first “?”. It is a list of parameters written as key=value and joined by “&” — for example ?page=2&sort=asc has two parameters, page and sort. Spaces and other special characters are percent-encoded (a space becomes %20 or +). This parser reads each pair into its own row so you can see, edit, add or delete parameters, then rebuilds a valid, properly-encoded query string for you.
- Why are my parameter values shown decoded?
- Inside a URL, characters that are not URL-safe are percent-encoded — a space is %20 or +, an ampersand is %26, an accented letter becomes a sequence like %C3%A9. This tool decodes each value so you can read and edit it in plain text (São Paulo instead of S%C3%A3o%20Paulo). When you edit a value and it rebuilds the URL, it re-encodes everything correctly, so the copyable result is always a valid URL even if you type spaces or symbols.
- Can I edit the parameters and get a new URL?
- Yes. Each query parameter is an editable key/value pair. Change a value, rename a key, remove a parameter with the × button, or click “Add parameter” to append a new one — the “Rebuilt URL” box updates live and the Copy button hands you the finished address. The scheme, host, path and fragment from the URL you pasted are preserved; only the query string is rebuilt from the table.
- Is my URL sent to a server?
- No. The entire tool runs client-side in JavaScript — the URL you paste never leaves your device, nothing is logged, and there is no network request. That makes it safe to inspect URLs that contain tokens, session IDs, tracking parameters or other sensitive query data.