JSON pick or omit keys
ClientChoose keys to keep (pick) or drop (omit) at the top level only. Root value must be an object or an array of objects.
Pick or omit keys
?
Only top-level keys on each object are changed. Key matching is case-sensitive. Root must be an object or an array of objects.
Common use cases
- Trim API response objects to id/name fields before saving a sample.
- Strip noisy or sensitive top-level keys from an array of row objects.
Common mistakes to avoid
Expecting nested keys to be removed
Only the root object’s top-level keys (or each array element’s top-level keys) are affected. Nested properties stay as-is.
FAQ
Is processing done in the browser?
Yes. Parsing and output are handled locally in your tab.
More tools
Related utilities you can open in another tab—mostly client-side.
JSON redact keys
ClientMask values by key name recursively—case-insensitive; local only.
JSON path list
ClientEnumerate leaf paths ($ / dot / brackets); optional RFC 6901 pointers, filter, and stats—local only.
Extract JSON from text
ClientFirst {...} or [...] in logs or mixed paste—strict JSON, pretty-print locally.
JSON formatter
ClientJSON format online: pretty-print, minify, validate, escape, download .json.