Each item in a JSON array is compared with the items that have already been retained. Two values are considered duplicates when they are deeply equal, meaning their JSON contents match rather than merely being the same type. This applies to simple values as well as structured values such as objects and arrays. For example, an array containing two identical objects will keep the first object and remove the later equivalent object. The same approach works for nested arrays. The resulting array therefore contains only the first occurrence of each distinct value while preserving the order in which those distinct values originally appeared.

Yes, when Include Object Values is enabled. In that mode, the operation examines the values associated with an object's properties and keeps only the first property encountered for each distinct value. If two different keys contain deeply equal values, the first key and its value are retained and the later key is removed. This applies to structured values as well as simpler JSON values. Include Object Values is disabled by default according to the operation's input configuration, so object properties are not deduplicated unless that option is enabled.

The Recursive option determines whether duplicate removal is limited to the current JSON level or applied throughout nested JSON structures. With Recursive disabled, the operation processes only the value at the current level. With Recursive enabled, it first processes the children of arrays and objects and then removes duplicates from the resulting value at that level. This allows a single operation to clean duplicate array items and, when Include Object Values is also enabled, duplicate object values throughout nested JSON data. Recursive processing does not change primitive values such as strings, numbers, booleans, or null.

For a nested array, Recursive processing first applies the operation to every item inside that array. If an item contains another array or object, those nested structures are processed before the parent array is deduplicated. After its children have been processed, the parent array is checked for duplicate items. This ordering means the comparison happens against the processed versions of the items. For example, if two array elements become identical after their nested contents have been cleaned, they can then be recognized as duplicates at the parent level. Without Recursive enabled, nested structures are not traversed.

When Recursive is enabled, every object property value is processed before the object itself is considered for duplicate-value removal. If Include Object Values is also enabled, the operation then compares the object's property values and retains the first occurrence of each distinct value. This can be useful for JSON objects containing repeated nested structures. If Include Object Values is disabled, recursive processing still traverses and processes child arrays and objects, but the current object's own property values are not removed merely because they are duplicates. The two options therefore control different aspects of nested processing.

Yes. The operation builds a new result while iterating through the original value in order. For arrays, an item is added only when no previously retained item is deeply equal to it. For objects with Include Object Values enabled, properties are examined in their existing entry order, and a property is retained only when its value does not match a value already retained. As a result, when duplicates exist, the first occurrence is kept and later equivalent occurrences are removed. The operation does not intentionally reorder the distinct values or retained object properties.

Duplicate detection uses deep equality rather than a simple reference or shallow comparison. This is important for JSON because arrays and objects can contain nested data. Two structured values can therefore be recognized as duplicates when their contents are deeply equal. The operation does not treat two separate object instances as automatically different just because they were created separately. Instead, their contents are compared through the deep equality logic used by the workspace. This allows duplicate detection to work with nested JSON structures rather than only simple primitive values.

When Recursive is disabled, the operation does not walk through child arrays or objects. It applies duplicate removal only to the current JSON value. If that value is an array, duplicate array items at that level are removed. If it is an object and Include Object Values is enabled, duplicate property values at that level are removed. If the current value is not an array and does not qualify for object-value processing, it is returned unchanged. This option is useful when you want to control the scope of the cleanup rather than automatically process nested data.

With both options enabled, the operation performs the broadest duplicate cleanup supported by this implementation. It recursively processes nested arrays and objects, removes duplicate items from arrays at every processed level, and removes repeated values from objects at every processed level. Child structures are processed before their parent structures are deduplicated. This can clean a deeply nested JSON document in one operation while still retaining the first occurrence of each deeply equal value or object property value.

No. Primitive JSON values such as strings, numbers, booleans, and null are returned without transformation when they are processed as individual values. Duplicate removal is meaningful at array and, when enabled, object levels. A primitive value inside an array can still be removed when another deeply equal occurrence already exists in that array. Similarly, a primitive can be removed as an object's property value when Include Object Values is enabled and another retained property already contains the same value.

The operation attempts to parse the file content as JSON before processing it. If the content cannot be decoded as valid JSON, the operation does not produce a transformed JSON result. Instead, it sets a JSON Decode Error output with the message Invalid JSON file. This means the operation expects valid JSON input and does not attempt to repair malformed JSON syntax before removing duplicates.

This operation can be useful for anyone working with JSON data that contains repeated array items or repeated object values. Developers can use it when cleaning structured data, preparing JSON for further processing, or simplifying generated data. It can also help when inspecting datasets where repeated values make the structure harder to understand. The Recursive option is particularly useful when duplicate data appears at multiple nesting levels, while Include Object Values provides additional control when repeated values occur across different object properties.

Yes. Remove Duplicates is part of Lamuki's JSON workspace, where multiple files can be selected for processing. Lamuki supports unlimited batch processing, allowing the operation to be applied across the JSON files you need to process rather than requiring you to handle each file individually. You can also upload an entire folder when that fits your workflow. After selecting the files, you can apply the operation and review the computed results within the workspace.

Open the JSON workspace and add the JSON files you want to process, either individually or through a folder upload. Select the files you want to work on and choose the Remove Duplicates operation. Configure Recursive if you want duplicate removal to continue through nested arrays and objects, and enable Include Object Values if repeated object property values should also be removed. Apply the operation and review the resulting JSON files in the workspace. You can then download the processed files or continue working with them using another operation.

Yes. Remove Duplicates is part of a complete JSON workspace, so the processed files can remain in the workspace for the next step of your workflow. After the operation finishes, 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 just to move from duplicate removal to another JSON transformation.

Yes. Lamuki's workspace is designed around working with files, applying operations, and reviewing the computed results. After Remove Duplicates has processed a JSON file, the updated content can be reviewed in the workspace and the processed files can be downloaded when they are ready. This makes the operation suitable for workflows where duplicate cleanup is only one step before another transformation or before saving the cleaned JSON data.

Yes. Lamuki is free to use, and its workspaces and operations are available without a paid subscription. There is no account or login requirement, and Lamuki provides unlimited batch processing. This allows Remove Duplicates to be used for individual JSON files as well as larger batches without introducing a paid processing limit. The operation remains part of the complete JSON workspace rather than requiring a separate paid service.

No. Lamuki processes files directly in the user's browser. The JSON content is not uploaded to Lamuki's servers for processing or transferred to a remote processing service for this operation. The workspace is designed to keep file processing on the user's device, allowing users to work with their JSON data without sending the file contents to a server for the duplicate-removal process. This browser-based approach is a core part of Lamuki's privacy-focused design.

Duplicate array removal compares the items contained in an array and keeps the first occurrence of each distinct item. Duplicate object-value removal instead compares the values associated with an object's properties and removes later properties whose values are already represented by a retained property. The latter behavior is controlled by Include Object Values. These are separate cases because JSON arrays represent ordered collections of items, while JSON objects associate values with property names. Remove Duplicates supports both behaviors while keeping the two cases distinct.

Not automatically. Recursive controls whether nested levels are processed. With Recursive disabled, duplicate removal is limited to the current level. With Recursive enabled, nested arrays and objects are processed before their parent structures. Include Object Values separately determines whether duplicate values belonging to object properties are removed. Therefore, the final scope depends on these two settings. This gives you control over whether you want a focused cleanup at one level or a recursive cleanup throughout the JSON structure.

Recursive processing is useful when repeated data can occur at different depths in a JSON document. A JSON file may contain arrays inside objects, objects inside arrays, or several levels of nested structures. Processing only the top level would not inspect those children. Enabling Recursive allows the operation to traverse those nested structures and apply its duplicate-removal behavior throughout them. If the JSON should be cleaned only at a particular level, leaving Recursive disabled provides a narrower transformation.

The operation is a transformation rather than a duplicate report: matching values are actually removed from the resulting JSON. For arrays, later deeply equal items are removed. When Include Object Values is enabled, later object properties with duplicate values are removed as well. Recursive processing can extend these changes throughout nested structures. Because the first occurrence is retained, the position of duplicate values can affect which object property remains. For important data, review the computed result in the workspace before downloading or continuing with another operation.

Lamuki combines the Remove Duplicates operation with a complete workspace for working with JSON files. Instead of treating duplicate removal as an isolated action, you can select files, process multiple files in a batch, review results, download processed files, and continue with another operation using the same files. Folder uploads can make larger file collections easier to bring into the workspace. Processing happens directly in the browser, and Lamuki provides the workspace and its operations for free without requiring an account or login.