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

Enabling Smart Compression

PDF
Focus Mode
Font Size
Last updated: 2026-01-09 14:32:50

Feature Description

Enable the intelligent image compression feature for the current bucket.

Authorization Description

When using with an authorized sub-account, the ci:SetImageSlim permission is required. For details, please see Authorize Sub-Account to Access Cloud Infinite Service. For other permission information, please refer to Cloud Infinite Actions.

Activating a Service

Call this API requires enabling the Cloud Infinite service in advance and binding a bucket. For details, see Binding a Bucket.

Use Limits

When using this API, please first confirm the relevant restrictions. For details, see Usage Limits.

Fee Description

Intelligent image compression is a paid service. The incurred fees will be collected by Cloud Infinite. For detailed billing instructions, please refer to Image Processing Fees.
If processing during download is adopted and the download is performed via the public network, the call will incur traffic charges.

Request

Request sample:

PUT /?image-slim HTTP/1.1
Host: <BucketName-APPID>.pic.<Region>.myqcloud.com
Date: GMT Date
Authorization: Auth String
Note:
Authorization: Auth String. For details, see Request Signature document.

Request header.

Common Headers

This request operation does not use special request header information. The used common request headers are detailed in the Common Request Headers chapter.

Request body.

<ImageSlim>
<SlimMode>Auto</SimMode>
<Suffixs>
<Suffix>jpg</Suffix>
<Suffix>png</Suffix>
</Suffixs>
</ImageSlim>
Node Name
Parent Node
Description
Type
Required
ImageSlim
No
Extreme compression configuration info
Container
Yes
SlimMode
ImageSlim
Usage modes of extreme compression, including two kinds:
API: The usage method for enabling the intelligent compression API. Once activated, images can be compressed using intelligent compression parameters during download.
Auto: The automatic usage method for enabling intelligent compression. Once activated, no parameters are required. Images in the specified format within the bucket will be automatically intelligently compressed when accessed.
Note: Supports enabling both modes simultaneously. Multiple values are separated by commas.
string
Yes
Suffixs
ImageSlim
This parameter is valid only when the value of SlimMode contains Auto. Used to specify image formats that require automatic compression.
Container
No
Suffix
Suffixs
Image formats requiring automatic compression, available values: jpg, png, gif
string
No, required when SlimMode contains Auto

Response

Response Headers

This response does not use special response headers. Only common response headers are used. For details about common response headers, see Common Response Headers chapter.

Response Body

The response body is empty.

Real Case

Request

PUT /?image-slim HTTP/1.1
Host: examplebucket-1250000000.pic.ap-shanghai.myqcloud.com
Date: Tue, 03 Apr 2019 09:06:15 GMT
Authorization:q-sign-algorithm=sha1&q-ak=**********************************&q-sign-time=1497530202;1497610202&q-key-time=1497530202;1497610202&q-header-list=&q-url-param-list=&q-signature=**************************************

<?xml version="1.0" encoding="UTF-8" ?>
<ImageSlim>
<SlimMode>Auto,API</SimMode>
<Suffixs>
<Suffix>jpg</Suffix>
</Suffixs>
</ImageSlim>

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 0
Date: Tue, 03 Apr 2019 09:06:16 GMT
x-cos-request-id: xxxxxxxxxxxxxxxxxx


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback