URL Parameters to JSON
Paste a full URL or a raw query string and convert URL parameters into a JSON object.
Duplicate parameters are grouped into arrays, making it easy to inspect
how query values are actually passed to applications and APIs.
This tool helps you quickly understand request parameters, debug API calls, and verify generated URLs during development or testing.
All values are output as strings, exactly as they appear in the URL, so the original text is never altered.
All parsing and formatting are performed locally in your browser.
No URLs or parameter data are sent to any server, allowing you to safely inspect query strings without exposing sensitive information.
Read with types and nesting
Read the URL or query above with options: turn numbers and true / false into real types, and rebuild a[b]=1 and a[]=1 into nested objects and arrays.
JSON → query string
Turn a JSON object into a query string. Nested objects use a[b]=1; arrays follow the format you choose.
GuideHow to use & features
- Paste a query string and click “To JSON” to see a formatted object view.
- Provide JSON input and click “To URL params” to generate a query string.
- Copy the generated output instantly; encoded values are preserved as-is.
- Even large parameter sets are processed entirely in the browser with no uploads.
SamplesSample input & output
Extract query params
https://example.com/search?q=devtoolkits&lang=en
{
"q": "devtoolkits",
"lang": "en"
}FAQFAQ
What happens when a parameter name appears more than once?
If a key such as `tag=a&tag=b` appears two or more times, it is grouped into an array: `"tag": ["a", "b"]`. A key that appears once stays a string.Do numbers and true become numbers and booleans?
No. All values are output as strings, so `page=2` becomes `"page": "2"`. A URL query string has no types, so the original text is kept.What input does it accept?
A full URL such as `https://example.com/path?a=1`, a URL without a scheme such as `example.com/path?a=1`, or just a query string such as `?a=1&b=2` or `a=1&b=2`. For a URL, everything after `#` (the fragment) is ignored. When pasting only a query string, leave out anything after `#`.What happens to `%E3%81%82` and `+`?
Percent-encoding is decoded back to the original characters and `+` is read as a space, so non-ASCII parameters come out readable.What about `items[]=1&items[]=2`?
The key stays `items[]` and its value becomes the array `["1", "2"]`. Notation such as `items[0]` or `user[name]` is not expanded into nested structures.Is the URL I enter sent anywhere?
No. Conversion happens entirely in your browser, so URLs that contain tokens or email addresses are not sent out.
Use casesCommon use cases
Checking an API request's query
List parameters such as `filter`, `sort` and `page` from a long URL as JSON and confirm they are passed as intended.Inspecting UTM and other tracking parameters
Quickly pull out `utm_source`, `utm_medium`, `utm_campaign` and similar parameters from ad or email links.Reading an OAuth redirect URL
Extract `code`, `state` and `error` from a callback URL to narrow down where the authorization flow failed.Reusing a query as test data or an API client body
Turn a URL query into JSON to use as a request body or as the starting point for a test fixture.
NotesNotes & limitations
All values are strings
Numbers and `true` / `false` are output as strings. Convert them in the code that receives them if you need types.`items[]` and `user[name]` are not expanded
The array and nesting notation used by PHP or Rails keeps its key name as written. Tidy the output by hand if you need structured JSON.The type depends on how many times a key appears
A key that appears once is a string; two or more times, an array. Be careful if your code reads a parameter as an array but it may arrive only once.The path and fragment are not converted
The URL path (such as `/users/42`) and everything after `#` are ignored. Only the query string after `?` is extracted.
AboutAbout this tool
URL Parameters to JSON Converter
Long URLs are hard to review when parameters are packed into a single query string. This tool converts URL parameters into readable JSON so you can inspect keys, values, duplicated fields, tracking parameters, and API request filters more easily.
When it helps
- Review UTM links: Check
utm_source,utm_medium,utm_campaign, and other campaign values. - Debug API requests: Convert GET request parameters into a structured object for testing or documentation.
- Clean shared links: Spot unnecessary or unexpected parameters before publishing a URL.
Things to watch
Some URLs contain repeated keys, encoded values, or empty parameters. Decide whether repeated keys should become arrays, whether blank values are meaningful, and whether encoded text should be decoded before review.
Articles for this tool
How to Convert URL Parameters to JSON for UTM and API Debugging
Turn long query strings into readable JSON so you can review UTM tags, API filters, duplicated keys, and encoded values more easily—with concrete examples.
URL Mechanics and Parameter Analysis: From Encoding to JSON Conversion
Explore the structure of URLs, the necessity of Percent-Encoding, and efficient ways to handle complex query parameters in web development.
How to URL Encode and Decode Strings for APIs and Query Parameters
Learn what percent encoding means, when to encode URLs, and how to inspect encoded query strings safely during API and tracking-link debugging.
