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.
Numeric values are automatically parsed when possible, so the resulting JSON is easier to read and reuse.
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.
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.
Recent Articles
curl Options Cheat Sheet: What -X, -H and -d Actually Do
A reference for the curl options you meet in real API work: why -d already implies POST, how -d differs from --data-raw, the @ prefix that silently reads a file, single vs double quotes, and why -k and -L deserve more caution than they usually get.
Converting Between JSON Schema and Zod: How required Maps to .optional()
Inside a two-way converter that turns JSON Schema into a Zod schema and Zod code back into JSON Schema. Covers the inverted defaults between required and .optional(), the constraint mapping table, and how the Zod side is parsed without executing any code.
SQL Clause Order Reference: Why WHERE Can't See Your SELECT Alias
The order you write SQL clauses is not the order the database runs them. A reference for the logical execution order (FROM → WHERE → GROUP BY → HAVING → SELECT → ORDER BY → LIMIT), why aliases fail in WHERE, when to use WHERE vs HAVING, and the MySQL/PostgreSQL differences that bite.
Unified Diff Format Reference: Reading @@ Hunks in git diff Output
How to read the unified diff format git produces: what the four numbers in @@ -12,7 +12,9 @@ mean, why a one-character edit shows as a whole-line replacement, the whitespace and line-ending traps, \ No newline at end of file, combined @@@ diffs on merges, and rename detection via similarity index.
UTC to JST Reference: The 9-Hour Offset, Cheat Sheet & Timezone Pitfalls
Convert between UTC and JST (Japan Standard Time) with a cheat sheet. Covers what Z and +09:00 mean in ISO 8601, when JavaScript date parsing silently shifts by 9 hours, MySQL/PostgreSQL timezone behavior, and why GitHub Actions cron always runs in UTC.
CREATE TABLE Reference: MySQL vs PostgreSQL vs SQLite Types & Constraints
A cross-database CREATE TABLE (DDL) reference with cheat sheets for data types, auto-increment keys (AUTO_INCREMENT / IDENTITY / rowid), foreign key ON DELETE behavior, and the CHECK constraint that MySQL silently ignores.