๐Ÿ”’ Runs in your browser โ€” nothing is uploadedโœ“ Free, no signup

URL Parser & Query String Parser

Paste a URL to break it into protocol, host, port, path, query parameters and hash โ€” with every parameter decoded into a readable table and JSON.

When should you use the URL Parser?

  • Reading a long tracking or redirect URL with dozens of parameters
  • Debugging API requests and OAuth callback URLs
  • Extracting query parameters as JSON for a script or test

How to use the URL Parser

  1. 1

    Paste a URL

    Paste a full URL, a URL without https://, or just a query string like ?a=1&b=2.

  2. 2

    Read the parts

    See protocol, credentials, host, port, path, query and fragment separately.

  3. 3

    Check parameters

    Every query parameter is listed with its decoded value. Repeated parameters appear once per value.

  4. 4

    Copy as JSON

    Copy all the parts and parameters as JSON.

Examples

Parsing a product URL

URL

https://shop.example.com:8443/shoes?color=red&q=running%20shoes#reviews

Parts

Host      shop.example.com:8443
Path      /shoes
Params    color = red
          q = running shoes
Fragment  #reviews

Common errors and how to fix them

That doesn't look like a valid URL
Include a domain name. Spaces and some special characters must be percent-encoded โ€” use the URL Encoder if needed.
A parameter value looks cut off
An unencoded & or # inside a value splits it. The sender should encode those characters as %26 and %23.
Related tools:ย URL Encoder & Decoder ยท JSON Formatter ยท Base64 Encoder & Decoder

More from Web & Network

Free tools that run in your browser โ€” no signup, nothing uploaded.

URL Parser FAQ

A URL has a protocol (https:), optional username and password, a host (domain and port), a path (/products), a query string (?color=red) and a fragment (#reviews).

Yes. Paste something like ?a=1&b=2 or a=1&b=2 and the parameters are listed and decoded.

Yes. Percent-encoded values like %20 and + are decoded to readable text in the table and JSON.

Each occurrence is listed in the table, and in the JSON output repeated keys become an array, such as "tags": ["sale", "new"].

The part after #. Browsers use it to jump to a section of the page or for client-side routing, and never send it to the server.

No. Parsing happens in your browser โ€” useful for URLs that contain tokens or personal data.