URL Parser & Query String Editor
Break an http(s) URL into protocol, host, port, path, fragment and query parameters, then add, edit, reorder or remove parameters with a live rebuilt URL.
Loading URL Parser & Query String Editor…
About the URL Parser & Query String Editor
URL Parser & Query String Editor splits an http:// or https:// address into its parts — protocol, host name, port, path and fragment — and lists every query parameter in order, including repeated keys such as tag=a&tag=b. You can then edit keys and values, add or remove parameters and move them up or down, and the final URL is rebuilt live with correct percent-encoding and the original #fragment.
Values are shown decoded so they are easy to read and edit, and a per-parameter preview shows exactly how each will appear in the URL. The address is treated purely as text: the tool never opens, fetches, crawls or tests it.
How to use
- Paste a full http:// or https:// URL and click Parse URL (or press Enter).
- Check the URL parts table: protocol, host, port, path, fragment and origin.
- Edit parameter keys and values, use the arrows to reorder, Remove to delete or Add parameter for new ones.
- Use Decode %XX or Percent-encode on a value if you pasted it in encoded form or need it encoded.
- Copy the final URL or the parsed data, or download a summary.
Key features
- Separate display of protocol, host name, port, path, fragment and origin.
- Every query parameter in its original order, with repeated keys labelled.
- Add, edit, remove and reorder parameters with a live rebuilt URL.
- Per-value decode and percent-encode controls with an “in URL as” preview.
- Fragments preserved at the end of the rebuilt URL.
- Clear errors for malformed and non-HTTP(S) URLs.
Best practices
- Keep repeated keys in the order your server expects — some frameworks read only the first or last.
- Remember that a + in a query string is usually read as a space.
- Avoid putting passwords, tokens or personal data in URLs; they end up in logs and history.
- Use the UTM Campaign URL Builder for campaign tagging rather than editing utm_ parameters by hand.
- Test the edited URL in your own app — this tool does not open it.
Benefits
- Read long, encoded URLs at a glance.
- Edit query strings without breaking encoding.
- Handy for debugging redirects, APIs and tracking links.
- Private: nothing is fetched or sent.
Frequently asked questions
Does this tool visit the URL?
No. The URL is only parsed as text in your browser; nothing is opened, fetched or tested.
How are repeated keys handled?
Each occurrence is kept as its own row in the original order and labelled, for example “repeated key · 2 of 3”.
Why does + appear as a space?
In query strings a + traditionally means a space (form encoding). The tool reads it that way. Parameters you do not touch keep their original spelling in the final URL; once you edit a parameter, its spaces are written as %20 to be unambiguous.
What do Decode %XX and Percent-encode do?
They convert the text in that value field. Decode turns sequences like %20 back into characters; Percent-encode converts the text into its encoded form. Edited parameters are always encoded automatically in the final URL.
Which URLs are supported?
Absolute http:// and https:// URLs. Other schemes such as ftp:, mailto: or javascript: are rejected.
Is the #fragment kept?
Yes. It is shown separately and placed back at the end of the rebuilt URL.