Toolzavro
Browse tools

QUICK START

Loading tools…
Find tools by name or task Esc to close

URL Parser

Inspect a URL's scheme, host, port, path, fragment and repeated query parameters as JSON. Parsing does not visit the address or test website availability.

Separate a complete URL into its components when debugging a link or query string. The browser URL parser normalizes the address and the result retains repeated query entries as an ordered list. This is a parsing operation, not a request to the website or a safety verdict.

  • 100% free
  • No registration
  • On your device
  • Modern browser
  1. 1Enter details
  2. 2Adjust options
  3. 3View result

Inspect URL components and repeated query parameters locally. Your input stays on this device.

ResultIdle
Your result will appear here.

Your input stays on this device for this operation. We don’t upload or store it.

About URL Parser

Separate a complete URL into its components when debugging a link or query string. The browser URL parser normalizes the address and the result retains repeated query entries as an ordered list. This is a parsing operation, not a request to the website or a safety verdict.

Component breakdown

Reports protocol, hostname, port, pathname and hash, plus any embedded username/password fields.

Repeated query entries

Retains multiple entries with the same parameter name instead of flattening them into one property.

JSON export

The formatted result can be copied or saved as url-parser.json.

How to use URL Parser

  1. 1

    Paste a complete URL

    Include the scheme, such as https://. Use a redacted example if the address includes credentials or private query values.

  2. 2

    Process the address

    Press Process to read normalized components and the query entry list.

  3. 3

    Inspect the JSON

    Compare repeated parameters, path and fragment, then copy the result or download url-parser.json.

Formats and practical limits

Input: a complete URL, up to 100,000 JavaScript string units. Output: normalized components and ordered query entries as JSON.

  • Parsing may normalize spelling, encoding and default ports; the output is not a byte-preserving copy of the original URL.
  • Embedded credentials and sensitive query values remain in the result. Redact them before sharing JSON or screenshots.

Practical example

For https://example.com:8443/a?tag=one&tag=two#summary, inspect port 8443, pathname /a, hash #summary and both tag entries in the query list.

Frequently Asked Questions

3 answers
Does parsing check whether a website is online?

No. The operation constructs a URL object; it does not fetch the address, resolve DNS or inspect a server response.

Why did an explicit port disappear?

The browser parser normalizes default ports. For example, HTTPS port 443 can be represented by an empty port field. Use a non-default port when testing that component.

Can I enter only /path?

This workspace supplies no base URL, so enter a complete absolute address. A relative path by itself does not meet that input requirement.

Related Developer tools

View all Developer tools

URL Encoder

Encode unsafe URL characters.

URL Decoder

Decode encoded URL strings.

New

QR Code Decoder

Decode QR codes from images or your camera locally.

New

Base32 Decoder

Decode Base32 into UTF-8 text.