CI supports scaling, cropping, transcoding, watermarking, and more to meet your image processing needs.
Currently, CI supports JPG, BMP, GIF, PNG, and WebP, as well as HEIF decoding and processing. For more information, please see Rules and Limits.
The size of an input image cannot be larger than 20 MB, its width and height cannot exceed 30,000 pixels, and the total number of pixels cannot exceed 250 million. The width and height of the output image cannot exceed 9,999 pixels. For a source animated image, Width x Height x Number of frames cannot exceed 250 million pixels.
CI uses Tencent Cloud Object Storage (COS) to store data. You can process images during the upload and store the results persistently in COS, or process images during the download.
You can use COS Migration Tool or Migration Service Platform (MSP).
Source bucket names and the corresponding List permissions are required for the migration.
You can use the image origin-pull feature of COS to bind COS buckets to your origin server, then replace the image processing domain name with the CI domain name (CI pulls original images from the origin server and then processes them, while COS pulls images asynchronously.) In this method, only resources that you request will be migrated.
Yes. All you need to do is add the processing parameters in the CDN file URL.
Yes, you can achieve this by using style separators. For example, with url?imageMorg2/cut/400x400|watermark/1/xxx, you can crop an image and add a watermark at the same time.
Basic image processing (e.g., scaling, cropping, transcoding, and watermarking) is charged at 0.01 USD/GB. Advanced features (e.g., content recognition, blind watermarking, and Guetzli) are charged additionally. For detailed pricing, please see Billing and Pricing.
Processed images will be stored through APIs. Images processed during downloading will not be stored in customers’ storage.
Yes. You can also process images already stored in COS buckets.
Yes. You can encrypt URLs based on our encoding and decoding rules. Encrypted access is a customized feature. If you want to use it, please submit a ticket.
Take cropping + watermarking as an example, use the pipeline operator l to connect respective processing parameters, and then both operations will be performed in sequence.
Take the pipeline operator (|) as an example. It will be escaped or truncated by the WeChat Mini Program. Therefore, you need to redefine it.
One possible cause is that the EXIF information of the input image accounts for the majority of the image size. If the image size shows little change after you adjust the image resolution, use the strip parameter to remove the EXIF information. For instructions, see Removing Meta Information.
The possible causes are as follows:
http://. In this case, HTTP cannot be omitted and HTTPS cannot be used.
Many parameters of CI’s image processing (e.g., text, color, and font of the text watermark, as well as the URL of the image watermark) need to be Base64 URL-safe encoded. The rules are as follows:
CI will return 302 and redirect you to the URL of the image in COS for you to download the input image.
Guetzli is an image compression feature with no visual quality loss launched by CI. Once Guetzli is enabled, images in the bucket will be compressed with Guetzli upon the download, and
x-GuetzliState will be added to the HTTP header of the request to indicate the compression status. If Guetzli does not take effect, you can:
examplebucket-1250000000.picgz.myqcloud.comand try again. Currently, using COS endpoints (format:
examplebucket-1250000000.cos.ap-guangzhou.myqcloud.com) for processing is not supported for some users.