The Filter Keys operation filters object properties in a JSON file based on a list of key names. You can choose to keep only the keys you specify or remove those keys from the JSON data. The filtering is applied recursively to objects throughout the JSON structure, while arrays are preserved and their items are processed as well.
Upload a JSON file to Lamuki's JSON workspace, select the Filter Keys operation, and provide the key names you want to filter. Enter multiple keys as a comma-separated list, such as name, email, age. With Keep Keys enabled, only matching keys remain in each JSON object. With Keep Keys disabled, matching keys are removed and other keys remain.
Yes. Enable Keep Keys and enter the key names you want to retain. For example, if an object contains name, email, age, and address and you specify name,email, the resulting object contains only name and email. The same key filtering behavior is applied to nested objects as the operation processes the JSON recursively.
Yes. Disable Keep Keys to remove the specified keys instead of retaining them. If you provide password, token as the key list, objects containing those exact keys will have them removed. Other properties are retained, and nested objects are processed using the same rule.
Yes. Filter Keys recursively processes JSON objects at every level. A matching key is filtered wherever it occurs inside an object, including objects nested within other objects. This makes the operation useful for JSON files with repeated structures or deeply nested data rather than only simple top-level objects.
Arrays are preserved as arrays, and each item is processed recursively. If an array contains objects, the keys of those objects are filtered according to the selected key list and Keep Keys setting. Primitive array values such as strings, numbers, booleans, and null values are preserved.
Yes. The operation compares the key names in your JSON data with the names in the provided key list. Matching is based on the key text after leading and trailing whitespace is removed from each supplied key. The operation does not perform partial-key or pattern matching.
Enter the keys as a comma-separated list. For example, name, email, phone identifies three keys. Whitespace around each comma-separated key is ignored, and empty entries are discarded. The key names are then used as the set of keys to keep or remove throughout the JSON structure.
The operation filters the key itself and its associated value together. When a key is removed, its entire property and value are removed from the resulting object. When Keep Keys is enabled, only the specified properties and their values remain. Values belonging to retained properties are recursively processed if they contain objects or arrays.
The operation parses the JSON content, applies the key filtering recursively, and replaces the file content with the resulting JSON representation. The resulting content is formatted with two spaces of indentation, making the processed JSON easier to read.
The operation expects the file content to be valid JSON. If the content cannot be parsed as JSON, the operation does not produce a filtered JSON result and reports a JSON Decode Error indicating that the file contains invalid JSON.
Yes. Primitive JSON values such as strings, numbers, booleans, and null are preserved when encountered during recursive processing. Key filtering applies to object properties, while arrays are traversed and their contents are processed.
Filter Keys is useful when you need to reduce JSON objects to selected properties or remove specific properties from structured data. Common examples include keeping only fields needed for a particular dataset, removing unwanted fields from nested records, preparing JSON for another processing step, or removing known properties throughout repeated object structures.
Developers, data analysts, students, and anyone working with structured JSON data can use Filter Keys to simplify objects without manually editing every occurrence of a property. It is particularly useful when the same key appears across nested objects or across many JSON files that need the same operation.
Yes. Filter Keys is part of Lamuki's complete JSON workspace, where you can select files and apply operations to them. Lamuki supports multiple-file processing and unlimited batch processing, making the operation suitable when the same key-filtering workflow needs to be applied to many JSON files.
Lamuki supports uploading entire folders as part of its file workflow. After adding your files to the JSON workspace, you can select the files you want to process and apply the Filter Keys operation to the selected files rather than manually opening and processing each file separately.
Yes. Lamuki provides a complete workspace for working with files, applying operations, and reviewing computed results. After Filter Keys runs, you can inspect the resulting JSON in the workspace and then download the processed files you need.
Yes. Filter Keys can be part of a longer JSON workflow. After completing the operation, you can select another operation from the workspace's operation interface and continue working with the same files. You do not need to manually download and re-upload the files between operations.
Yes. Filter Keys is available as part of Lamuki's JSON workspace and is free to use. Lamuki provides unlimited batch processing, so you can use the operation for repeated multi-file JSON workflows without a paid subscription or account.
No. Lamuki does not require account creation or login. You can use the JSON workspace and its operations without creating an account or signing in.
No. Filter Keys processes JSON content directly in your browser. Your file contents are not transferred to a remote server for processing, so the filtering work takes place on your device rather than through a remote processing service.
Keep Keys determines which side of the key list becomes the result. When Keep Keys is enabled, only keys included in your comma-separated list are retained. When it is disabled, the listed keys are removed and all other object properties are retained. In both modes, the rule is applied recursively to nested objects.
No. The operation is recursive rather than limited to the top level. It examines objects throughout the JSON structure, including objects nested inside other objects and objects contained in arrays. This means a selected key can be filtered at multiple levels of the same JSON file.
Filter Keys operates on JSON object keys, not arbitrary text occurrences. The supplied key list is interpreted as comma-separated key names, and each name is trimmed before matching. The same keep-or-remove rule is applied recursively to every object encountered. If the input is invalid JSON, the operation reports an error instead of producing a filtered result.
