URL Parser
Break any URL into protocol, host, port, path, query string, and fragment, with each query parameter listed individually for easy copying.
Native URL APIQuery paramsClient-sideFree to use
Paste any URL above to break it into its components.
How to use
- Paste a URL. Drop any absolute URL into the input field.
- Read the parts. Protocol, host, port, path, search, and hash are listed live.
- Copy what you need. Each component and each query parameter has its own copy button.
Common use cases
- Decoding UTM and tracking parameters from a campaign URL
- Inspecting OAuth callbacks and signed URLs
- Pulling fields out of an otpauth:// URI
- Verifying the host and path of a third-party redirect
Frequently asked questions
- What is this tool best used for?
- The URL parser is most useful for pulling apart long, messy URLs from analytics reports, OAuth callbacks, signed S3 links, or campaign tracking systems. Rather than mentally parsing a URL with a dozen query parameters, you can paste it and instantly see each component and parameter in a labeled table.
- Which standard does the parser follow?
- Parsing uses the WHATWG URL standard, which is the same specification implemented by all modern browsers and Node.js. This means the tool handles protocol normalization, percent-encoding, IDN hostnames, and edge cases the same way a browser would.
- Does this tool send my URL to a server?
- No. Parsing runs entirely in your browser using the built-in URL API. The URL you paste is never transmitted to any external service.
- Why is the fragment (the #hash part) not sent to the server?
- By design in the HTTP specification, the fragment identifier is processed entirely by the browser and is never included in the request sent to the server. It is used for in-page navigation, single-page app routing, and client-side state. Because servers never see it, it appears in this tool's output for your reference only.
- Why does the tool not accept relative URLs?
- A relative URL like /path?foo=bar is only meaningful in the context of a base URL. Without knowing the origin, the parser cannot determine the protocol, host, or full path. Paste the full absolute URL (including https://) and the parser will decompose every component correctly.
- How are percent-encoded query parameter values displayed?
- Query parameter keys and values are percent-decoded before being shown in the table. For example, %20 is shown as a space and %2F as a forward slash. This makes the table human-readable. If you need the raw encoded form, copy the full query string component directly.
Related tools
How to use
- Paste a URL. Drop any absolute URL into the input field.
- Read the parts. Protocol, host, port, path, search, and hash are listed live.
- Copy what you need. Each component and each query parameter has its own copy button.
Common use cases
- Decoding UTM and tracking parameters from a campaign URL
- Inspecting OAuth callbacks and signed URLs
- Pulling fields out of an otpauth:// URI
- Verifying the host and path of a third-party redirect
Frequently asked questions
- What is this tool best used for?
- The URL parser is most useful for pulling apart long, messy URLs from analytics reports, OAuth callbacks, signed S3 links, or campaign tracking systems. Rather than mentally parsing a URL with a dozen query parameters, you can paste it and instantly see each component and parameter in a labeled table.
- Which standard does the parser follow?
- Parsing uses the WHATWG URL standard, which is the same specification implemented by all modern browsers and Node.js. This means the tool handles protocol normalization, percent-encoding, IDN hostnames, and edge cases the same way a browser would.
- Does this tool send my URL to a server?
- No. Parsing runs entirely in your browser using the built-in URL API. The URL you paste is never transmitted to any external service.
- Why is the fragment (the #hash part) not sent to the server?
- By design in the HTTP specification, the fragment identifier is processed entirely by the browser and is never included in the request sent to the server. It is used for in-page navigation, single-page app routing, and client-side state. Because servers never see it, it appears in this tool's output for your reference only.
- Why does the tool not accept relative URLs?
- A relative URL like /path?foo=bar is only meaningful in the context of a base URL. Without knowing the origin, the parser cannot determine the protocol, host, or full path. Paste the full absolute URL (including https://) and the parser will decompose every component correctly.
- How are percent-encoded query parameter values displayed?
- Query parameter keys and values are percent-decoded before being shown in the table. For example, %20 is shown as a space and %2F as a forward slash. This makes the table human-readable. If you need the raw encoded form, copy the full query string component directly.