No query parameters
A URL (Uniform Resource Locator) is the address of a resource on the Internet. A standard URL consists of multiple components in the format: protocol://user:pass@host:port/path?query#hash. Each part has a specific meaning and purpose, and understanding these components is essential for web development, API debugging, and link analysis.
Protocol: Specifies the protocol used to access the resource, such as HTTP, HTTPS, FTP, or FILE. HTTPS encrypts transmission via TLS/SSL and is the standard for modern websites.
Host: The domain name or IP address that identifies the server hosting the resource. Examples: www.example.com or 192.168.1.1.
Port: The service port on the server. HTTP defaults to 80, HTTPS to 443. Non-standard ports are explicitly specified, e.g., :8080.
Path: The specific location of the resource on the server, separated by /. Example: /blog/2024/article.html.
Query Parameters: Key-value pairs starting with ? and separated by &, used to pass additional data to the server. Example: ?page=2&sort=date.
Fragment (Hash): A fragment identifier starting with #, used client-side to navigate to a specific section within a page.
This URL parser and builder is simple yet powerful. Here is a detailed guide:
Parsing URLs: Paste or type any complete URL in the top input box (supports HTTP, HTTPS, FTP, and more). Click Parse URL or press Enter. The tool breaks the URL down into protocol, host, port, path, query parameters, and fragment. Each component can be copied individually.
Viewing Query Parameters: If the URL contains query parameters, the tool automatically extracts them into a key-value table. You can add new parameters, modify values, or delete unwanted ones, then click Rebuild URL to generate the updated link.
Building URLs: Switch to the Build URL tab, enter the protocol, host, path, and other components, then click Build URL to assemble the complete link. This is especially useful for constructing API request URLs or testing different parameter combinations.
Encode Helper: Switch to the Encode Helper tab, enter Chinese or special characters, and convert them to URL-encoded format (%XX). Supports both encodeURI and encodeURIComponent modes for different encoding needs.
URL parsing and building are widely used in web development and everyday browsing. Here are some typical scenarios:
API Debugging and Testing: Backend developers frequently need to analyze third-party API request URLs to extract the endpoint path and query parameters. This tool quickly disassembles complex API URLs so you can clearly see each parameter's purpose without manually parsing them.
UTM Parameter Analysis: Marketers use UTM parameters (utm_source, utm_medium, utm_campaign) to track traffic sources. Paste a UTM-tagged link into the tool to view all UTM parameters and their values at a glance, making it easy to verify and optimize campaigns.
Link Cleaning and Reconstruction: Social media sharing links often contain lengthy tracking parameters. Use this tool to parse the link, remove unnecessary parameters, and rebuild a clean short link that is easier to share and protects privacy.
URL Encoding Principle: URLs only allow printable ASCII characters. For Chinese characters, spaces, special symbols, and more, percent-encoding converts them into %HH format. For example, a space encodes as %20 (or + in application/x-www-form-urlencoded). encodeURI encodes the entire URL while preserving protocol and domain special characters; encodeURIComponent encodes individual parameter values more strictly.
URL Canonicalization: The same resource may correspond to multiple URL variants (with/without www, case differences, extra slashes, etc.). Search engines use canonicalization to determine the single indexed version. The components extracted by this tool help developers check whether a link conforms to best practices.
Related Standards: Modern URL specification is based on the WHATWG URL Standard, which is closer to actual browser behavior than the traditional RFC 3986. JavaScript's URL and URLSearchParams APIs are built on this standard, supporting IDN internationalized domain names (punycode conversion) and IPv6 address parsing.
No. All parsing and building operations are performed locally in your browser using the native JavaScript URL API. Your URL data never leaves your device.
HTTP, HTTPS, FTP, FTPS, FILE, DATA URI, and any other URL format recognized by the browser, including those with username/password, port numbers, complex query parameters, and fragments.
Paste your URL and the tool automatically extracts all query parameters into an editable table. You can modify values, add new parameters, or delete existing ones. Click Rebuild URL to generate the updated link.
URL encoding (Percent-Encoding) converts non-ASCII characters and special symbols into %XX format for safe transmission in URLs. UTF-8 is a character encoding standard. This tool applies URL encoding to query parameter values so special characters like Chinese text, spaces, and & are transmitted correctly.
Yes. In the Build URL tab, enter a relative path (e.g., /path/to/page?a=1) and the tool will resolve it into a full URL based on the current page.
The browser's URL API omits the default port for standard protocols (HTTP=80, HTTPS=443). Non-standard ports like 8080 or 3000 will be displayed normally.
Each component in the parsed results has a Copy button on the right side. Click it to copy that component (e.g., hostname, path, or full query string) to your clipboard.
Yes. The tool uses the standard URLSearchParams API and supports both repeated keys (a=1&a=2) and array syntax (a[]=1&a[]=2), displaying them in the parameter table.