Jq/JSONPath Tester

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from Jq/JSONPath Tester

Jq/JSONPath Tester helps you test jq or JSONPath expressions in JSON. These query languages select values from nested JSON, and jq can also reshape or compute results through its own expression syntax. This is useful when the information is already available but its structure, presentation, or consistency makes it difficult to inspect. Work with a representative sample first so that you can recognize the expected result before applying the same operation to a larger document. Select the correct query language before entering an expression. jq and JSONPath differ in syntax, result shape, and available operations. Keep the original input available while reviewing the output. The important check is whether the result still has the intended values and relationships, rather than whether it merely looks neater. Test arrays, missing properties, and null values rather than relying only on a single successful object lookup.

Guide updated October 13, 2026

How to use this tool

1. Place the JSON input in the relevant editor. If the tool compares or combines documents, keep each document in its own input.
2. Select the available settings for the operation you need. Test arrays, missing properties, and null values rather than relying only on a single successful object lookup.
3. Review any syntax errors before interpreting the result. A valid document with the wrong structure needs a different fix from malformed input.
4. Inspect the changed portion and at least one unchanged portion. Keep a copy of the original JSON until the result has been checked in its destination.

SEE IT IN PRACTICE

A worked example

{"name":"Ada"}; jq filter .name

"Ada"

The .name jq filter selects the value associated with name. A JSONPath equivalent uses that language’s own syntax.

Arrays and absent matches

A query that works on one object can behave differently when the same object is inside an array. Test a list containing two matching records, a record without the property, and a null value. Observe whether the result is a stream, an array, or a scalar under the selected language. Those differences matter when piping the output into another tool.

Choose jq or JSONPath deliberately

For jq, .name selects a property and .[] iterates values of a suitable collection. JSONPath uses another notation and commonly starts with a root expression such as $. These syntaxes are not interchangeable. Begin with the selected engine’s smallest field-selection example, then add filtering or projection. Check whether the engine returns one result, several results, or an enclosing array before reusing the output.

When this tool is useful

• Extract API response fields while keeping the underlying structure visible.
• Reproduce a query error with a compact, reproducible sample.
• Develop a compact data projection before copying data into another application.

Tips for a better result

• Select the correct query language before entering an expression. jq and JSONPath differ in syntax, result shape, and available operations.
• Test arrays, missing properties, and null values rather than relying only on a single successful object lookup.
• Use a small JSON example to isolate an unexpected result. Add nested objects, arrays, quoted text, and empty values only as needed to reproduce the behavior.

Frequently asked questions