> For the complete documentation index, see [llms.txt](https://docs.cloudeka.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudeka.id/storage/deka-box/enable-versioning-in-s3.md).
# Enable versioning in S3
Versioning in S3 is keeping multiple variants of an object in the same bucket. you can use the S3 versioning feature to preserve, retrieve, and restore every version of every object stored in your buckets. With versioning, you can recover more easily from both unintended user actions and application failures. If you enable versioning for a bucket, S3 automatically generates a unique version ID for the object that is being stored. For example, in one bucket you can have two objects with the same key but different version IDs, such as **photo.png** (version 1) and **photo.png** (version 2). to enable versioning, follow the instructions below.
{% hint style="info" %}
If you activate this feature, the old version of the ID will still be stored and will take up storage on your Deka Box.
{% endhint %}
To activate the version feature in S3 Browser, you can follow these steps:
* Open S3 Browser on your computer.
S3 Browser
* On the S3 browser, click **bucket**, then select **Edit Versioning Settings**.
S3 Browser - Edit Versioning Settings
* The **Bucket Versioning Settings** window, \[x] tick the checkbox of **Enable versioning for test-bucket** then click **OK**.
Edit Versioning Settings - Enable versioning for test-bucket
* Now that the versioning feature is enabled, you can try uploading a file with the same filename that is in the bucket. For example, we will upload a file called 4.1 Deka Box - Create Deka Box.png with a different Size. It can be seen in the Version section that there is no version history for this file.
Active Versioning Feature
* After trying to upload a file called 4.1 Deka Box - Create Deka Box.png, there will be two versions of the file, and those two files are two different files.
