Image compression refers to reducing the image size as much as possible while maintaining the original image quality, thereby saving image storage space, reducing image access traffic, and improving image access speed.
Cloud Infinite (CI) introduced the WebP compression feature, which converts images into the WebP compressed format, outperforming JPG in compression. At the same image quality level, WebP images are over 25% smaller than JPG images, enabling adaptation to multi-terminal usage scenarios.
Authorization Description
When using a sub-account, you need to add the corresponding permission to the action in the authorization policy. For all supported API operations in Cloud Object Storage, see COS action.
Processing during download: Set action to cos:GetObject in the authorization policy.
Processing upon upload: Set action to cos:PutObject in the authorization policy.
Cloud data processing: Set action to cos:PutObject in the authorization policy.
Note:
GetObject resource is the source file, PutObject resource is the transferred file.
Service Activation
The first time you use this feature, Cloud Infinite (CI) will be activated for you by default, and the bucket will automatically bind CI with no need for role authorization, allowing you to use it directly.
Note:
After binding Cloud Infinite, if you manually perform bucket unbind for CI, you will not be able to continue using this function.
Use Limits
When using this API, please confirm the relevant restrictions. For details, see Usage Limits.
Fee Instructions
WebP compression is a paid service with the same fee as basic image processing. For specific fees, see Image Processing Fees. Generated costs will be charged by CI.
If processing during download is used and the download is performed via public network, traffic charges will occur.
Note:
After converting an image to WebP format, some browsers cannot read the exif data of WebP images, resulting in no rotation. See the rotation document and add the auto-orient parameter to rotate the original image before compression.
WebP compression inherits the original image's quality parameters by default. See the quality change document to adjust the compression rate by changing the image quality.
Authorization: A request header carrying authentication information to verify the validity of the request. The Pic-Operations header should be signed within the signature information. For details, see Request Signature.
When the fileid is the same as the ObjectKey, the output image will overwrite the input image for storage; otherwise, both the input and output images will be stored separately.
The value of fileid needs to be processed through URLEncode.
Processing Parameter Description
Parameter
Description
Type
Required or Not
ObjectKey
File name of the object, for example, folder/sample.jpg.
String
Yes
/format/<Format>
Compression format (here is WebP).
String
Yes
Practical Case
Note:
The practical cases in this document only include the Processing upon Download scenario. This type of processing does not save the output images to the bucket. If you need to save them, please use the Process upon Upload or Cloud Data Processing method.
Assume the input image is in PNG format with a size of 1335.2 KB, as shown in the figure below.
Convert the input image to WebP format. The request URL is as follows.
