About

URL query strings are the nervous system of the web, carrying vital signals for tracking, state management, and API communication. However, as digital ecosystems grow complex, URLs often become nested wrappers - containing redirects, callbacks, and double-encoded payloads. Manual decoding is not just tedious; it is prone to invisible errors like %20 whitespace mismanagement or lost deep-link parameters.

This tool is engineered for Total Inspection. Unlike simple splitters, it employs a recursive parsing engine that detects URLs inside parameters (e.g., redirect_uri inside an OAuth flow) and unpacks them layer by layer. It automatically identifies industry-standard keys (UTM, GCLID, Facebook Pixel) and provides context-aware definitions. Whether you are a Data Scientist cleaning click-stream logs or a Backend Engineer debugging microservice chains, this utility guarantees zero-loss extraction.

Formulas

The parsing logic adheres to RFC 3986, decomposing the Uniform Resource Identifier (URI) into its atomic components. The structure is processed as follows:

{

URI = scheme : // authority path ? query # fragmentquery = key₁=value₁ & key₂=value₂

For recursive extraction, we define a heuristic function is_url(v) to detect nested encoded entities:

{

TRUE if decode(v) match /^https?:/FALSE otherwise

Reference Data

Parameter	Type	Standard Definition	Example Pattern
utm_source	Tracking	Identifies the advertiser, site, publication, etc.	google, newsletter
utm_medium	Tracking	Advertising medium (banner, email).	cpc, banner
gclid	Ad Tech	Google Click Identifier (Auto-tagging).	CjwKCAjw... (Base64)
fbclid	Ad Tech	Facebook Click Identifier.	IwAR0...
q / query	Search	Standard search query parameter.	keyword
redirect_uri	Auth	OAuth 2.0 callback URL (often nested).	https%3A%2F%2F...
code	Auth	Authorization code for token exchange.	4/P7q...
limit	API	Pagination: Number of items per page.	10, 50
offset	API	Pagination: Number of items to skip.	0, 100
ref / referrer	Analytics	Originating page or source.	homepage

Frequently Asked Questions

Many modern URLs (especially in AdTech and OAuth flows) contain other URLs as parameter values. For example, a "redirect_uri" might contain a full URL that itself has query parameters. Our engine detects these patterns, decodes the value, and triggers a sub-parse routine, presenting the data in a nested tree structure rather than a flat string.

Yes. Switch the input mode to "Bulk". You can paste a list of thousands of URLs (one per line). The tool will aggregate all unique keys found across the dataset and generate a consolidated CSV or JSON report.

The tool strictly adheres to standard "&" and ";" delimiters as per W3C recommendations. However, it also attempts to heal malformed query strings where possible (e.g., missing "?" separators) by using heuristic RegEx pattern matching.

No. All parsing happens locally in your browser's JavaScript runtime. No URL data is ever transmitted, ensuring full privacy for sensitive API tokens or PII.