URL Parser
URL Parser
URL Parser breaks common URLs into protocol, hostname, port, path, and query parameters, then lets you edit each part and preview the rebuilt URL in real time.
Input URL
Auto add https:// when missing scheme
Details
Protocol
Hostname
Port
Username / Password
Username
Password
Pathname
Hash
Query parameters
0
No parameters
Output URL
Quick Start
Common Scenarios
API debugging
break down endpoint URLs, inspect or adjust query parameters, and quickly pinpoint parameter issues.
Link analysis
unpack complex marketing/tracking URLs to inspect UTM parameters, referrer sources, and more.
Parameter tuning
quickly add, remove, and edit paging, filtering, sorting, and other query parameters with less manual URL concatenation.
Link cleanup
remove unnecessary tracking parameters before sharing a cleaner URL.
Redirect troubleshooting
inspect redirect URLs and verify target host, port, and path.
Deep-link construction
assemble app deep links (including custom schemes) and preview the full URL instantly.
Usage Advice
Limitations & Compatibility
Privacy & Security
FAQ
A URL (Uniform Resource Locator) is an internet "address" used to locate resources on the web. A complete URL usually includes: • Scheme (protocol): for example https:, ftp:, mailto: • Auth info: user:pass@ (optional), often used in FTP/intranet scenarios • Hostname: domain name or IP address • Port: optional; HTTPS defaults to 443, HTTP defaults to 80 • Path (pathname): points to a specific resource • Query string: key-value pairs after ?, separated by & • Fragment (hash): anchor after #, used client-side only and not sent to the server For example, https://user:pass@example.com:8080/path?key=value#section contains all of the above parts. This tool mainly targets hierarchical URLs and relative paths; editing and reassembling non-hierarchical schemes like mailto:, data:, and file: are limited.
The tool will try to auto-complete it: with "Auto add https:// when missing scheme" enabled, it prepends https://; when disabled, it prepends http://. To test a specific scheme such as ftp: or custom:, enter the full scheme prefix directly. It only shows "Invalid URL" for malformed input.
Check these points: make sure each parameter key is not empty (rows with empty keys are ignored in output); and make sure you're editing the "Query parameters" section, not the "Input URL" box. Editing the input box re-parses the URL and can overwrite manual edits.
In standard URLs, query parameters after ? are sent to the server, while content after # is client-side only. This tool prioritizes parsing ?search; if search is empty and # contains ?, it parses those as hash query parameters.
Just enter the value directly; the tool will handle percent-encoding (URL encoding) automatically. For full-text encoding/decoding, use the companion tool "URL Encoder/Decoder".
Yes. Inputs like /api/data?id=1 are parsed in relative-path mode, so protocol and hostname remain empty.
Leaving it blank uses the scheme's default port (HTTPS 443, HTTP 80), and the port will be omitted from the output URL.