# Over-retained noncurrent object versions in versioned GCS buckets Canonical: 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. By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Over-Retained Noncurrent Object Versions in Versioned GCS Buckets The short version When GCS object versioning is enabled, every overwrite or delete operation creates a new noncurrent version. 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-0080 Type Excessive Data Retention ## Explanation Why the waste happens and who it affects. Without a lifecycle rule to manage old versions, they persist indefinitely. Over time, this results in: - Accumulation of outdated data - Unnecessary storage costs, especially in Standard or Nearline classes - Lack of visibility into what is still needed vs. legacy debris This issue often goes unnoticed in environments with frequent data updates or automated processes (e.g., logs, models, config snapshots). ## Billing model The pricing dimensions that drive this cost. Storage costs accrue based on: - Total volume of data stored (including noncurrent object versions) - Storage class (e.g., Standard, Nearline, Coldline, Archive) - Retention of object versions, regardless of access patterns Versioned buckets retain every object version until explicitly deleted or transitioned, leading to silent growth in storage usage if no lifecycle policy is enforced. Noncurrent versions deleted by a lifecycle rule are also kept as soft-deleted objects for the bucket's soft delete retention period (7 days by default) and are billed during that window. ## How to detect 5 checks to find it in your estate. - Identify GCS buckets with versioning enabled - Review total storage split between current and noncurrent object versions - Assess frequency of updates to versioned objects - Determine if lifecycle rules exist to delete or transition noncurrent versions - Evaluate whether object version retention aligns with compliance or business needs ## How to fix 3 ways to remove the waste. - Implement lifecycle policies to delete noncurrent versions after a defined period - Transition noncurrent versions to colder storage classes (e.g., Archive) if needed for compliance, noting that Archive storage has a 365-day minimum storage duration - Audit versioned buckets periodically to ensure alignment with data governance and cost goals ## Documentation Vendor references for pricing and configuration. - [Object Versioning docs.cloud.google.com](https://docs.cloud.google.com/storage/docs/object-versioning) - [Object Lifecycle Management docs.cloud.google.com](https://docs.cloud.google.com/storage/docs/lifecycle) - [Soft delete overview docs.cloud.google.com](https://docs.cloud.google.com/storage/docs/soft-delete) - [Storage pricing cloud.google.com](https://cloud.google.com/storage/pricing) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - GCP GCS CER-0472 ### [Soft Delete Retention on High-Churn Cloud Storage Buckets](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 days, and new buckets get it unless an organization changes the default. Soft-deleted data... 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.