What JSON field selection is
Project object arrays into a focused structure
Field selection keeps chosen properties and removes everything else from each object. UtilityDock detects nested leaf paths, reconstructs their parent structure, and preserves source record order entirely in your browser.
Reducing API payloads
Keep the response fields your integration actually uses
Prototype a smaller API response by retaining identifiers, labels, statuses, or nested values while excluding verbose metadata. The projected JSON is ready to copy into fixtures or download for local development.
Preparing analytics datasets
Create a consistent input for analysis
Select dimensions and measures before sending records into a notebook, spreadsheet, or reporting workflow. Missing fields remain absent, explicit null values remain null, and every source row stays in place.
Removing unnecessary fields
Reduce noise before sharing or processing data
Drop internal flags, large descriptions, or unrelated nested structures by selecting only the paths needed downstream. Review the before-and-after byte size before downloading.
Examples
Select paths for a clear outcome
| Goal | Fields to keep |
|---|---|
| Create a contact list | id, profile.name, profile.email |
| Prepare event metrics | event.type, event.timestamp, value |
| Simplify product records | sku, name, pricing.amount |
Data Toolkit
Continue with related UtilityDock JSON workflows
FAQ
Questions about selecting JSON fields
Does UtilityDock upload or store my JSON?
No. Your files never leave your computer. Validation, field detection, projection, preview, copying, and download creation all happen locally inside your browser.
What JSON shape can I use?
Version 1 accepts a non-empty array of JSON objects at the document root.
Can I keep nested fields?
Yes. UtilityDock detects nested leaf values with escaped dot paths and indexed array paths, then reconstructs their containing objects and arrays.
What happens when a selected field is missing?
That field is omitted from the affected output object. Null values are retained because null is an explicit JSON value.
Does field selection change array order?
No. Source records stay in their original order, and selected nested arrays retain their indexes.
Can I rename or calculate fields?
No. Version 1 only retains selected fields. It does not rename fields, evaluate expressions, calculate values, or call APIs.