Query Params ⇄ JSON
GET param parsing · JSON to URL builder
Query params
Ready
ABOUT
About Query Params ⇄ JSON
Parse query strings like ?a=1&b=2 into JSON, or generate URL parameters from JSON.
Query strings on GET requests are a high-frequency entry point for API debugging: UTM params, pagination, filters, OAuth callbacks—simple in structure, yet nested and duplicate keys often cause manual assembly errors.
DEEP DIVE
Learn More About Query Params ⇄ JSON
URL query strings are the standard way to pass parameters in GET requests. Manually parsing ?a=1&b=2&c=hello is tedious and error-prone, especially with URL-encoded Chinese or nested parameters. JSONSort Query tool converts both ways: string → JSON object, or JSON → query string.
Ideal for REST API debugging, constructing test URLs, analyzing frontend router query params, and troubleshooting encodeURIComponent issues.
application/x-www-form-urlencoded and multipart differ in array conventions. JSONSort parses duplicate keys as arrays and generates query strings with repeated keys for arrays—consistent with default behavior in Java Spring / Node Express.
FEATURES
Core capabilities
Query → JSON
Parse URL query strings into nested JSON objects with automatic URL decoding.
JSON → Query
Generate standard URL-encoded query strings from JSON objects.
Duplicate key handling
Same-name parameters become arrays, matching common server-side parsing semantics.
Encode / decode
Automatically handles %XX-encoded Chinese and special characters.
Instant Output
Paste a full URL or just the query portion—both work.
Local processing
URLs may contain sensitive params like tokens; local parsing is safer.
Full URL parsing
Paste a full URL with domain to auto-extract the query after ?.
Nested objects
Bidirectional mapping between bracket/dot notation and JSON objects.
HOW TO USE
How to use
-
1
Paste a URL query string or JSON object
-
2
Choose parse or generate direction
-
3
Copy result
-
4
On failure, check the error, fix source syntax, and retry
-
5
Pretty-print with the formatter or export for downstream scripts
WORKFLOW
Typical workflow
End-to-end workflow from import to export, helping teams standardize Query Params ⇄ JSON usage.
Enter query or URL
Copy from the browser address bar, Network panel, or logs.
View JSON
Confirm nested and array structures match server-side parsing logic.
Edit JSON
Modify parameter values, then reverse-generate the query string.
Run test
Append to base URL and verify in browser or Postman.
USE CASES
Use cases
Frontend developers
Parse Vue Router / Next.js query params as JSON for debugging.
Backend developers
Construct GET API test URLs—define params in JSON and generate query in one click.
QA engineers
Batch-construct test URLs with multiple parameters.
SEO / Marketing
Analyze landing page UTM param structure and convert to JSON for analytics.
Security testing
Break down redirect_uri and state params to analyze OAuth flows.
Data analysis
Batch-convert UTM params to JSON for BI tools and channel attribution.
TIPS
Tips
- When pasting a full URL, the tool extracts and parses the query after ?.
- Query strings generated from JSON → Query can be appended directly to a base URL for testing.
- Chinese parameters are automatically encodeURIComponent-encoded—no manual encoding needed.
- Array params in query strings typically appear as repeated keys; parsing restores them as arrays.
- Use with the Encode/Decode tool to troubleshoot double-encoding or missing encoding.
- Quickly break down and analyze OAuth redirect_uri query portions with this tool.
- + in query strings often represents a space; note it is equivalent to %20 when decoding.
- Before appending generated query to base URL, check whether ? already exists.
- Test array param edge cases: empty array, single element, and multiple elements.
- Use with Postman: extract URLs from Collection, then break down query.
LOCAL VS ONLINE
Local vs online tools
JSONSort stays purely frontend—this comparison shows why local tools fit dev data better.
TROUBLESHOOTING
Common pitfalls & fixes
Issues you may hit in practice and how to handle them—save time on trial and error.
Garbled Chinese text
Tip:Confirm URL decoding; for double-encoding, use the Encode/Decode tool to remove one layer.
Array becomes string
Tip:Check whether repeated keys should be used instead of a JSON array string.
Empty values lost
Tip:key= form is preserved as empty string, different from a missing key.
Nested depth limit
Tip:Very deep bracket notation may not be supported by the server—align format with backend conventions.
FAQ
FAQ
Does it support hash router params?
Only the query after ? is parsed. Hash after # must be separated manually.
Are empty-value params preserved?
Empty values in key= form parse as empty string "".
How are nested objects converted to query?
Flattened as key[nested]=value or dot notation, depending on mode.
Can params inside hash be parsed?
Query inside hash in #/page?x=1 must be separated manually; standard query before ? is handled automatically.
Is parameter order preserved?
JSON object key order may differ from the original query; functionally equivalent.
Is data uploaded to a server?
No. All JSONSort tools run locally in your browser—your input is never sent to any backend.
Do I need to sign up or install anything?
No. Open the page and go—no account, no client download, PWA offline cache supported.
How large can files be?
Depends on browser memory; multi-MB data usually runs smoothly. Split very large files or use merge & clean first.