/// GUIDES / VERSIONING
Versioning
Versioning keeps every revision of an object so you can recover from an accidental overwrite or delete. storafleet lets you turn it on, browse an object's full history, and restore, delete, or clean up versions — all from the Fleet UI.
What versioning does
When versioning is enabled, each write to a key produces a new version with its own version ID. Older versions stay in the bucket until you explicitly remove them, which is what makes one-click restore and recovery from accidental deletes possible.
Enable or disable versioning
Open a Fleet, go to Settings → Versioning, and toggle it on or off. Where the provider supports it, storafleet writes the bucket versioning state for you.
Manage an object's versions
From the object browser, open an object's version history to see every stored revision. From there you can:
- Restore a previous version in one click, making it the current version again.
- Delete a specific version when you no longer need that exact revision.
- Remove delete markers to bring back an object that was deleted while versioning was on.
Bulk clean-up
Because old versions keep accumulating, storafleet offers a bulk clean-upto remove old versions in one operation and cut storage cost.
Provider notes
- AWS, Wasabi, MinIO, and DigitalOcean Spaces support full versioning control — enable, disable, and manage versions.
- Backblaze B2 versioning is always on and is read-only via the S3 API — you can browse versions but cannot toggle versioning through the S3 interface.
- Cloudflare R2 has no S3 versioning, so versioning controls do not apply to an R2 Fleet.