Summary

  • Overwriting an object in an unversioned Wasabi bucket does not immediately stop billing for the previous object. The replacement starts its own minimum-age clock while the earlier generation can remain chargeable as deleted storage.
  • If Wasabi changes an account's minimum duration from 90 to 30 days, the shorter period applies only to subsequent uploads. Earlier objects keep the original treatment; a new billing cycle does not erase that history.
  • Price changes, active-storage minimums, contractual capacity and billable object size have separate boundaries. A current filename or raw-byte total cannot, by itself, explain the invoice.

A small application updates the same object every day. Its operator sees one name and one current file. That is a reasonable description of the application. It may be a poor description of the storage bill.

Wasabi's documentation gives an unusually clear example. In an unversioned bucket, each overwrite implicitly deletes the previous object. The old object can remain billable until its minimum-age requirement runs out, while the replacement begins a new billing life. Repeat a same-name upload daily for 30 days and, in the company's illustration, as many as 30 generations may overlap in billing: one current object and up to 29 deleted ones. Versioning need not be enabled for this effect. Billing for overwrites and deleted storage.

The example is not evidence of a billing error or a customer incident. It exposes the unit being sold. The application presents a current object; the supplier bills the relevant object generations over time. An action that looks like replacement to a user can be an additional commitment in the account's economic history.

That distinction matters more than a slogan about predictable pricing. A simple rate can be predictable only if the buyer also understands which population of objects is charged, for how long, and under which account and contract. The public rules are disclosed. The challenge is making operational decisions and budget ownership follow them.

Deletion ends one thing, not everything

The default minimum storage duration for ordinary object-storage Pay-Go customers is 90 days. Wasabi's Reserved Capacity Storage model, or RCS, has a 30-day minimum; Cloud NAS and Surveillance Cloud Pay-Go also have shorter stated minima. The default is therefore not universal across every product and contract.

Under the documented 90-day example, an object stored on day one and deleted on day sixteen generates 15 days of active storage and 75 days of timed-deleted storage. The remaining charge is a minimum-duration obligation, not evidence that the customer still has a usable file. Wasabi separately states that a deleted file cannot be recovered. Paying for the remainder of the minimum is not buying a recovery window. Minimum-duration policy; deletion and recovery boundary.

This article's central case is an unversioned overwrite. A versioned bucket can preserve older versions, and a delete marker is not the same as permanently deleting every version. Immutability introduces another distinction: protected objects remain active storage until their applicable retention conditions allow deletion. A billing minimum should not be confused with a security setting or an instruction to retain data longer than it is needed.

For a business that frequently replaces objects, the relevant question is therefore not just “how much do we store?” It is “how many recent generations have we created, and when does each stop being billable?” The current application view answers the first question imperfectly and the second hardly at all.

A better future rule does not rewrite older uploads

Suppose an account obtains a change from a 90-day to a 30-day minimum. Wasabi documents a prospective boundary: the new period applies to objects uploaded after the change. Objects uploaded beforehand retain the original 90-day treatment. The shorter minimum is not a retroactive repricing of their duration.

There is a separate administrative event. If Wasabi implements the change, the current billing cycle ends and a new one begins on that date. An invoice is produced for usage up to the change, with the corresponding card charge. The invoice boundary and the object-age boundary are related events, but they do not do the same job. Closing one billing period does not say that older obligations have disappeared. Changing the minimum duration.

This is easy to miss in a purchasing review. The commercial team can truthfully report that it has obtained a better minimum for new data. Finance can truthfully continue to see charges associated with older data. Neither fact establishes that the other team made a mistake. They are looking at different cohorts.

Nor should a buyer assume that deleting and uploading everything again is a free way to move to the new rule. An actual early deletion can leave its old-duration obligation, and a new upload starts another object's clock. This is a description of the documented mechanism, not a recommendation to move or delete data. The economic consequence must be evaluated before operational changes are made, alongside the requirement to protect and lawfully manage the data itself.

The price has its own effective date

The published Hot Cloud Storage Pay-Go rate became $7.99 per TB per month across North America, EMEA and APAC from 1 July 2026. The notice affects the stated current and new Pay-Go accounts. Its accompanying FAQ says existing affected customers see the new plan on the first billing cycle on or after that date. That is a price-plan transition, not an announcement that all object minimum ages have changed. July pricing notice; pricing-change FAQ.

RCS follows a different contractual boundary. New or renewing contracts use the updated base with term and capacity discounts. Existing RCS contracts in place before 1 July are excluded for their existing term, but the notice expressly separates overages: those use the new pricing from 1 July. Contracted pricing, including Pay-Go Flex, is excluded from the general change. Customers buying through a reseller or managed service provider need their own provider's price, not an assumption that a public tariff exactly reproduces their agreement.

Consequently, a grandfathered capacity contract does not necessarily grandfather every additional unit. A discounted capacity rate does not automatically change an earlier object's duration rule. These are separate questions to take to the invoice and agreement. The public material does not permit a universal prediction of every customer's total charge.

The headline price also excludes taxes and optional services. No current comparison with a competing provider is attempted here. A ranking based on one storage rate would omit precisely the workload and contractual boundaries that make this case interesting.

Floors sit underneath activity; old charges can sit beside it

Ordinary Pay-Go has a monthly active-storage minimum equivalent to one billing TB. Below that amount, the active-storage charge and its minimum top-up together reach $7.99 at the stated public rate. The documented floor applies even to an empty account. This does not mean that all other chargeable storage is absorbed into one fixed payment: timed-deleted storage is a separately described invoice component. Pay-Go pricing and invoice components.

A control account also does not turn every linked customer into one pooled minimum. Wasabi says control accounts and subaccounts can each qualify for their own active-storage floor. Its illustration has two accounts jointly storing 750 billing GB but carrying a combined two-TB minimum and an active-storage bill of at least $15.98 at the public rate. That floor combines actual active usage and its minimum top-up; it is not the top-up alone. The same combined usage in one standalone account would have a different floor. Account organisation can therefore affect cost independently of the visible payload. Contract-specific partner pricing still needs separate verification. Monthly minimum policy.

There is a smaller scale boundary as well. Wasabi's public FAQ sets a minimum billable file size of 4 KB; a smaller file is charged at that size. Versioned objects and bucket logs can add stored material. These rules should not be collapsed into one generic “minimum”. Object-size padding, an account's active-storage floor and an object's minimum duration operate on different things.

For unit calculations, the provider uses base two while labelling its billing units GB and TB. Its billing TB is 1,099,511,627,776 bytes, equal to 1,024 of its billing GB. A decimal-byte inventory should not be joined to the invoice without conversion. This is a disclosed convention, not itself a surcharge. Billing-unit convention.

Reconcile the billable population

Wasabi separates current raw bytes, current bytes padded to the minimum object size, and deleted-but-still-billable bytes. The last category is where repeated overwrites can leave a large difference between what the application currently presents and what the account owes. The useful explanation is the age and treatment of each generation, not an accusation prompted by an apparently surprising total.

The downloadable utilisation report adds time. It records UTC measurement periods and distinguishes raw active, billable active and billable deleted usage in GiB-days. It can include buckets that have already been deleted; repeated bucket names therefore need not indicate duplicate charging. Bucket identifiers and measurement periods help distinguish the records. A newly created bucket can take up to 24 hours, including one completed billing cycle, to appear in the export. A current utilisation estimate is not a final invoice or a real-time spending stop. Billing overview and utilisation export.

The right commercial record connects an upload or overwrite date with its applicable minimum, the account owning the charge, and the relevant price plan. It also distinguishes an old cohort ageing out from a fall in current data. Without that record, a developer may see a constant working set while finance sees a growing bill, with neither view sufficient to explain the other.

A disclosed trade-off, not an unlimited promise

Stable data kept for long periods can fit this model well. If few young objects are replaced, the gap between current data and recent deleted generations can remain limited. A low capacity rate without ordinary API or egress line items can be commercially attractive. That countercase is important: the existence of a minimum does not establish that the offer is deceptive or unsuitable for every workload.

“No egress charge” is nevertheless not the same as unrestricted use. Wasabi's public guideline treats monthly downloads no greater than active storage as a suitable fit; repeated excess can lead to service limits or suspension. It does not provide a universal per-GB overage tariff for that situation. The API policy also distinguishes reasonable use from inefficient, unreasonable load. The July pricing FAQ says those policies were not changed by the price announcement. No enforcement incident or customer breach has been examined here. Public usage policies.

Capacity contracts change the trade-off again. Ordinary RCS describes overage billing; RCS Capped prevents new uploads when purchased capacity is reached until the customer frees space or purchases more. That is an ingestion boundary, not merely a smaller invoice and not a stated denial of access to existing objects. Product and pricing-model terms.

The central conclusion is narrower than “cheap storage is expensive”. Storage economics depend on the decisions that create billable generations and on the dates that retire them. One filename can hide several such decisions. A new plan can improve the next decision without undoing the previous ones.