URL Parser & Query String Builder

Deconstruct URLs into protocol, host, port, path, and hash segments with an interactive query parameters table for adding, editing, sorting, and rebuilding clean URLs.

Query Parameters Table

(0 active)
No query parameters found. Click "Add Parameter" or paste a URL containing ?key=val

Path & Hash Editor

URL Breakdown

Protocol
https:
Hostname / Domain
developer.example.com
Port
8080
Pathname
/api/v2/products/search
Hash / Fragment
#results
Reconstructed URL Preview:
https://developer.example.com:8080/api/v2/products/search#results
Pure Client-Side Local Memory Processing · Zero Data Upload

Usage Guide

  • 1. Paste any destination URL into the input field to automatically deconstruct protocol, host, port, path, query, and hash fragments.
  • 2. Add, modify, toggle, or alphabetically sort query parameter key-value pairs in the interactive table with auto percent-encoding.
  • 3. Copy the rebuilt clean URL or export query parameters directly to JSON Formatter or Code Generator.

Security & Privacy Guarantee

  • 1. Fully compliant with WHATWG URL and RFC 3986 specifications, parsing IPv4/IPv6, custom ports, and multi-tier subpaths.
  • 2. Features parameter enable/disable toggles to test redirect behaviors without losing configured parameters.
  • 3. 100% client-side JavaScript execution; URLs containing sensitive API tokens and credentials never leave your browser.

Frequently Asked Questions

Q: Why do certain special characters in URLs become percent-encoded (e.g. %20 or %3F)?
A: RFC 3986 reserves delimiters like ?, &, /, and = for URL structural syntax. Special characters inside parameter values must be percent-encoded to prevent parsers from misinterpreting them as structural delimiters.
Q: What happens when I uncheck or toggle a query parameter in the table?
A: Unchecked parameters are temporarily excluded from the reconstructed URL preview without being deleted from your working session, making it easy to test various parameter combinations.
Q: Is the URL hash/fragment (#) sent to the web server?
A: No. According to HTTP specifications, the fragment identifier following '#' is processed entirely on the client side for page anchor navigation or Single Page Application (SPA) routing, and is never transmitted in HTTP request headers.
Q: How do I use this tool to debug OAuth 2.0 redirects or UTM marketing campaigns?
A: Paste complex URLs containing redirect_uri, state, code, or utm_source parameters. The table instantly separates and decodes nested values, making typos and double-encoding issues immediately visible.