URL Anatomy
Every URL follows a standard structure defined by RFC 3986: protocol://host:port/path?query#fragment. The protocol (http, https, ftp) defines how to connect. The host identifies the server. The optional port overrides the default (443 for HTTPS, 80 for HTTP). The path locates the resource. Query parameters pass key-value data. The fragment points to a section within the page.
Use Cases for URL Parsing
✓Debugging API endpoints — understand exactly what parameters are being sent
✓Analyzing redirect chains — see where OAuth callbacks and deep links go
✓Inspecting analytics URLs — decode UTM parameters and campaign tracking
✓Building API requests — construct URLs from individual components
✓Understanding encoded query strings — see decoded parameter values
Query Parameter Management
Query parameters are the most frequently inspected part of a URL. This tool shows each parameter as an editable key-value pair with the value automatically decoded. You can add new parameters, remove existing ones, reorder them with arrow buttons, and copy all parameters as a JavaScript object or URLSearchParams code.