JSON All-in-One
JSON All-in-One / JQ in Chrome
Put JQ inside your everyday JSON workflow
Open an API response or local file, write a JQ expression beside the source, and review the transformed result in the same browser workspace. Save named aliases for filters you use again.
Free includes JQ and the rest of the workbench. A license removes reminders, not feature limits.
One source, one expression
See the result before adapting the filter
[
{"id":"ord_1","status":"paid","total":18},
{"id":"ord_2","status":"draft","total":7}
]map(select(.status == "paid") | {id, total})[
{"id":"ord_1","total":18}
]Paste the source as a JSON array or open it as a file, switch to JQ, run the expression, and check that only ord_1 remains. The JQ filter guide explains each operator. The video above follows the same source-to-result pattern with a larger cloud-cost fixture.
When an extension helps, and when it does not
Use the extension
You inspect responses and files in Chrome or Edge regularly, want source and derived tabs together, and reuse expressions with aliases, autocomplete, and query history.
Use a one-off tool or CLI
For an occasional pasted example, the JQ online tool is the shorter path. For shell pipelines, automation, or direct integration with scripts, use the jq CLI. This extension is not a CLI replacement.
Know the input mode before you query
JSON
Use normal JQ syntax on the document you opened. Narrow an array with map(select(...)), or use .[] when you want separate output values.
JSONC
Comments can be stripped before ordinary JQ, but trailing commas are rejected on that route. A narrow direct projection over a root array has a different fast path. See exact JSONC examples and limits.
JSONL / NDJSON
Recognized line-delimited records become an array in the workspace. Query that array, rather than copying a CLI streaming expression unchanged. See the record-mode guide.
After querying, review the result shape before an export. The nested JSON to CSV guide shows how to make rows explicit.
Local processing, with clear network boundaries
Core JQ runs in the browser workspace on the opened source. Direct file:// navigation needs Chrome's or Edge's extension file-access setting; the in-workbench picker is a separate path. Optional configured AI can send a prompt and selected snippets to the provider you choose, and opt-in image fetching can contact URLs from your data. Neither is needed to run the JQ expression above. Read the privacy policy and local-file instructions for the details.
Before you install
How do I start?
Install from the Chrome or Edge store, open a JSON response or choose a local file in the workspace, switch to JQ, paste the sample expression, and run it against the sample array.
Why does a local file open as raw text?
If you navigated directly to a file:// URL, enable file URL access on the extension details page and reopen it. You can also use the workspace file picker. Follow the file guide.
Is JQ paid?
No. JQ and the other workbench features are available in Freemium. The optional lifetime license removes occasional reminders.
Are large numbers exact through JQ arithmetic?
Do not assume that viewing an original number literal makes a later JQ calculation or export arbitrary-precision. Test the exact operation, especially for identifiers and long decimals. See the number precision guide.
For reusable expressions, continue with JQ recipes.