# Soft Delete Retention on High-Churn Cloud Storage Buckets Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/soft-delete-retention-on-high-churn-cloud-storage-buckets Cloud Storage soft delete keeps deleted and overwritten objects recoverable for a retention period, 7 days by default and configurable from 7 to 90... By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version Cloud Storage soft delete keeps deleted and overwritten objects recoverable for a retention period, 7 days by default and configurable from 7 to 90 days, and new buckets get it unless an organization changes the default. PointFive Research Cloud cost research at PointFive GCP service [GCP GCS](https://www.pointfive.co/efficiency-hub/cloud-services/gcp-gcs) Category [Storage](https://www.pointfive.co/efficiency-hub/service-category/storage) Reference CER-0472 Type Excessive Data Retention ## Explanation Why the waste happens and who it affects. Soft-deleted data is billed like any other stored data for the whole retention period. For buckets holding long-lived data this is a modest insurance cost, but for buckets whose objects are written and deleted quickly, the soft-deleted bytes can exceed the live bytes. Google warns that if a bucket primarily contains temporary data, soft delete can result in significantly increased storage costs, and names typical cases: staging files, query results, source parts of composite objects and workloads with frequent writes and deletes. Pipelines that rename objects by copying and deleting them, or that rewrite the same objects daily, create the same effect. ## Billing model The pricing dimensions that drive this cost. Soft-deleted storage Billed at the storage rate of each object's storage class, the same as live and noncurrent objects, until the retention period expires Retention duration 7 days by default, configurable from 7 to 90 days, or 0 to disable Early deletion Objects in Nearline, Coldline or Archive that are soft deleted before their minimum storage duration incur early deletion charges, reduced by the length of the retention duration Restores Restoring soft-deleted objects is billed as operations, and retrieval fees do not apply ## How to detect 4 checks to find it in your estate. - Review the Cloud Storage Soft Delete recommender; it recommends disabling soft delete on buckets whose soft delete costs are over 50% of their monthly Cloud Storage cost and at least 20 USD, and shows the estimated monthly savings - Chart storage.googleapis.com/storage/v2/total\_bytes (or v2/total\_byte\_seconds) by the type label and compare soft-deleted-object with live-object bytes per bucket - Identify buckets used for temporary data: staging, landing, scratch, query results, compose sources and checkpoints - Check for pipelines that rename objects with copy plus delete, which soft-delete the original on every rename ## How to fix 4 ways to remove the waste. - Disable soft delete on buckets that hold only temporary data with gcloud storage buckets update --clear-soft-delete gs://BUCKET, or keep the minimum 7-day retention where some protection is wanted; already soft-deleted objects stay until their original retention expires - Move temporary objects into dedicated buckets with soft delete disabled and keep durable data in buckets that retain it - Rename objects with the objects.move API instead of copy plus delete, so renames do not leave soft-deleted copies - Set an organization or folder default with tags so new scratch buckets are not created with soft delete, and weigh each change against the higher risk of data loss from accidental or malicious deletion ## Documentation Vendor references for pricing and configuration. - [Soft delete overview docs.cloud.google.com](https://docs.cloud.google.com/storage/docs/soft-delete) - [Soft Delete recommender docs.cloud.google.com](https://docs.cloud.google.com/storage/docs/soft-delete-recommender) - [Disable soft delete docs.cloud.google.com](https://docs.cloud.google.com/storage/docs/disable-soft-delete) - [Storage pricing cloud.google.com](https://cloud.google.com/storage/pricing) - [Google Cloud metrics: P through Z docs.cloud.google.com](https://docs.cloud.google.com/monitoring/api/metrics_gcp_p_z) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - GCP GCS CER-0080 ### [Over-Retained Noncurrent Object Versions in Versioned GCS Buckets](https://www.pointfive.co/efficiency-hub/inefficiencies/over-retained-exported-object-versions-in-gcs-versioning-buckets) When GCS object versioning is enabled, every overwrite or delete operation creates a new noncurrent version. Without a lifecycle rule to manage old versions, they persist indefinitely. Over time, this results in: Accumulation of outdated... Storage - GCP GCS CER-0336 ### [Excessive API Request Cost Overhead from I/O-Intensive Workloads](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-api-request-costs-from-filesystem-style-access-on-gcs) Google Cloud Storage exposes a flat namespace through an HTTP API, but many workloads consume it through filesystem-style abstractions - FUSE mounts, Hadoop/Spark connectors, or analytic engines that enumerate prefixes to discover state.... Storage - GCP GCS CER-0117 ### [Missing Autoclass on GCS Bucket](https://www.pointfive.co/efficiency-hub/inefficiencies/missing-autoclass-on-gcs-bucket) Buckets without Autoclass enabled can accumulate infrequently accessed data in more expensive storage classes, inflating monthly costs. Enabling Autoclass allows GCS to automatically move objects to lower-cost tiers based on observed... Storage --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.