URL & Query String Parser

Paste any URL to decompose it into components. Edit query parameters in a table. Convert between query strings, JSON, and reconstructed URLs. 100% client-side.

🟢📦 Query String →JSON

⬻ ☁️ JSON →Query String

🟢📖 How It Works

A URL (Uniform Resource Locator) has a defined structure per RFC 3986:

scheme://user:password@host:port/path?query#fragment
  • Schemehttps, http, ftp, ws, file, etc.
  • Host —domain name or IP address (e.g. www.jslet.com, 192.168.1.1)
  • Port —TCP port number (implicit from scheme if omitted: 443 for https, 80 for http)
  • Path —resource path (e.g. /json-formatter)
  • Query String —key-value pairs after ?, delimited by &
  • Fragment / Hash —anchor after #, never sent to the server

Common use cases: debugging API URLs, inspecting UTM tracking parameters, converting between percent-encoded and decoded query strings, preparing cURL requests, or generating JSON from query strings for programmatic use.