URL Parser — Break Down URLs into Components Online

URL Parser dissects any HTTP, HTTPS, FTP, or other URL into its individual components: protocol, hostname, port, pathname, search string, and hash. Query parameters are listed individually as key–value pairs. Useful for debugging redirect chains, understanding API endpoints, and inspecting authentication callback URLs.

URL Component Breakdown

A URL (Uniform Resource Locator) has up to six distinct components: scheme (https:), authority (//user:password@host:port), path (/some/path), query (?key=value&key2=value2), and fragment (#section). The URL Parser extracts all of these and additionally splits the query string into individual key–value pairs, decoding each percent-encoded value.

The scheme defines the protocol: https for encrypted HTTP, http for plain HTTP, ftp for file transfer, mailto for email, ws/wss for WebSockets. The host is the domain name or IP address. The port is optional — if omitted, the default port for the scheme is used (443 for https, 80 for http). The path identifies the resource on the server. The query string carries parameters. The fragment (#) is processed only by the browser and is never sent to the server.

Debugging OAuth and Redirect URLs

OAuth authorization URLs pack a lot of information into the query string: client_id, redirect_uri, response_type, scope, state, nonce, and sometimes code_challenge. When an OAuth flow fails, the first debugging step is to paste the full authorization URL into the parser and inspect each parameter individually. Is the redirect_uri correct and properly encoded? Is the scope correct? Is the state parameter present?

Redirect chains in analytics and affiliate marketing also benefit from URL parsing. A tracked link may contain a destination parameter that is itself a fully percent-encoded URL. The parser shows the outer URL structure; decoding the destination parameter value with the URL Decoder reveals the inner URL. This is the "URL within a URL" pattern common in tracking pixels and ad click attribution.

Common Use Cases

Extracting query parameters from a complex URL
Checking the origin and pathname of a redirect URL
Understanding OAuth callback URLs with multiple parameters
Debugging webhook URLs in API integrations

Frequently Asked Questions

What does a URL parser do?

A URL parser splits a URL into its structural components: protocol (https:), host (example.com), port (443), pathname (/path), search (?foo=bar), and hash (#section). It also decodes individual query parameters.

Privacy & Security

This tool runs entirely in your browser using client-side JavaScript. No data is sent to a server — your input never leaves your machine. SmartDevBox has no account system, no usage tracking, and no paid tier. See the Privacy & Security page for full details.

URL DecoderDecode any percent-encoded URL string back to readable text instantly in your browser. Free, no sign-up, 100% client-side.
URL EncoderPercent-encode any string for safe use in URLs instantly in your browser. Free, no sign-up, 100% client-side.
Base64 DecoderDecode any Base64 string back to plain text instantly in your browser. Free, no sign-up, 100% client-side. Supports standard and URL-safe Base64.

Extract URLs from logsPull every URL out of noisy logs, then parse the important ones into scheme, host, path, query parameters, and fragments.
curl to Markdown docsTransform a copied terminal command into readable API documentation without leaking headers or tokens.