JSON anti-join on key
ClientFind records present only on the left side of a key join.
Learn more: JSON anti-join
Compares two row sets on a key in your browser.
Local processing
Parsing and output formatting run entirely in your browser—nothing is uploaded for this transform.
Loading…
Nearby workflows on Toolcore
- JSON formatter — JSON format online: pretty-print, minify, validate, escape, download . once JSON text parses on this page.
- JSON replace values — Replace every value equal to from with to—use from|to, JSON or plain text. once JSON text parses on this page.
- JSON filter field by regex — Keep rows whose string field matches a regular expression—local. once JSON text parses on this page.
- JSON count field nulls — Count null or missing values for one row field—metadata. once JSON text parses on this page.
Common use cases
- Find records present only on the left side of a key join.
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 formatter
ClientJSON format online: pretty-print, minify, validate, escape, download .json.
JSON replace values
ClientReplace every value equal to from with to—use from|to, JSON or plain text.
JSON filter field by regex
ClientKeep rows whose string field matches a regular expression—local.
JSON count field nulls
ClientCount null or missing values for one row field—metadata.