tencent cloud

Image Super Resolution
Download PDF
Last updated: 2025-09-09 20:02:19
Image Super Resolution
Last updated: 2025-09-09 20:02:19
Download PDF

Feature Description

Tencent Cloud Data Infinite performs super-resolution processing on images through the AISuperResolution API, with the current default super-resolution being 2 times the width and height.

Authorization Description

When using with a sub-account, corresponding permissions must be granted. For COS permissions, please refer to COS action. For CI permissions, please refer to Cloud Infinite action.
Processing during download: Set action to authorization policy as cos:GetObject, ci:CreateSuperResolutionJob.
Process upon upload: Set action to authorization policy as cos:PutObject.
Cloud data processing: Set action in authorization policy to cos:GetObject, cos:PutObject (Note: GetObject corresponds to the resource of the source file, and PutObject corresponds to the resource of the transferred file).

Service Activation

Using this feature requires enabling Cloud Infinite in advance and binding a bucket.
Use this feature requires enabling the AI Content Recognition service in advance through the console or API.

Use Limits

When using this API, please confirm the related Usage Limits.

Fee Description

This API is a paid service. The incurred fees will be collected by Cloud Infinite. For detailed billing instructions, please refer to Content Recognition Fees.


Processing Method 1: Processing during Download

Request

Request Syntax

 Original images are stored in COS. 
GET /<ObjectKey>?ci-process=AISuperResolution HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: <GMT Date>
Authorization: <Auth String>
The original image comes from another link.
GET /?ci-process=AISuperResolution&detect-url=<detect-url> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: <GMT Date>
Authorization: <Auth String>

Request Content

Operation name: AISuperResolution
Parameter
Meaning
Type
Required or Not
ObjectKey
object filename, for example: folder/document.jpg
String
No
ci-process
CI processing capability, Image Super Resolution fixed as AISuperResolution
String
Yes
detect-url
You can handle any publicly accessible image link by filling in detect-url. If detect-url is not filled in, the backend will process ObjectKey by default. If detect-url is filled in, the backend will process the detect-url link, and there is no need to fill in ObjectKey.
detect-url example: http://www.example.com/abc.jpg, needs to be UrlEncoded, processed as http%3A%2F%2Fwww.example.com%2Fabc.jpg.
String
No
magnify
Target magnification times, optional parameters 2, 4, default is 2
int
No

Response

HTTP/1.1 200 OK
Content-Type: image/png
Content-Length: 98645
Date: Tue, 23 Apr 2022 09:06:16 GMT
Status: 200 OK
x-cos-request-id: NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****

[pic-content]
The processed image is returned directly in the response body.

Processing Method 2: Process Upon Upload

Request

Request Syntax

PUT  /<ObjectKey> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Authorization: Auth String
Pic-Operations: <PicOperations>
Note:
Authorization: Auth String (For details, see Request Signature document).

Request header.

This API only uses common request headers. For details, see the Common Request Headers document.
In addition to the common headers, the following headers need to be provided:
Header Name
Description
Type
Pic-Operations
Parameters for image operations
String
Pic-Operations is a json format string, with the following specific parameters:
Parameter Name
Description
Type
Required or Not
is_pic_info
Whether to return original image information, 0 means do not return original image information, 1 means return original image information, default is 0
Int
No
rules
Processing rules, one rule corresponds to one processing result (currently supports five rules), leave blank to skip image processing
Array
No
Each item in the rules (json array) has the following specific parameters:
Parameter Name
Description
Type
Required or Not
bucket
Destination bucket name for storing results, format is BucketName-AppId, if not specified, it will default save to the current bucket.
String
No
fileid
Storage path and name of the processed file. Rule description for naming.
For example, the file path and filename of the source object are: /p1/test1.jpg
An absolute path starts with /, for example, when the fileid value is /p2/test2.jpg, it means a file named test2.jpg is stored in the p2 folder.
A relative path does not start with /. For example, when the fileid value is p2/test2.jpg, it means a p2 folder is created in the p1 folder, and then a file named test2.jpg is stored in the p2 folder.
Note: Do not end with /, otherwise an empty filename will occur.
If you want the repaired image to overwrite the original image, set the fileid field to <ObjectKey>
String
Yes
rule
Processing parameters, such as: ci-process = AISuperResolution or ci-process = AISuperResolution&magnify = 2
String
Yes

Request body

The request body contains the original image to be super-resolved [Image Content].

Response

Response Headers

This API returns common response headers. For details, see the Common Response Headers document.

Response Body

The response body returns with a content-type of application/xml. The specific data content is as follows:
Node Name (Keyword)
Parent Node
Description
Type
UploadResult
None.
Request result.
Container
The content of UploadResult
Node Name (Keyword)
Parent Node
Description
Type
OriginalInfo
UploadResult
Image information
Container
ProcessResults
UploadResult
Request processing result
Container
The content of the OriginalInfo node
Node Name
Parent Node
Description
Type
Key
OriginalInfo
Original image filename
String
Location
OriginalInfo
Original image path
String
ETag
OriginalInfo
Original image ETag value
String
ProcessResults node content
Node Name (Keyword)
Parent Node
Description
Type
Object
ProcessResults
Processing result of each image
Container
Content of Object node
Node Name (Keyword)
Parent Node
Description
Type
Key
Object
Image file name after super-resolution
String
Location
Object
Image link after super-resolution
String
ETag
Object
ETag value of the super-resolved image
String
Size
Object
Image size after super-resolution
Int

