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
DokumentasiCloud Object StorageAPI DocumentationData Processing APIsImage ProcessingBasic Image ProcessingGIF Frame Extraction

GIF Frame Extraction

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-01-09 10:57:02

Feature Overview

Cloud Infinite provides GIF frame extraction functionality through the imageMogr2 API. This feature supports the following processing methods:
Processing during download
Processing during upload
Processing in the cloud

Authorization Guide

When used with a sub-account, corresponding permissions must be granted. For details, please refer to Cloud Object Storage. For other CI permissions, please refer to Cloud Infinite.
Processing during download: Set action to cos:GetObject in the authorization policy.
Process upon upload: Set action to cos:PutObject in the authorization policy.
Cloud data processing: Set action to cos:PutObject in the authorization policy.
Note：
The resource corresponding to GetObject is the source file, and the resource corresponding to PutObject is the transferred file.

Service Activation

Using this feature will activate Cloud Infinite for you by default and bind a bucket. No role authorization is required, it can be used directly.

Use Limits

When using this API, please first confirm the relevant restrictions. For details, see Specifications and Limits.
Supported formats: Supports processing GIF, WebP formats.
Volume limit: GIF original image width × height × frame count not exceeding 250 million pixels; WebP original image width and height not exceeding 16,383 pixels.
Animated image frame limit: Number of frames limited to 300.

Fee Description

This API is a paid service. The incurred fees will be collected by Cloud Infinite. For detailed billing information, see Image Processing Fees.
If processing during download is adopted and the download is performed via the public network, the API call will incur Traffic Fees.

API Example

1. Processing during download

GET /<ObjectKey>?imageMogr2/cgif/<FrameNumber>
                           /egif/<FrameInterval> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: <GMT Date>
Authorization: <Auth String>
Note:
Ignore the spaces and line breaks above.

2. Processing during upload

PUT /<ObjectKey> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Authorization: Auth String
Pic-Operations: 
{
  "is_pic_info": 1,
  "rules": [{
      "fileid": "exampleobject",
      "rule": "imageMogr2/cgif/<FrameNumber>
                         /egif/<FrameInterval>"
  }]
}

3. Processing in the cloud

POST /<ObjectKey>?image_process HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Content-length: Size
Authorization: Auth String
Pic-Operations: 
{
  "is_pic_info": 1,
  "rules": [{
      "fileid": "exampleobject",
      "rule": "imageMogr2/cgif/<FrameNumber>
                         /egif/<FrameInterval>"
  }]
}
Note:
Authorization: Auth String. For details, see Request Signature documentation.
Pic-Operations is a JSON format string. For specific parameter details, refer to Persistent Image Processing.
When fileid is the same as ObjectKey, the processed image will overwrite the original image storage; if they are different, both the original image and the processed image will be stored separately.
The value of fileid needs to be passed through URL-safe Base64 encoding.

Processing Parameter Description

Parameter
Meaning
Type
Required
ObjectKey
Object filename, for example folder/sample.gif.
String
Yes
/frame/
Extract a single frame from a GIF (processing during download only): You can specify to extract the Nth frame of the GIF, where N is a positive integer (1, 2, 3...). If N exceeds the maximum frame number of the GIF, the last frame will be taken. For example, to extract the 1st frame of a GIF, the parameter is /frame/1.
Int
No
/cgif/
GIF format optimization (frame extraction type): Optimized for original images in GIF or WebP format, this optimization involves extracting frames and reducing image colors. It is divided into the following two scenarios:
If FrameNumber = 1, the default frame count of 30 is used. If the image frame number is larger than this, frames will be extracted to reduce to 30.
If FrameNumber is in the range (1,100], the image will be compressed to the specified number of frames (FrameNumber).
String
No
/egif/
GIF format optimization (frame sampling type): Optimized for original images in GIF or WebP format, this optimization involves reducing image colors and extracting target frames at a certain frame interval (FrameInterval) for output.
FrameInterval takes values in the range [1,10].
String
No
/ignore-error/1
When processing requests carry this parameter, if operations fail due to oversized files or parameter exceeds limit, it will directly return the original image without reporting an error.
String
No
Note:
When both cgif and egif parameters are selected, prioritize processing cgif.

Practical Example

Note:
The examples in this documentation contain only processing during download. This type of processing will not save the processed images to the storage bucket. If you have a need to save, you can check the Persistent Image Processing document and configure processing during upload or processing in the cloud.
Capture the first 10 frames of a GIF:
http://examples-125xxxxxx.cos.ap-shanghai.myqcloud.com/sample.gif?imageMogr2/cgif/10

Important Notes

To prevent unauthorized personnel from accessing and downloading the original images through links that do not carry processing parameters, you can include the processing parameters in the request signature. The processing parameters are the key in the parameters with an empty value. A simple example is provided below (for reference only; the link may be expired and inaccessible). For detailed calculation methods, please refer to Request Signature.
http://examples-1251000004.cos.ap-shanghai.myqcloud.com/sample.jpeg?q-sign-algorithm=sha1&q-ak=**********************************&q-sign-time=1593342360;1593342720&q-key-time=1593342360;1593342720&q-header-list=&q-url-param-list=watermark%252f1%252fimage%252fahr0cdovl2v4yw1wbgvzlteyntewmdawmdqucgljc2gubxlxy2xvdwquy29tl3nodwl5aw4uanbn%252fgravity%252fsoutheast&q-signature=**************************************&watermark/1/image/aHR0cDovL2V4YW1wbGVzLTEyNTEwMDAwMDQucGljc2gubXlxY2xvdWQuY29tL3NodWl5aW4uanBn/gravity/southeast

Topik sebelumnya: Progressive DisplayTopik selanjutnya: Quality Change

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan