---
title: "Managing File Deletion in WCN"
slug: "managing-file-deletion"
updated: 2026-02-05T16:51:38Z
published: 2026-02-05T16:51:38Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing File Deletion in WCN

When file delete mode is enabled, you can manage file deletion in a bucket with:

- [Versioning disabled](/v1/docs/managing-file-deletion#managing-file-deletion-in-a-bucket-with-versioning-disabled)
- [Versioning enabled](/v1/docs/managing-file-deletion#managing-file-deletion-in-a-bucket-with-versioning-enabled)

For detail about configuring file delete mode, review [Configuring File Delete Mode](https://docs.wasabi.com/docs/configuring-file-delete-mode).

### Managing File Deletion in a Bucket With Versioning Disabled

When file delete mode is enabled and bucket versioning is disabled, WCN will permanently delete the corresponding replica from the bucket when:

- The file is deleted from the source and permanently removed from the recycle bin.
- The data replication policy time interval lapses.

### Managing File Deletion in a Bucket With Versioning Enabled

When file delete mode is enabled and bucket versioning is enabled, deleting a file on the source results in a soft delete in the bucket. Be sure to note that:

- A delete marker is added to the object.
- The object becomes a noncurrent version.

This behavior remains the same even if the file is removed from the recycle bin on the source system. This enables you to retain full recovery capabilities from the bucket without the risk of immediate, permanent deletion.

1. Right-click a file to delete from the source folder.
2. Click **Delete**. The file is moved to the recycle bin. Once the file is permanently deleted from the recycle bin, WCN processes the deletion based on the data replication policy interval.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image(7)(1).png)
3. Navigate to the bucket with versioning enabled.
4. Click **Show Versions**. Notice that:

The file appears deleted but is still stored in the bucket under a delete marker and can be recovered, as needed.
  - A delete marker is added.
  - The original file remains as a noncurrent version.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image(6)(1).png)

## Permanently Deleting Noncurrent Versions

You can configure lifecycle rule settings in a bucket with versioning enabled to manage storage usage. Specify when Wasabi permanently deletes noncurrent versions of objects created through soft deletes. To do so, follow the steps in [Creating a Lifecycle Rule](https://docs.wasabi.com/docs/lifecycle#creating-a-lifecycle-rule). Be sure to set:

- Actions—Select **Permanently delete noncurrent versions of objects**.
- Days after object become noncurrent—(required) Enter a number.
- Specify number of newer versions to retain—(optional) Enter the number of days to retain noncurrent objects in the bucket.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image(5)(1).png)