Examples

Request

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": "ci-process=AISuperResolution&magnify=2"
  }]
}

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 645
Date: Tue, 23 Apr 2022 09:06:16 GMT
Status: 200 OK
Server: tencent-ci
x-cos-request-id: NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****

<UploadResult>
    <OriginalInfo>
        <Key>ObjectKey</Key>
        <Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/filename.jpg</Location>
        <ETag>"ed60e3598e6862d8c8443a06acfb2153"</ETag>
    </OriginalInfo>
    <ProcessResults>
        <Object>
            <Key>exampleobject</Key>
            <Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/exampleobject</Location>
            <Format/>
            <Size>354256</Size>
            <ETag>"521451f63c331becf533e466732c1091"</ETag>
        </Object>
    </ProcessResults>
</UploadResult>

Processing Method 3: Cloud Data Processing

Request

Request Syntax

POST  /<ObjectKey>?image_process HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Authorization: Auth String
Pic-Operations: <PicOperations>
Note:
Authorization: Auth String (For details, see Request Signature document).

Request header

This API only uses common request headers. For details, see the Common Request Headers document.
In addition to the common headers, the following headers need to be provided:
Header Name
Description
Type
Pic-Operations
Parameters for image operations
String
Pic-Operations is a json format string, with the following specific parameters:
Parameter Name
Description
Type
Required or Not
is_pic_info
Whether to return original image information, 0 means do not return original image information, 1 means return original image information, default is 0
Int
No
rules
Processing rules, one rule corresponds to one processing result (currently supports five rules), leave blank to skip image processing
Array
No
Each item in the rules (json array) has the following specific parameters:
Parameter Name
Description
Type
Required or Not
bucket
Destination bucket name for storing results, format is BucketName-AppId, if not specified, it will default save to the current bucket.
String
No
fileid
Storage path and name of the processed file. Rule description for naming.
For example, the source file path and filename are: /p1/test1.jpg
An absolute path starts with /. For example, when the fileid value is /p2/test2.jpg, it means a file named test2.jpg is stored in the p2 folder.
A relative path does not start with /. For example, when the fileid value is p2/test2.jpg, it means a p2 folder is created in the p1 folder, and then a file named test2.jpg is stored in the p2 folder.
Note: Do not end with /, otherwise an empty filename will occur.
If you want the repaired image to overwrite the original image, set the fileid field to <ObjectKey>
String
Yes
rule
Processing parameters, such as: ci-process = AISuperResolution or ci-process = AISuperResolution&magnify = 2
String
Yes

Request body

The request body contains the original image to be colorized [Image Content].

Response

Response Headers

This API returns common response headers. For details, see the Common Response Headers document.

Response Body

The response body returns with a content-type of application/xml. The specific data content is as follows:
Node Name (Keyword)
Parent Node
Description
Type
UploadResult
None.
Request result.
Container
The content of UploadResult
Node Name (Keyword)
Parent Node
Description
Type
OriginalInfo
UploadResult
Image information
Container
ProcessResults
UploadResult
Request processing result
Container
The content of the OriginalInfo node
Node Name
Parent Node
Description
Type
Key
OriginalInfo
Original image filename
String
Location
OriginalInfo
Original image path
String
ETag
OriginalInfo
Original image ETag value
String
ProcessResults node content
Node Name (Keyword)
Parent Node
Description
Type
Object
ProcessResults
Processing result of each image
Container
Content of Object node
Node Name (Keyword)
Parent Node
Description
Type
Key
Object
Image file name after super-resolution
String
Location
Object
Image link after super-resolution
String
ETag
Object
ETag value of the super-resolved image
String
Size
Object
image size
Int

Examples

Request

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: 
{
  "rules": [{
      "fileid": "exampleobject",
      "rule": "ci-process=AISuperResolution&magnify=2"
  }]
}
The processed image is stored in the bucket and named using the value of the field fileid as the object name.

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 645
Date: Tue, 23 Apr 2022 09:06:16 GMT
Status: 200 OK
Server: tencent-ci
x-cos-request-id: NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****

<UploadResult>
    <OriginalInfo>
        <Key>ObjectKey</Key>
        <Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/filename.jpg</Location>
        <ETag>"ed60e3598e6862d8c8443a06acfb2153"</ETag>
    </OriginalInfo>
    <ProcessResults>
        <Object>
            <Key>exampleobject</Key>
            <Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/exampleobject</Location>
            <Format/>
            <Size>354256</Size>
            <ETag>"521451f63c331becf533e466732c1091"</ETag>
        </Object>
    </ProcessResults>
</UploadResult>

Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback