Storage fees
OSS charges storage fees based on the storage class, size, and duration of objects in a bucket, regardless of access or operations performed.
Unit price
For unit prices of each billable item, see .OSS product pricing
The OSS product pricing page specifies storage unit prices in CNY per GB-month, but billing items are calculated hourly using the formula: Actual resource usage × Hourly unit price. Therefore, to calculate actual storage fees, you need to convert the storage unit price to CNY per GB-hour. For example, the Standard (LRS) unit price is 0.12 CNY/GB/month, so the hourly unit price is approximately 0.000167 CNY/GB/hour (0.12 ÷ 30 ÷ 24).
Billable items
Storage fees for a specified storage duration
Storage fees are based on the storage class, redundancy type, size, and duration of each object.
Storage fees for early deletion (less than minimum duration)
Some storage classes have a minimum storage duration: 30 days for Infrequent Access (IA), 60 days for Archive, and 180 days for Cold Archive and Deep Cold Archive. If an object is converted or deleted before meeting the minimum duration, you are charged for the remaining duration.
Example: If an IA LRS object is deleted after less than 30 days (720 hours), you are charged for the remainder (720 hours - actual duration). The same calculation applies to Archive, Cold Archive, and Deep Cold Archive objects with their respective minimum durations.
Storage usage of LRS objects that are stored for a specific period of time
Billable item | Code | Minimum billable size |
Storage usage of Standard LRS objects | Storage | N/A (billed by actual size) |
Storage usage of IA LRS objects | ChargedDatasize | 64 KB (Objects smaller than 64 KB are billed as 64 KB. Objects 64 KB or larger are billed by actual size.) |
Storage usage of Archive LRS objects | ChargedDatasize | |
Storage usage of Cold Archive LRS objects | ChargedDatasizeCA | |
Storage usage of Deep Cold Archive LRS objects | ChargedDatasizeDeepCA | |
Anywhere Reserved Capacity | AnywhereReservedCapacityLRS | N/A (billed by actual size) |
The billed storage usage of IA, Archive, Cold Archive, or Deep Cold Archive objects is larger than the metered storage usage of these objects because each object has a minimum billable size of 64 KB. For more information about the metered storage usage and billed storage usage of these objects, see Query the storage capacity of a bucket (OSS SDK for Java 1.0).
Storage usage of ZRS objects that are stored for a specific period of time
Billable item | Code | Minimum billable size |
Storage usage of Standard zone-redundant storage (ZRS) objects | StorageZRS | N/A (billed by actual size) |
Storage usage of IA ZRS objects | ChargedDatasizeZRS | 64 KB (Objects smaller than 64 KB are billed as 64 KB. Objects 64 KB or larger are billed by actual size.) |
Storage usage of Archive ZRS objects | ChargedDataSizeArcZRS |
Storage usage of LRS objects that are stored for less than the minimum storage duration
Billable item | Code | Calculation method of the minimum storage duration |
Storage usage of IA LRS objects that are stored for less than the minimum storage duration | LessthanMonthDatasize | The minimum storage duration is calculated based on the last modified time of the objects. |
Storage usage of Archive LRS objects that are stored for less than the minimum storage duration | LessthanMonthDatasize | |
Storage usage of Cold Archive LRS objects that are stored for less than the minimum storage duration | EarlyDeletionCA | The minimum storage duration is calculated based on the time when the storage class of the object is converted to Cold Archive or Deep Cold Archive. |
Storage usage of Deep Cold Archive LRS objects that are stored for less than the minimum storage duration | EarlyDeletionDeepCA |
To avoid unnecessary fees, ensure objects meet the minimum storage duration before converting or deleting them. For information, see How can I avoid being charged for the storage usage of objects that are stored for less than the minimum storage duration?
Storage usage of ZRS objects that are stored for less than the minimum storage duration
Billable item | Code | Calculation method of the minimum storage duration |
Storage usage of IA ZRS objects that are stored for less than the minimum storage duration | LessthanMonthDatasizeZRS | The minimum storage duration is calculated based on the last modified time of the objects. |
Storage usage of Archive ZRS objects that are stored for less than the minimum storage duration | LessthanMonthDatasizeArcZRS |
Billing methods
The following 5 billing methods are supported: pay-as-you-go, resource plans, reserved capacity, Anywhere Reserved Capacity, and storage capacity units (SCUs).
Instructions on selecting a billing method
The following table compares billing methods to help you select the most cost-effective option.
Billing method | Description | Feature | Scenario |
Pay-as-you-go | Default billing method. You pay for actual storage usage after consumption. | Unpredictable storage usage. | Startups or early-stage projects with unstable storage needs. |
Storage plans | Prepaid plans that offset fees for specific billable items at discounted rates. | Stable, predictable storage capacity. | Large enterprises or long-running projects with stable storage volumes. Storage plan specifications range from 40 GB to 20 PB. |
Prepaid product for region-specific storage billable items. Purchase first, then deduct. | Offsets only Standard LRS storage fees from region-specific buckets and ECS snapshot storage fees. | For stable, large-scale Standard LRS and ECS snapshot storage in region-specific buckets. Capacity ranges from 500 GB to 1 PB. | |
Prepaid product for region-independent storage billable items. Purchase first, then deduct. | Offsets only Standard LRS storage fees from region-independent buckets. | For stable, large-scale Standard LRS storage in region-independent buckets. Capacity ranges from 10 TB to 1 PB. | |
Prepaid SCUs offset storage fees for multiple OSS billable items. Purchase SCUs in advance to apply discounts. | SCUs offset storage fees for multiple OSS billable items and other Alibaba Cloud storage services. |
|
Billing methods supported by different billable items
The following table lists the billing methods supported by each billable item.
Billable item | Pay-as-you-go | Storage plan | Reserved Capacity | Anywhere Reserved Capacity | SCU |
Standard (ZRS) storage | √ | × | × | √ | |
Standard (LRS) storage | √ | √ | × | √ | |
IA (ZRS) storage | √ | × | × | √ | |
IA (LRS) storage | √ | × | × | √ | |
Archive (LRS) storage | √ | × | × | √ | |
Cold Archive (LRS) storage | √ | × | × | × | |
Deep Cold Archive (LRS) storage | √ | × | × | × | × |
Anywhere Reserved Capacity | √ | × | × | √ | × |
Archive (ZRS) storage | √ | × | × | × | |
IA (LRS) early deletion | √ | × | × | × | |
Archive (LRS) early deletion | √ | × | × | × | |
Cold Archive (LRS) early deletion | √ | × | × | × | |
Deep Cold Archive (LRS) early deletion | √ | × | × | × | × |
IA (ZRS) early deletion | √ | × | × | × | |
Archive (ZRS) early deletion | √ | × | × | × | × |
Billing examples
Troubleshooting Abnormal Storage Capacity
If you notice that your OSS storage capacity has increased unexpectedly, you can troubleshoot the issue using the following steps:
Check parts from incomplete multipart uploads: On the Bucket Overview page, view the number of parts from incomplete multipart uploads. Parts from incomplete multipart uploads consume storage space and are not automatically deleted by the ossutil sync command. To automatically clean up outdated parts, configure a lifecycle rule with the AbortIncompleteMultipartUpload action.
Check the minimum billable size for your storage class: Objects stored in Infrequent Access (IA), Archive, Cold Archive, or Deep Cold Archive storage classes are billed at a minimum size of 64 KB per object. If you store a large number of objects smaller than 64 KB, your billed storage usage may be significantly higher than the actual object sizes.
Check the minimum storage duration for Archive objects: Archive objects have a minimum storage duration of 60 days. Cold Archive and Deep Cold Archive objects have a minimum storage duration of 180 days. If an object is deleted or converted to a different storage class before the minimum storage duration ends, you are still charged for the remaining duration.
Account for statistics latency: Storage capacity statistics in the OSS console are updated with an average delay of 1 to 2 hours. After you make changes to your storage, wait for the statistics to update before verifying the results.
For comprehensive troubleshooting, combine approaches such as cleaning up parts, converting storage classes, and configuring lifecycle rules.
FAQ
After I purchase an IA (LRS) storage plan, why do I receive a large bill for the storage usage of IA LRS objects that are stored for less than the minimum storage duration in a specific billing cycle?
After I purchase an Archive (LRS) storage plan, why do I receive a large bill for the storage usage of Archive LRS objects that are stored for less than the minimum storage duration in a specific billing cycle?
Why am I continuously charged for the storage usage of objects that are stored for less than the minimum storage duration?
Why am I charged storage fees even though I have not actively uploaded files?
Does activating OSS without using it incur charges?
References
By default, the storage class of an uploaded object is Standard. To reduce costs, convert objects to IA, Archive, Cold Archive, or Deep Cold Archive as needed. Convert the storage class of an object.
For more information about the billing examples of IA, Archive, and Cold Archive and Deep Cold Archive objects that are stored for less than the minimum storage duration, see How am I charged for objects whose storage duration is less than the minimum storage duration?
You are charged for the parts that are generated during multipart upload based on the storage class, actual size, and storage duration of the parts. For more information, see How am I charged for parts?
For more information about how to query OSS hourly billing data, see Query hourly data of OSS.
To learn about billing details with specific examples, see Billing examples.
For more information about the billing details of the billable items, see Query bills.