URL Parser

Parse a URL into scheme, host, port, path, query parameters, fragment, and origin — fully client-side

Input

Loading editor...

Output

Output will appear here...

What is URL Parser

Last reviewed: April 18, 2026

A URL (Uniform Resource Locator) is a web address that points to a resource like a page, API endpoint, or file, typically including scheme, host, path, and query.

URL Parser uses the WHATWG `URL` parser — the same engine used by browsers — to split any URL into its scheme, userinfo, host, port, pathname, query parameters, fragment, and origin.

It's ideal when you need to verify the structure of a URL, extract query parameters, or debug callback URLs from OAuth flows.

Why use it

Debug OAuth and SSO callback URLs.
Extract query parameters for logs and tests.
Verify canonical URL shapes before shipping.
Teach URL anatomy to new developers.
Decode complex parameter lists safely.

Features

WHATWG-compliant parser
Extracts scheme, host, port, path
Lists all query parameters
Shows origin & fragment
Local-only URL Parser processing keeps data in-browser

How to use URL Parser

Paste URL. Include the scheme (http / https).
Run. Review each URL component.
Copy parts. Use in tests, docs, or debugging sessions.

Example (before/after)

URL

https://user:[email protected]:8443/v2/items?q=books&page=2#top

Parsed

Scheme:    https
Username:  user
Password:  (set, hidden)
Host:      api.example.com
Port:      8443
Pathname:  /v2/items
Query:     ?q=books&page=2
Params:
  q = books
  page = 2
Fragment:  #top
Origin:    https://api.example.com:8443

Common errors

Missing scheme

URLs without http(s):// fail to parse.

Fix: Prepend the scheme before parsing.

Unencoded characters

Raw spaces or quotes cause errors.

Fix: URL-encode special characters first.

FAQ

Does it follow redirects?

No — this is a pure syntactic parser.

Is input uploaded?

No — parsing is fully client-side.

Does it decode query values?

Yes — `URLSearchParams` handles percent-decoding automatically.

Can it handle mailto: or custom schemes?

Yes — any WHATWG-parsable URL works.

Does it reveal passwords?

No — the password is detected but redacted in the report.

Related tools

Pair with URL encoder/decoder and HTTP tools. You can also browse the full Networking & DNS category for more options.

URL Encoder/Decoder

Encode or decode URL strings

HTTP Header Inspector

Paste response headers to audit HSTS, CSP, CORS, X-Powered-By disclosure, and Set-Cookie flags

CORS Origin Checker

Test whether origins are allowed by a given Access-Control-Allow-Origin value — wildcard and subdomain aware

User-Agent Parser

Parse a User-Agent string into browser, version, operating system, device type, and bot status

CIDR Calculator

Calculate network, broadcast, usable hosts, subnet mask, and wildcard for any IPv4 CIDR

Well-Known Ports Reference

Searchable list of well-known TCP/UDP ports — filter by port number, service name, or description

URL Extractor

Pull all HTTP / HTTPS URLs out of any text with trailing punctuation cleaned

URL Inspector

Inspect status, headers, redirects, and canonical hints for a URL

JWT Decoder

Decode and view JWT token payloads

JSON Formatter

Format, validate, and beautify JSON online with readable indentation, syntax checking, and copy-ready output for APIs, logs, and config files.

URL Opener

Open multiple URLs at once

URL Slug Length and Readability Checker

Check slug length, stop words, readability, and URL cleanliness for SEO-friendly article, category, and landing page paths.