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

Pay-as-You-Go

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-11-28 17:46:02
Pay-as-you-go (postpaid) is the default billing mode of COS supported in all regions as described in Regions and Access Endpoints, where you use resources first and pay later. Fees of various billable items are calculated, settled, deducted, and billed daily.
If you have a detailed estimation of the amount, it is recommended to use resource package (prepaid) to enjoy more discounts. You can purchase the resource package required on the purchase page.

Pricing

For pay-as-you-go pricing of COS, see Pricing | Cloud Object Storage.

Billable Items

COS billable items are calculated as follows:
Billable Item
Description
Calculation Formula
Storage usage fees
Calculated based on the storage usage at a unit price that varies by storage class.
Storage usage fees = monthly unit price / 30 * daily storage usage * number of days
Daily storage usage = sum of "5-minute usage" / 288 (number of statistical points)
Request fees
Calculated based on the number of requests at a unit price that varies by storage class.
Request fees = unit price per 10,000 requests * daily accumulated number of requests / 10,000
Data retrieval fees
Calculated based on the volume of data retrieved at a unit price that varies by storage class. This billable item applies when data in the STANDARD_IA or ARCHIVE storage class is downloaded.
Data retrieval fees = unit price per GB * daily amount of data retrieved
Traffic fees
Calculated based on the public network downstream traffic, CDN origin-pull traffic, cross-region replication traffic, and global acceleration traffic at a unit price that varies by traffic type.
Traffic fees = unit price per GB * daily accumulated traffic
Management feature fees
Fees incurred by management features that you enabled and used, including inventory, extraction, batch operation, and object tagging.
Inventory fees = unit price per million objects listed * number of objects listed / 1 million
COS extraction fees = unit price per GB * daily accumulated amount of data extracted
Batch operation fees include job fees and object processing fees.

Job fees = unit price per job * number of jobs created
Object processing fees = unit price per 10,000 objects processed * number of objects / 10,000
Object tagging fees = unit price per 10,000 tags * number of tags / 10,000
Note:
For more information on billable items and billing restrictions, see Traffic Fees.
288 (number of sampling points) refers to the 5-minute count within 24 hours, with a statistical period from 00:00:00 to 23:59:59. Therefore, there are 288 daily samplings, or 288 sampling points.

Billing Cycle

COS billable items are billed daily as detailed below:
Billable Item
Billing Cycle
Description
Storage usage fees
Daily
Fees incurred between 00:00 and 23:59:59 on a day are settled the next day.
Request fees
Daily
Fees incurred between 00:00 and 23:59:59 on a day are settled the next day.
Data retrieval fees
Daily
Fees incurred between 00:00 and 23:59:59 on a day are settled the next day.
Traffic fees
Daily
Fees incurred between 00:00 and 23:59:59 on a day are settled the next day.
Management feature fees
Daily
Fees incurred between 00:00 and 23:59:59 on a day are settled the next day.
Note:
Bills in the system may have a certain delay. Daily bills are generated at around 08:00 AM.

Examples

Assume that on March 1, 2019, user A activated COS and uploaded 100 GB of files to the STANDARD storage class in a bucket in Beijing region. On March 15, the user downloaded 10 GB of data over the public network. 10,000 STANDARD read/write requests were generated. Apart from these operations, the user did not perform any other operations in March.
Therefore, the following fees were incurred in March:
STANDARD storage usage fees: The storage usage fees for 100 GB of data in the month.
Traffic fees: The public network downstream traffic fees for 10 GB of data in the month.
Request fee: The request fees for 10,000 STANDARD read/write requests in the month. Among them, uploading data generated STANDARD write requests, and downloading data generated STANDARD read requests.
Note:
To learn about the detailed cost calculation of COS and billing details in different scenarios, please see Billing Examples.
To view the COS billing statement, see the operation guide for Viewing and Downloading Bill.


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan