Paste a line item from your invoice and find what it bills for, across the Google Cloud services covered so far.
Early Delete (EarlyDelete-ByteHrs)
A charge for deleting, replacing, or rewriting an object before its storage class minimum duration has elapsed.
You are billed as though the object had stayed for the full period. It is one of the least self-explanatory SKU names on a Google Cloud bill and one of the easiest to eliminate.
Billed: Byte-hours for the unused remainder of the minimum storage duration (Nearline 30 days, Coldline 90, Archive 365), billed when the object is deleted, replaced, or rewritten.
What triggers this charge
- Deleting a Nearline object before 30 days, Coldline before 90, or Archive before 365.
- Overwriting an object in a cold class, which replaces it: the replaced object is charged for the rest of its minimum.
- Changing an object's storage class by rewriting it, the manual way, which also counts as a replacement. A lifecycle rule changing the class does not rewrite, and is exempt.
- A lifecycle rule that moves objects to a colder class plus a delete rule that removes them before that class minimum is met. The move itself is free and the object's age carries over, but the deletion is charged for the shortfall.
- Re-uploading a backup with the same name daily into a cold class.
- Soft delete and versioning: an object that becomes soft deleted or noncurrent is charged only once it is eligible for permanent deletion, and the time it spent soft deleted or noncurrent counts toward the minimum.
- Unused or overwritten parts of an XML API multipart upload, and aborted uploads, which are charged as early deletions too.
How to reduce it
Align storage-class transitions with the planned deletion date
Count the object's total age at deletion against the minimum of the class it will be in by then. A lifecycle move to Coldline at day 30 followed by deletion at day 60 leaves the object 30 days short of the 90-day Coldline minimum, and that shortfall is billed. Stop at Nearline, whose 30-day minimum is already met, or keep the data to day 90.
Prefer Standard for frequently overwritten objects
Every overwrite of a cold-class object bills the unused minimum of the object it replaces. Nearline may still make sense when object lifetime and access patterns justify its 30-day minimum and retrieval charges, for example a file replaced monthly and rarely read.
Change classes with lifecycle rules, not rewrites
A lifecycle SetStorageClass action carries no early-deletion or retrieval fee at transition time. A manual rewrite to a new class carries both. Either way the change is billed as a Class A operation at the destination class rate.
Consider Autoclass when access is unpredictable
Autoclass buckets do not incur early-deletion charges, except within the one-time enablement charge on existing objects. Weigh that and the monthly management fee against the charges it avoids.
Rates
Sources and review
- Explanation reviewed:
- 1 Nov 2026, against Cloud Storage pricing, the storage classes docs, the Object Lifecycle Management docs and the Autoclass docs.
- Rates verified:
- not yet. No rate is shown on this page until one is loaded from the Cloud Billing Catalog API.
Related charges
Now find out how much of this you are actually paying.
Finitizer breaks your Google Cloud bill down to the SKU, shows how each one has moved since last week, and separates rate changes from usage changes, so you know whether to talk to engineering or to procurement.
See how Finitizer works