tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Data Retrieval Fees

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2025-10-29 16:15:39
Retrieving data stored in the STANDARD_IA, MAZ_STANDARD_IA, ARCHIVE, MAZ_ARCHIVE or DEEP_ARCHIVE storage class incurs data retrieval fees, which will be charged by the size of the retrieved data.
Note:
For more information on storage classes, see Storage Class Overview.

Data Retrieval Fees Billable Item

STANDARD_IA / MAZ_STANDARD_IA Data Retrieval Fees

Billable Item Description
Applicable Storage Class
Applicable Billing Mode
Data stored in STANDARD_IA / MAZ_STANDARD_IA can only be read/downloaded after it is restored. The data retrieval fees are calculated based on the size of the object.
STANDARD_IA
MAZ_STANDARD_IA
Pay-as-you-go
Note:
If you configure a lifecycle policy for low-frequency storage data (such as setting low-frequency storage data to settle into archive storage or DEEP_ARCHIVE), retrieval fees and request fees will occur during the execution lifecycle policy.

ARCHIVE / MAZ_ARCHIVE / DEEP_ARCHIVE Data Retrieval Fees

Billable Item Description
Applicable Storage Class
Applicable Billing Mode
For Archive Type data (such as ARCHIVE, DEEP_ARCHIVE), the data cannot be read or downloaded before it is restored (thawed). To access and download such data, you must first restore it as a STANDARD storage class copy. In this case, data retrieval can also be referred to as data thawing (the process of restoring archived data to standard data).
Fees are categorized based on different archive types (such as ARCHIVE, DEEP_ARCHIVE) and retrieval modes as follows:
ARCHIVE Expedited Retrieval Fees
ARCHIVE Standard Retrieval Fees
ARCHIVE Bulk Retrieval Fees
DEEP_ARCHIVE Standard Retrieval Fees
DEEP_ARCHIVE Bulk Retrieval Fees
ARCHIVE
MAZ_ARCHIVE
DEEP_ARCHIVE
Pay-as-you-go

Billing Mode and Calculation Formula

Billing Mode
Applicable Billable Items
Calculation Formula
Pay-as-You-Go
STANDARD_IA Data Retrieval Fees
MAZ_STANDARD_IA Data Retrieval Fees
ARCHIVE Storage Data Retrieval Fees
MAZ_ARCHIVE Storage Data Retrieval Fees
DEEP_ARCHIVE Data Retrieval Fees
Daily billed cycle
Data retrieval fees = unit price per GB * daily amount of data retrieved
Note:
Objects in different storage types vary in retrieval time and fees. For details, see Storage Class Overview and Pricing | Cloud Object Storage.. Among them:
STANDARD: No need to retrieve data, no data retrieval fees.
STANDARD_IA: Data needs to be retrieved with no waiting and fast reading. Data retrieval fees are billed based on usage.
ARCHIVE: Data needs to be retrieved with three supported retrieval modes. Duration and fees vary by mode. Data retrieval fees are pay-as-you-go.
Expedited retrieval mode: Recovery tasks can be completed in 1-5 minutes.
Standard retrieval mode: Recovery tasks complete within 3-5 hours.
Bulk retrieval mode: Recovery tasks complete within 5-12 hours.
DEEP_ARCHIVE: Data needs to be retrieved with two supported retrieval modes. Duration and fees vary by mode. Data retrieval fees are pay-as-you-go.
Standard retrieval mode: Recovery time is 12-24 hours.
Bulk retrieval mode: Recovery time is 24-48 hours.
INTELLIGENT_TIERING: Only expedited retrieval for the archive tier in intelligent tiering storage is charged, which aligns with archive storage expedited retrieval. Retrieval of other storage type data is free of charge.
Data retrieval fees are charged based on the actual data amount retrieved, and are determined by the actual completion time of the retrieval task, not the request initiation time.
Example:
User A triggered a standard retrieval request for 10GB of deep archived data on September 14, 2025. The retrieval task was completed on September 15, 2025. Later, User A initiated another standard retrieval request for 5GB of deep archived data on September 15, 2025, and the task was done on September 16, 2025.
Since data retrieval fees are settled daily, the payments generated by the above two retrieval tasks were deducted on September 16, 2025 and September 17, 2025, corresponding to the actual data retrieval completion on September 15, 2025 and September 16, 2025 respectively.

Data Retrieval Pricing

For the unit prices of data retrieval, see Pricing | Cloud Object Storage.

Billing Examples

Note:
Prices in the following examples are for reference only. For the actual prices, see Pricing | Cloud Object Storage.
The storage capacity is calculated in binary, for example, 1 TB = 1024 GB.

Example: STANDARD_IA storage usage fees + STANDARD_IA data retrieval fees + STANDARD_IA request fees + Public downstream traffic fees

Assume that on November 1, 2020, user B uploaded 5 GB of data to a bucket residing in Guangzhou region in the STANDARD_IA storage class, generating 100 requests. On November 2, user B read the data over the public network with CDN disabled, generating 100 requests. Apart from these operations, user B did not perform any other operations. As fees for a day were settled the next day, then:
STANDARD_IA storage usage fees: Settled daily starting from November 2, 2020.
STANDARD_IA Data retrieval fees: Settled on November 2, 2020.
STANDARD_IA request fees: Settled on November 2 and 3, 2020.
Public network downstream traffic fees: Settled on November 3, 2020.
Fees analysis:
STANDARD_IA storage usage fees = 0.018 USD/GB/month / 30 * 5 GB * 30 days = 0.09 USD
STANDARD_IA data retrieval fees = 0.002 USD/GB x 5 GB = 0.01 USD
STANDARD_IA request fees = 0.01 USD/10,000 requests * 100 requests / 10,000 * 2 = 0.0002 USD
Public downstream traffic fees = 0.1 USD/GB x 5 GB = 0.5 USD
In summary, the total bill for user B in November is calculated as follows: 0.09 + 0.01 + 0.0002 + 0.5 = 0.6002 USD.

Ajuda e Suporte

Esta página foi útil?

comentários