Utility Tools
Use this URL parser to audit campaign links, redirects, QR destinations, support tickets, and copied URLs before sharing, documenting, or debugging them.
Live analyzer
https://toolkitshelf.com/tools/qr-code-generator?utm_source=newsletter&utm_medium=email&utm_campaign=spring-launch&utm_content=hero-button&table=12&table=patio#menu
The URL is parsed with the browser URL API.
Duplicate keys: table.
UTM fields are highlighted so campaign links are easier to audit.
newsletteremailspring-launchhero-button12patio{
"url": "https://toolkitshelf.com/tools/qr-code-generator?utm_source=newsletter&utm_medium=email&utm_campaign=spring-launch&utm_content=hero-button&table=12&table=patio#menu",
"protocol": "https:",
"origin": "https://toolkitshelf.com",
"host": "toolkitshelf.com",
"pathname": "/tools/qr-code-generator",
"queryString": "utm_source=newsletter&utm_medium=email&utm_campaign=spring-launch&utm_content=hero-button&table=12&table=patio",
"hash": "menu",
"params": [
{
"key": "utm_source",
"value": "newsletter",
"duplicate": false,
"empty": false,
"utm": true
},
{
"key": "utm_medium",
"value": "email",
"duplicate": false,
"empty": false,
"utm": true
},
{
"key": "utm_campaign",
"value": "spring-launch",
"duplicate": false,
"empty": false,
"utm": true
},
{
"key": "utm_content",
"value": "hero-button",
"duplicate": false,
"empty": false,
"utm": true
},
{
"key": "table",
"value": "12",
"duplicate": true,
"empty": false,
"utm": false
},
{
"key": "table",
"value": "patio",
"duplicate": true,
"empty": false,
"utm": false
}
]
}This inspector runs in the browser. URLs can contain readable campaign labels, search terms, tokens, emails, or customer details, so remove sensitive values before sharing parsed output.
Quick answer
URL Parser / Query String Inspector generates parsed URL parts and query parameters from URL or domain, query string, URL parameters, UTM parameters, hash fragment and path. The visible generation method is Parsed URL = browser URL parts + decoded query rows + duplicate, empty, UTM, credential, hash, and length checks.
Generation method
Parsed URL = browser URL parts + decoded query rows + duplicate, empty, UTM, credential, hash, and length checksThe inspector uses the browser URL parser. It can assume https:// for bare domains, but destination behavior still depends on the real server and redirect chain.
How to use
Example
Generator use
Before relying on it
Details
These notes make the assumptions explicit, especially where the same search query can mean slightly different things.
Each query parameter is shown in the order it appears, with raw duplicate and empty-value signals preserved.
Common UTM fields are detected so campaign links can be reviewed before they become ads, QR codes, emails, or partner URLs.
Copy the whole normalized URL for testing, the query string for quick edits, or structured output for issue tickets and QA notes.
Benchmarks
This generator is a drafting aid, not a fixed rule. Use the output to compare options and document your assumptions. Benchmark ranges are broad planning heuristics unless this page names a specific source for the range.
Verify source, medium, campaign, and creative labels before creating ads, emails, or QR codes.
Some systems support duplicate keys and others only read the first or last value, so duplicates deserve a quick check.
Very long URLs can work, but redirects, QR codes, print layouts, and messaging apps may behave differently.
Method and limitations
The generation method, inputs, example, and limitations are shown so the draft output is checkable, not treated as final copy.
Parsed URL = browser URL parts + decoded query rows + duplicate, empty, UTM, credential, hash, and length checks
URL or domain, Query string, URL parameters, UTM parameters, Hash fragment, Path
Utility outputs depend on the encoded payload, file format, target app, scanner, printer, browser, and real-world testing before sharing.
June 6, 2026
Toolkit Shelf. URL Parser / Query String Inspector. Last reviewed June 6, 2026. https://toolkitshelf.com/tools/url-parser-query-string-inspector
FAQ
It separates the URL into protocol, host, path, query string, hash, and individual query parameters so you can inspect what will be sent or shared.
Duplicate keys can be intentional, but platforms differ on whether they keep all values, the first value, or the last value. Flagging them makes campaign and redirect links easier to QA.
No. This tool parses the URL text you paste. It does not fetch the URL or follow redirect chains.
Use the page notes for each tool. Browser-side utilities can generate outputs locally, but the final file or code may still reveal whatever you encode or share.
Scanners, printers, file viewers, apps, and platform previews can behave differently, so test the exact downloaded output before using it publicly.
Different tools may use different rounding, assumptions, default rates, methods, formulas, or input timing. Compare the visible method and inputs before relying on the output.