URL Parser
Break down any URL into its components: protocol, host, port, path, query parameters, and hash.
How to use
- 1 Paste any URL into the input field.
- 2 The tool instantly breaks it into components: protocol, hostname, port, pathname, query parameters, and hash.
- 3 Query parameters are listed individually in a table for easy reading.
- 4 Useful for debugging complex URLs with many query parameters.
Key features
- Breaks any URL into protocol, host, port, pathname, query string, and hash
- Lists all query parameters individually in a readable table
- Handles complex URLs with multiple encoded parameters
- Useful for debugging redirects, OAuth flows, and API callback URLs
What is URL Parsing?
A URL (Uniform Resource Locator) is more than just an address — it's a structured string composed of multiple components: protocol, hostname, port, path, query parameters, and fragment. URL parsing is the process of breaking this string into its constituent parts so you can inspect, debug, or manipulate each piece independently.
Modern web applications handle URLs constantly — building API requests, parsing redirect targets, extracting OAuth callback parameters, reading tracking codes from campaign URLs, or debugging malformed links. This tool takes any URL and instantly displays every component in a clear table, including a searchable list of query parameters.
All parsing happens entirely in your browser using the native URL API — no data is sent to any server. Every component is extracted client-side and you can copy each value individually with one click.
Common Use Cases
Debug malformed URLs
Paste a broken URL to identify which component is wrong — missing protocol, invalid port, or malformed query parameters are instantly visible.
Inspect API request URLs
Break down complex REST API URLs to verify endpoint, path parameters, and query strings when debugging integration issues.
Extract OAuth callback parameters
OAuth flows redirect users with tokens and state parameters in the URL. Paste the full callback URL to extract each parameter in plain text.
Debug SPA routing issues
Single-page apps use hash fragments for client-side routing. Parse the URL to see how the hash is structured and debug routing problems.
Verify URL manipulation logic
Before writing code that builds or modifies URLs, use this tool to confirm the resulting structure matches your expectations.
Security audit of redirect URLs
Check that redirect URLs point to the expected origin and path. Detects open redirects, protocol mismatches, or unexpected query injections.
Parse tracking and campaign URLs
UTM parameters, referral codes, and campaign tags are embedded in query strings. Parse any marketing URL to see all parameters in one view.
Learn URL anatomy
New developers can paste any URL to see how it breaks down into components — the best way to understand URL structure is visual inspection.
URL Structure Reference
Every URL follows the same general structure. Here is what each component represents.
| Component | Example | Description |
|---|---|---|
| Protocol | https:// | Determines how the data is transmitted. Common values: http, https, ftp, mailto. |
| Host | example.com:8080 | The combination of hostname and port. If no explicit port is specified, the default for the protocol is used (443 for HTTPS, 80 for HTTP). |
| Hostname | example.com | The domain name or IP address (without the port). This is what DNS resolves to locate the server. |
| Port | 8080 | A numeric identifier for a specific process on the server. If omitted, the browser uses the protocol's default port. |
| Pathname | /products/123 | Identifies the specific resource on the server. Hierarchical structure separated by forward slashes. |
| Query String | ?page=2&sort=asc | Key-value pairs that carry additional parameters — search queries, filters, pagination, or tracking data. Starts with ? and pairs are separated by &. |
| Hash / Fragment | #section | References a specific section or state within the page. Fragments are never sent to the server — they are handled entirely by the browser. |
| Origin | https://example.com:8080 | The combination of protocol + hostname + port. Used by browsers for the same-origin policy that controls CORS and security boundaries. |
URL Encoding (Percent-Encoding)
Certain characters are not allowed in URLs — spaces, Unicode characters, and symbols that have special meaning like ?, &, and #. URL encoding replaces these with a % followed by their hexadecimal character code. For example, a space becomes %20 and a literal # becomes %23.
When you parse a URL with this tool, the query parameters are already decoded for readability. This means you'll see the actual values as intended — spaces, special characters, and non-ASCII characters are displayed in their human-readable form rather than their percent-encoded representation.
If you need to encode or decode a URL manually — for example, preparing a parameter for an API call or debugging an encoded redirect — use the URL Encoder / Decoder tool. It works in both directions: encode plain text to percent-encoded format, or decode percent-encoded strings back to readable text.