Input
Preparing your workspace…
How to use
- Paste an absolute URL, or supply Base URL for a relative path.
- Inspect components and switch query values between encoded and decoded views.
- Copy a component or parameter, or download the parsed JSON.
Separating a URL into components
A URL combines several kinds of information: scheme, authority, path, query and fragment. Separating them can expose an unexpected port, repeated parameter or encoded value.
This parser uses the browser URL implementation. Its normalized representation can differ from the input spelling, which is useful to understand before reusing a component.
Components and query pairs
The component list separates the host, port, path and other URL fields. The query table retains repeated names as separate rows in their original order.
Decoded query values follow URLSearchParams behavior: a plus sign becomes a space, while %2B represents a literal plus sign. The encoded view helps inspect the source representation.
https://example.com:8443/docs/hello%20world?tag=api&tag=web&query=hello+world&empty=#overviewhostname: example.com
port: 8443
pathname: /docs/hello%20world
tag: api
tag: webExample data only. Values, authentication and endpoint behavior must be checked in your own context.
Normalization and base URLs
The URL standard can normalize hostname case, default ports and dot segments. Relative input needs an explicit base; the parser does not guess a destination from this website’s address.
Reusing parsed values
Each Copy button exports its associated value, and the query copy follows the selected encoded/decoded view. JSON download includes the parsed data, including URL credentials if supplied; on-screen masking is not redaction of an export.
Local tools accept up to 1 MiB, URLs up to 64 KiB, and have a 5-second processing limit. API requests support 100 headers and 100 parameter rows, a 1–120 second timeout and up to 5 MiB of received response data. Long text previews are abbreviated. Requests go directly to your chosen endpoint; CORS and browser policy apply.
Frequently asked questions
Why does the normalized URL differ from the input?
The URL implementation normalizes some fields, including hostname case, internationalized hostnames, default ports and relative path segments.
Are duplicate query names retained?
Yes. Every pair gets a separate row in order, rather than overwriting an earlier value with the same name.
Why did a plus sign become a space?
Query decoding uses form-style rules. A literal plus in a decoded query value is represented by %2B in the encoded source.
Does parsing open the destination URL?
No. It parses the string locally and does not fetch the URL or check whether the destination is reachable.
Are masked credentials removed from downloaded JSON?
No. Masking affects the display. The JSON contains the parsed URL data, so review it before saving or sharing.