DeveloperKit

URL Parser

Split a URL into protocol, host, port, path, query parameters, and fragment, and edit the parameters as a table. Free, private, and 100% in your browser.

URL

Paste a URL to see its protocol, host, port, path, query parameters, and fragment.

Parse and Deconstruct URLs Online

Long URLs from logs, analytics, and redirects are hard to read: tracking parameters, encoded values, and fragments run together. Paste a URL to see each part on its own line and every query parameter decoded in a key-value table.

URL anatomy
https://user:[email protected]:8443/en/products?color=blue&size=42#reviews

scheme       https
credentials  user:pass
host         shop.example.com
port         8443
path         /en/products
query        color=blue&size=42
fragment     reviews

Features

  • Every URL component

    Protocol, username, password, hostname, port (with the default port), origin, path segments, query string, and fragment, each with a copy button.

  • Query parameters as a table

    Keys and decoded values side by side, with the raw encoded value and a warning for repeated keys. Copy them all as JSON.

  • Edit and rebuild

    Change, add, or remove parameters in the table and the URL is rebuilt with correct encoding, ideal for tweaking API calls and tracking links.

  • Fragment parameters

    OAuth redirects such as #access_token=…&state=… are split into their own table.

  • Internationalized domains

    Punycode hostnames like xn--mnchen-3ya.de are shown in Unicode (münchen.de).

  • Same rules as browsers

    Parsing uses the WHATWG URL standard built into your browser, so the result matches what fetch() and the address bar see. Nothing is sent anywhere.

How to Parse a URL

  1. Paste a URL into the input field.
  2. Read the colored breakdown and the component table.
  3. Inspect, edit, add, or remove query parameters; the URL updates automatically.
  4. Copy any single component, the rebuilt URL, or all parameters as JSON.

Frequently Asked Questions

What are the parts of a URL?

A URL such as https://user:[email protected]:8080/path/page?key=value#section has a scheme (https), optional credentials (user:pass), a host (example.com), an optional port (8080), a path (/path/page), a query string (key=value), and a fragment (section).

What is the difference between the host and the origin?

The host is the domain name or IP address, plus the port if one is given. The origin is the scheme, host, and port together, such as https://example.com:8080. Browsers use the origin for security rules like CORS and cookies.

How are repeated query parameters handled?

A key can appear several times, as in ?tag=a&tag=b. The table lists every occurrence in order and flags the repeated key. When you copy the parameters as JSON, repeated keys become arrays.

Is the fragment (#) sent to the server?

No. The fragment is only used by the browser, for example to scroll to a section or to pass data to a single-page app. Servers never receive it, which is why OAuth implicit flow put tokens there.

What if my URL has no https://?

The tool assumes https:// so that inputs like example.com/path or localhost:3000/api can still be parsed, and it tells you that the scheme was added.

Related Tools

  • URL Encoder / Decoder

    Percent-encode or decode URLs and query values, and unwrap double-encoded strings from logs in one click.

  • User-Agent Parser

    Identify the browser, operating system, device type, and bots from any User-Agent string, one or thousands at once.

  • cURL to Fetch / Axios

    Convert cURL commands, including Copy as cURL from DevTools, into JavaScript fetch() or axios code.

  • HTTP Status Codes

    Search every HTTP status code, from 200 OK and 404 Not Found to 418 I'm a teapot, with causes and fixes.