URL parser

Client

Redirect logs, OAuth callbacks, and webhook configs often paste long URLs with query strings. This page uses the browser URL API to list each component—if you omit https://, we assume it for parsing. Pair with URI encoding or query string → JSON when you need to transform values next.

What this does

The browser URL API splits an absolute link into protocol, host, port, pathname, query string, and fragment. Parsing is local—no HTTP request—so redirect URLs and API bases stay on your machine.

Privacy: parsing uses the built-in URL API in your tab. Toolcore does not fetch the link or log it on a server.
?

Paste an absolute URL, or a host/path without a scheme—we prepend https:// for parsing when no scheme is present. Relative paths (e.g. /only/path) need a base URL and are not supported here.

Result

Need percent-encoding on query values? Try URI encoding or query string → JSON.

href
https://api.example.com:8443/v1/search?q=toolcore&page=2#results
origin
https://api.example.com:8443
protocol
https:
host
api.example.com:8443
hostname
api.example.com
port
8443
pathname
/v1/search
search
?q=toolcore&page=2
hash
#results

Query parameters

  • q=toolcore
  • page=2

Nearby workflows on Toolcore

Common use cases

  • Split an OAuth redirect or webhook callback into host, path, and query keys before wiring your app.
  • Confirm which port and pathname an API client targets when debugging environment-specific base URLs.
  • List duplicate or empty query parameter values copied from analytics or ad platform URLs.
  • Compare encoded query strings with decoded values after using the URI encoding tool.

Common mistakes to avoid

  • Expecting this page to fetch the URL

    Parsing is local only—no HTTP request is made. Status codes and response bodies require your own client.

  • Pasting only a relative path

    Relative URLs need a base; paste a full URL or host/path so we can prepend https:// when the scheme is missing.

  • Sharing URLs that embed passwords

    user:pass@ in the authority is shown in plain text here—redact before screenshots or support tickets.

FAQ

Does Toolcore request the URL?

No—the breakdown runs entirely in your browser tab.

Why was https:// added?

Many pastes omit the scheme (e.g. example.com/path). We prepend https:// so the URL API can parse host and path; the note appears in the result.

How is this different from the slug generator?

The slug tool builds a single path segment from a title. This page dissects an existing absolute URL into standard components.

Common search terms

Phrases people search for that match this tool. See the full long-tail keyword index.

  • url parser online split query string
  • parse url protocol host path hash browser
  • url breakdown tool no fetch client side
  • decompose url components developer

More tools

Related utilities you can open in another tab—mostly client-side.