URL Parser & Inspector
Parse any URL into its components: protocol, hostname, port, pathname, query string parameters, and fragment. Decode URL-encoded values, inspect query parameters in a table, and get the normalized form of the URL.
Examples:
How to Use URL Parser & Inspector
- 1Paste or type any URL into the input field.
- 2The URL is parsed into protocol, hostname, port, path, query string, and fragment.
- 3Query parameters are displayed in a table with decoded keys and values.
- 4Copy individual components or the normalized URL.
Zenovay
Track your website performance
Real-time analytics, session replay, heatmaps, and AI insights. 2-minute setup, privacy-first.
Related Tools
JSON Formatter & ValidatorFormat, validate, and beautify JSON data with syntax highlighting and error detection.
JWT DecoderDecode and inspect JWT tokens. View header, payload, and verify signatures.
Base64 Encode/DecodeEncode text to Base64 or decode Base64 back to text. Supports UTF-8 and binary data.
URL Encode/DecodeEncode or decode URL components. Handle special characters, query strings, and full URLs.
Frequently Asked Questions
What are the components of a URL?▾
A URL (Uniform Resource Locator) has these parts: (1) Protocol/Scheme: https:// or http:// or ftp://. (2) Username and password (optional): user:pass@. (3) Hostname: the domain or IP address. (4) Port: the TCP port (omitted if default — 443 for HTTPS, 80 for HTTP). (5) Pathname: the path to the resource after the domain. (6) Query string: key=value pairs after ? separated by &. (7) Fragment: the #anchor portion, not sent to the server.
What is URL encoding?▾
URL encoding (percent-encoding) converts special characters into a % followed by two hex digits. For example, a space becomes %20, a colon becomes %3A. This is necessary because URLs can only contain a limited set of ASCII characters. Query string values often contain encoded characters — decoding them reveals the actual value. The encodeURIComponent() JavaScript function URL-encodes a value; decodeURIComponent() decodes it.
What is the difference between the path and query string?▾
The path (/products/shoes) identifies the resource being requested and is part of the URL structure. The query string (?color=red&size=10) passes additional parameters to the server and appears after a ?. Both are sent to the server. The fragment (#section2) is NOT sent to the server — it is processed entirely by the browser and used for in-page navigation. Search engines typically ignore fragments (with some exceptions).
How do duplicate query parameters work?▾
URLs can have multiple values for the same key: ?tag=red&tag=blue. How these are handled depends on the server framework. PHP uses tag[] syntax, Express.js parses them into an array, and some servers take only the last value. The URLSearchParams API in JavaScript supports getAll("tag") to retrieve all values for a key. This tool shows all duplicate parameters in the table.