URL Parser
Break any URL into protocol, host, port, path, query, and hash. Edit query parameters in a table and rebuild the URL live. Entirely client-side.
About this tool
Paste a URL and see every component pulled apart: the scheme, any embedded
credentials, the host and port, the path, the fragment, and the computed
origin. Below that, every query-string parameter is laid out as an
editable name/value table. The breakdown comes from the browser’s own
URL parser, so what you see is precisely how a browser — and
most servers — will interpret the address.
The query table is two-way. Rename a parameter, change a value, add a new
pair, or remove one, and the URL field rebuilds immediately with correct
percent-encoding. That makes it a quick way to construct an API request,
strip tracking parameters like utm_*, or sanity-check why a
link is routing somewhere unexpected — without hand-editing fragile
encoded strings.
Because everything runs client-side, it is safe to paste URLs that contain
session tokens, signed query parameters, or basic-auth credentials: none
of it is transmitted. Note that the tool works on absolute URLs — those
with a scheme such as https:// — since a relative path has no
host or protocol to parse on its own.
Frequently asked questions
What does this tool break a URL into?
Protocol, optional username and password, hostname, port, path, hash fragment, and the full origin — plus a table of every query parameter. It uses the browser’s built-in URL parser, so the breakdown matches exactly how a browser interprets the address.
Can I edit the query string here?
Yes. Each query parameter is an editable name/value pair. Change one, add a new pair, or delete a row and the URL field at the top rebuilds itself instantly with proper percent-encoding.
Why does it say my URL is invalid?
The parser requires an absolute URL with a scheme. example.com/path fails; https://example.com/path works. Relative URLs have no defined host or protocol on their own, so add the scheme first.
How are encoded characters handled?
Parameter values are shown decoded for readability, and re-encoded correctly when you edit them. Spaces, ampersands, and Unicode in values are percent-encoded in the rebuilt URL so it stays valid.
Is the URL sent anywhere?
No. Parsing and rebuilding happen entirely in your browser. The URL — including any tokens or credentials in it — never leaves your device.