Encoding
URL Encode
Percent-encode text so it can be safely used inside a URL.
Developer
URL Parser
Paste any URL and instantly see its protocol, host, port, path segments, query parameters, and fragment — with values URL-decoded and ready to copy.
Tool Summary Answer Block
This tool accepts structured input and returns deterministic output in the browser with no server upload.
- Tool name
- URL Parser
- Input intent
- Provide source content to transform, validate, or analyze.
- Output intent
- Receive normalized output suitable for copy, reuse, or debugging.
- Example input
- https://example.com:8443/blog/post-1?utm_source=email&ref=newsletter#share
- Example output
- protocol: https host: example.com:8443 path: /blog/post-1 query: utm_source=email, ref=newsletter hash: #share
URL components
- Protocol
- https
- Origin
- https://shop.example.com:8443
- Hostname
- shop.example.com
- Port
- 8443
- Path
- /products/widget
- Hash
- #reviews
Path segments (2)
- 1products
- 2widget
Query parameters (3)
| Key | Value | Actions |
|---|---|---|
| utm_source | ||
| utm_campaign | spring sale | |
| ref | newsletter |
JSON view
Tool Introduction
Paste any URL and instantly see its protocol, host, port, path segments, query parameters, and fragment — with values URL-decoded and ready to copy.
Tool Overview
Most URLs hide a lot of structure: subdomains, ports, encoded path segments, repeated query keys, and a fragment that may itself contain key/value pairs. This tool runs your input through the standard WHATWG URL parser, then expands every part into a labelled, copyable view. Query parameters are listed in the order they appear, with their values URL-decoded. Path segments are split on / and decoded too. A read-only JSON view makes it easy to drop the parsed result into a script or test fixture.
Use Cases
- Debug redirects and tracking URLs by inspecting every UTM and query parameter.
- Extract a deep link’s path segments to validate a route in your app.
- Convert a stringy URL into a structured object for a test fixture.
Input/Output Examples
Input Intent
https://example.com:8443/blog/post-1?utm_source=email&ref=newsletter#share
Output Intent
protocol: https host: example.com:8443 path: /blog/post-1 query: utm_source=email, ref=newsletter hash: #share
FAQ
What if my URL is missing the scheme?+
The parser requires a scheme. If you paste www.example.com without https://, it will report an error. Add the scheme and try again.
Are query values URL-decoded?+
Yes. Values are decoded so you see the human-readable form, but the original encoded value is also shown.
Does it support internationalized domains (IDN)?+
Yes. Unicode hostnames are accepted; if you need to round-trip them through punycode, use the IDN Punycode Converter.
Explore More Tools
Discover related utilities in the Developer category below.
Related tools
Handpicked utilities you might find useful