JSON pluck field
ClientLike selecting a column from a table—turn rows with id and name fields into a flat list of names for charts or quick checks.
Learn more: plucking a field
Requires a root JSON array of objects; missing keys become null in the output array.
Local processing
Parsing and output formatting run entirely in your browser—nothing is uploaded for this transform.
Input
?
Nearby workflows on Toolcore
- JSON group by field — Bucket a root array of objects by one property—object of arrays output; local only. once JSON text parses on this page.
- JSON count by field — Count occurrences of each value for one property across a JSON object array—local only. once JSON text parses on this page.
- JSON filter by field — Keep objects in a JSON array where one field equals a value—client-side row filter. once JSON text parses on this page.
- CSV ↔ JSON — Paste a table or JSON array of objects—convert both ways, choose delimiter, client-side. once JSON text parses on this page.
Common use cases
- Like selecting a column from a table—turn rows with id and name fields into a flat list of names for charts or quick checks.
Common mistakes to avoid
Invalid JSON
Fix parse errors before expecting output.
FAQ
Is data uploaded?
No—all parsing and transforms run locally.
How is this different from jq?
This page focuses on one deterministic task without a filter language.
More tools
Related utilities you can open in another tab—mostly client-side.
JSON group by field
ClientBucket a root array of objects by one property—object of arrays output; local only.
JSON count by field
ClientCount occurrences of each value for one property across a JSON object array—local only.
JSON filter by field
ClientKeep objects in a JSON array where one field equals a value—client-side row filter.
CSV ↔ JSON
ClientPaste a table or JSON array of objects—convert both ways, choose delimiter, client-side.