Free Online URL Parser
Break any URL into protocol, host, path, query, and fragment parts.
Query parameters
0 parameters| # | Key | Value | Copy |
|---|
This URL has no query string.
Parsing uses the browser's built-in URL API. Values are percent-decoded when displayed. If you omit the
scheme, https:// is assumed; a path beginning with a slash is resolved against this site.
About the URL Parser
A URL looks straightforward until you need to isolate one piece of it. Behind the familiar address bar syntax sit a scheme, an authority that may include credentials and a port, a path, a query string, and a fragment. This parser splits a pasted address into each component and presents the query parameters as a table, which is far easier to inspect than a dense line of ampersands. It is useful when debugging redirect targets, tracking parameters, API endpoints, signed download links, and deep links in mobile apps.
Components you will see
- Protocol: the scheme, such as
https:orftp:, including the colon. - Host and hostname: the host includes an explicit port; the hostname never does.
- Port: shown explicitly when present; browsers hide the default 80 or 443 value.
- Path: the hierarchical portion after the authority, percent-encoded as written.
- Query: the raw string after the question mark, plus a decoded key and value table.
- Fragment: the part after the hash, which is handled by the browser or client app rather than sent in the HTTP request.
- Origin: the scheme, host, and port combination used by browser security rules.
The parser normalizes some details automatically. Letter case in the scheme and hostname is lowered, an empty path becomes a single slash, dot segments are resolved, and spaces in the query are displayed as decoded characters. These are the same rules the URL standard applies inside a browser, so the result reflects how a request would actually be interpreted. The raw query string is still available through the copy action, which is helpful when an upstream service signs the exact byte sequence and re-encoding would invalidate the signature.
Duplicate parameter names are preserved in order. That matters for APIs that accept repeated keys, such as filter lists or array values without bracket notation. Empty values are shown as empty rather than hidden, because a parameter with no value can still trigger behavior on the server. If a URL contains a plus sign in the query, the browser's parameter parser treats it as a space, while the raw copy action keeps the plus, again preserving both interpretations.
Copy buttons are attached to every field and every parameter row, so you can move a hostname into a configuration file or a token into a debugging tool without retyping it. The complete structure can be copied or downloaded as JSON for scripts, tests, or issue reports. Everything happens locally; the URL and any secrets embedded in it are never transmitted by this page.
How to use this tool
- Paste or type an address into the input field.
- The parser runs as you type, or click Parse URL to force an update.
- Review the component cards and the query parameter table.
- Copy a single value, the full JSON object, or the raw query string.
Frequently asked questions
Why is the port field empty for most websites?
The URL standard omits default ports from the serialized host. When a site uses the normal port for its scheme, no port appears. An explicit non-default port, such as 8080, is displayed.
Is the fragment sent to the server?
No. Browsers strip the fragment before making an HTTP request. It is available to client-side JavaScript and is often used for anchors or single-page routing.
Why do some characters look decoded in the table?
The table displays percent-decoded values for readability. The copy query action preserves the original encoded text, which is what a server receives.