jq playground and JSONPath tester runs JSON queries locally. jq uses an actual WebAssembly build of the jq engine; JSONPath provides structural selection with script and filter evaluation disabled.
Paste valid JSON, choose the language and run explicitly. The jq engine loads only on first execution in a disposable worker; cancellation and a ten-second deadline stop expensive expressions.
How to use
- Paste a valid JSON document.
- Choose jq or JSONPath and enter an expression for that language.
- Run, inspect the result and download the output.
Frequently asked questions
Is jq emulated with JavaScript?
No. The jq mode uses jq-web’s WebAssembly engine, loaded locally from this site when you run it.
Can JSONPath filters execute code?
This editor disables JSONPath evaluation. Structural selectors work; expressions requiring script or filter evaluation are rejected.
Why are jq results newline separated?
jq can emit a stream of separate JSON values. The tool preserves its compact output stream rather than wrapping it into an invented array.
What are the size limits?
Input is limited to 1,000,000 characters, expressions to 4,000 and output to 2,000,000. Jobs exceeding ten seconds are terminated.
Two different query languages
A jq expression such as .items[].name emits names from an array. A structural JSONPath such as $.items[*].name returns selected values as an array.
The languages are not interchangeable. Switching modes supplies a matching starter expression; adjust it to the structure of your own JSON.
Local execution boundaries
The approximately 3 MB jq runtime is served as same-origin static assets. Pasted JSON and expressions stay in the worker rather than being sent to a query server.
This is a bounded playground, not a shell. There is no host filesystem, command execution, streaming file ingestion or guarantee that an enormous jq result can be materialized.
