What JSON filtering is
Keep object records that match one field-based rule
JSON array filtering checks the same top-level property across every object and returns only matching records. UtilityDock detects available fields, applies one clear rule, and preserves the order and contents of every match without uploading the array.
Data-cleaning workflows
Isolate records that need review or correction
Find blank values, keep records with a specific status, or isolate numeric values above or below a threshold. The original and filtered counts make it easy to confirm the scope of a cleanup before downloading the result.
- Find missing values before an import
- Keep records in one workflow status
- Identify values above a numeric threshold
- Match text prefixes used by identifiers
- Prepare a focused subset for manual review
- Preserve source order for downstream processing
API response filtering
Inspect the records relevant to a debugging task
Large API responses often contain object arrays with many states, categories, or numeric measurements. Filter a saved response locally to focus on one useful subset while keeping sensitive payloads on your computer.
Analytics preparation
Create smaller, consistent inputs for analysis
Apply a repeatable field rule before converting data, reviewing metrics, or sharing a prepared file. Text operators are case-sensitive, while Greater Than and Less Than accept finite JSON numbers and reject an invalid threshold clearly.
Missing and null values
Use predictable empty-value behavior
Missing properties and null values never match a value comparison. Is Empty matches missing properties,null, and empty strings. Is Not Empty matches all other values, including zero and false.
Examples
Choose the operator that matches your question
| Question | Example rule |
|---|---|
| Which records are ready? | status Equals ready |
| Which names begin with API? | name Starts With API |
| Which scores exceed 90? | score Greater Than 90 |
| Which records need a value? | owner Is Empty |
Data Toolkit
Continue with related UtilityDock JSON workflows
FAQ
Questions about filtering JSON arrays
Does UtilityDock upload or store my JSON?
No. Your files never leave your computer. Validation, field detection, filtering, preview, copying, and download creation all happen locally inside your browser.
What JSON shape can I filter?
Version 1 accepts a non-empty array of JSON objects at the document root. Each detected top-level property becomes an available filter field.
How are missing and null values handled?
A missing property or null value does not match value-based operators, including Not Equals. Is Empty matches missing properties, null, and empty strings; Is Not Empty matches everything else.
Are text filters case-sensitive?
Yes. Equals, Not Equals, Contains, Starts With, and Ends With use case-sensitive matching. Text operators apply to JSON strings.
How do numeric comparisons work?
Greater Than and Less Than compare finite JSON numbers with the number you enter. Numeric-looking strings are not converted automatically.
Does filtering change record order?
No. Matching records keep the same relative order they had in the source array.
Can I combine multiple filter rules?
No. Version 1 applies one field-based rule and does not support boolean groups, SQL syntax, regular expressions, custom expressions, or APIs.