JSONPath & JMESPath

Client

Switch between JSONPath and JMESPath, paste JSON, and copy query results— useful for APIs, logs, and config inspection.

Learn more: JSONPath and JMESPath

Extract slices of a large JSON value with JSONPath (jsonpath-plus) or JMESPath—handy for logs, APIs, and config without loading extra desktop tools.

Which to use

JSONPath is familiar from many linters and test tools; JMESPath appears in cloud CLIs and filters. Both return JSON-friendly results you can copy out.

Query JSON

?

JSONPath (jsonpath-plus) uses expressions like $.a.b[*]. JMESPath is common in AWS CLI-style filters.

Common use cases

  • Pull nested fields from large API or log JSON without writing a one-off script.
  • Prototype JSONPath or JMESPath expressions before embedding them in apps, jq pipelines, or AWS CLI filters.
  • Compare how the same payload answers different query languages side by side.

Common mistakes to avoid

  • Expecting JSONPath and JMESPath to use identical syntax

    They are different grammars. An expression that works in one may need rewriting in the other—always verify against your runtime.

  • Querying non-JSON or truncated input

    Queries assume valid JSON. Fix parse errors in the document first; otherwise results will be empty or misleading.

FAQ

Are queries executed on your servers?

No. Parsing and evaluation run locally in your browser.

Which dialect matches my cloud API?

Vendors differ. Use this page to test expressions, then confirm with the exact engine your service documents.

More tools

Related utilities you can open in another tab—mostly client-side.