URL Parser & Decoder
High-precision URL parser online. Deconstruct any web address into its logical components instantly.
No query parameters
Built With Care
“Parsing uses the browser's native URL constructor, so decomposition follows the WHATWG URL standard shared by Chrome, Firefox, and Safari. Missing ports resolve to the protocol default (443 for https, 80 for http), and query strings are extracted into key-value pairs with searchParams.”
URL Parser & Decoder
Paste any URL and see it split into protocol, hostname, path, port, and query parameters, with values decoded automatically. Use it to inspect tracking parameters, verify how a link decomposes, or confirm the exact pieces of a URL before writing code that consumes it.
- 1Paste a full URL or encoded string into the input field; parsing starts automatically.
- 2Review the protocol, hostname, path, and port cards on the left.
- 3Read the extracted query parameters as key-value pairs on the right.
- 4Click Decode URL to turn percent-encoded text into readable characters.
- 5Click Encode URL to percent-encode the whole string for safe transmission.
- 6Copy the full analysis as JSON for use in tests or support tickets.
- 7Input without http(s) is given an implicit https:// prefix before parsing, so a bare domain still decomposes completely.
- 8Read the port card closely: 443 or 80 appears when the URL omits the port, and the value is the protocol default rather than an explicit part of the string.
- Instant Decomposition: The URL splits into protocol, host, hostname, port, path, query, and hash.
- Query Parameter Extraction: Every key-value pair is listed from the search string automatically.
- One-Click Decode: Converts percent-encoded URLs into readable text.
- One-Click Encode: Percent-encodes a URL for safe use in requests and configuration.
- Default Port Resolution: Ports resolve to 443 for https and 80 for http when omitted.
- Copy as JSON: Exports the full parse as formatted JSON.
URL Parser & Decoder Specs
Limits
- Parses any RFC-3986 URL
- Also handles query-string expansion
Formats
- Output: scheme, host, port, path, query params, fragment
Defaults
- Decodes percent-encoded values
- Shows both raw and decoded
How it works
- URL API + custom query parser
Honest caveats
- Non-standard schemes parse leniently
- Malformed URLs show partial results with a warning
Real Ways People Use This
API Debugging
Break down endpoint URLs to inspect paths, query parameters, and auth tokens while troubleshooting requests.
Campaign Analysis
Extract UTM parameters from marketing links to see which campaign, source, and medium a URL carries.
Link Validation
Verify protocol, hostname, and port of redirects and canonical URLs before deploying them.
Security Inspection
Check where a suspicious link points and which parameters it carries without visiting the destination.
Encoding Troubleshooting
Diagnose double-encoded or malformed URLs that fail in scripts, configs, and third-party integrations.
Resource Request Inspection
Break down failing resource URLs reported in network logs to confirm the host, port, and query string before editing code, redirects, or CDN rules.
Redirect and Callback Validation
Check OAuth callback and webhook URLs for encoded state or query parameters before wiring them into an integration.
- Parsing reflects string structure only; it does not verify that the destination is safe or that the site exists.
- Percent-encoded parameters can hide redirects and payloads, so decode and read values before trusting a link.
- Small differences such as trailing slashes, case, or parameter order can change caching and analytics behavior.
- 1Confirm the protocol and hostname match the expected destination before using the URL.
- 2Decode the query string and scan for unexpected redirect or tracking keys.
- 3Re-encode any edited values before putting them back into production requests.