# Local screenshot upload (/en/realtime-media/video/build/add-advanced-video-features/screenshot-upload/web)
> For AI agents: see the complete documentation index at [llms.txt](/llms.txt).
To meet the needs of video content supervision, Agora Video SDK enables you to take screenshots of the video stream in a channel and then upload these images to third-party cloud storage.
This page shows you how to enable screenshot uploads on your app and handle screenshot upload callbacks.
Local screenshot upload is a paid service. For billing details, refer to [Pricing](/en/realtime-media/video/reference/pricing).
## Understand the tech [#understand-the-tech-3]
When you enable screenshot upload, you set the interval between screenshots. After each interval, Video SDK takes a screenshot of the video stream sent by local users, and uploads the image to Agora SDRTN®. Agora SDRTN® uploads each screenshot to your third-party cloud storage and sends a callback notification to your server in the form of an `HTTPS` request.
**Screenshot upload**
## Prerequisites [#prerequisites-3]
Before implementing the Agora local screenshot upload feature, take the following steps:
1. **Activate local screenshot upload service**
Log in to [Agora Console](https://console.agora.io), select the project for which you want to activate the local screenshot upload service, and then click **Configure**. Scroll down to the features section to find **Video Screenshot Upload** and click **Config**.
2. **Configure third-party cloud storage**
In the **Video Screenshot Upload Configuration**, update the screenshot upload settings:
Currently, the Agora local screenshot upload service supports Amazon S3 and Alibaba Cloud OSS as the third-party cloud storage providers. If you want to use other provider, [contact](mailto\:support@agora.io) technical support.
Fill in the following information:
AWS
Alibaba Cloud
* **Screenshot Callback Address**: The server address to receive callback notifications of local screenshot upload results.
* **Storage**: Third-party cloud storage provider. Select AWS.
* **Region**: The data center region setting for third-party cloud storage. See [AWS Official Documentation](https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region) for details.
* **Access Key**: String type, the access key of the third-party cloud storage. Best practice is to provide a write-only access key.
* **Secret Key**: String type, the secret key of the third-party cloud storage.
* **Bucket Name**: String type, the bucket name of the third-party cloud storage. The bucket name must comply with the naming rules of the corresponding third-party cloud storage service.
* **Endpoint**: Specify the access domain (Endpoint) of the bucket. See [AWS Official Documentation](https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region) for details.
* **Filename Prefix**: (Optional) JSON Array, an array composed of multiple strings, indicating the storage location of screenshots in the third-party cloud storage. For example, if `fileNamePrefix` = `["directory1","directory2"]`, the prefix `directory1/directory2/` will be added to the screenshot filename, that is, `directory1/directory2/xxx.jpg`. The prefix length, including slashes, must not exceed 128 characters. The string should not contain symbols such as slashes, underscores, parentheses, and so on. The supported character set is as follows:
* 26 lowercase English letters a-z
* 26 uppercase English letters A-Z
* 10 digits 0-9
**Sample configuration**
* Snapshot Callback Address: `https://webhook.site/2e75da2d-xxxx-xxxx-xxx-a0ef44a5259d`
* Storage: AWS
* Region: `cn-north-1`
* Access Key: `12345678`
* Secret Key: `abcd123`
* Bucket Name: `test-artifacts`
* Endpoint: `s3.cn-north-1.amazonaws.com.cn`
* Filename Prefix: `test`
* **Screenshot Callback Address**: The server address to receive callback notifications of local screenshot upload results.
* **Storage**: Third-party cloud storage provider. Select Alibaba Cloud.
* **Access Key**: String type, the access key of the third-party cloud storage. Best practice is to provide a write-only access key.
* **Secret Key**: String type, the secret key of the third-party cloud storage.
* **Bucket Name**: String type, the bucket name of the third-party cloud storage. The bucket name must comply with the naming rules of the corresponding third-party cloud storage service.
* **Endpoint**: Specify the access domain (Endpoint) of the bucket. See [Alibaba Cloud Official Documentation](https://help.aliyun.com/zh/oss/user-guide/regions-and-endpoints?spm=a2c4g.11186623.0.0.7ac5667aLnjEtX) for details.
* **Filename Prefix**: (Optional) JSON Array, an array composed of multiple strings, indicating the storage location of screenshots in the third-party cloud storage. For example, if `fileNamePrefix` = `["directory1","directory2"]`, the prefix `directory1/directory2/` will be added to the screenshot filename, that is, `directory1/directory2/xxx.jpg`. The prefix length, including slashes, must not exceed 128 characters. The string should not contain symbols such as slashes, underscores, parentheses, and so on. The supported character set is as follows:
* 26 lowercase English letters a-z
* 26 uppercase English letters A-Z
* 10 digits 0-9
**Sample configuration**
* Snapshot Callback Address: `https://webhook.site/2e75da2d-xxxx-xxxx-xxx-a0ef44a5259d`
* Storage: Alibaba Cloud
* Region: `cn-north-1`
* Access Key: `12345678`
* Secret Key: `abcd123`
* Bucket Name: `test-artifacts`
* Endpoint: `oss-accelerate.aliyuncs.com`
* Filename Prefix: `test`
3. **Integrate Video SDK**
Integrate the Video SDK (including the local screenshot upload dynamic library) into your project, join a channel, and publish a video stream. See [SDK quickstart](/en/realtime-media/video/get-started-sdk) for details.
## Implement local screenshot upload [#implement-local-screenshot-upload-3]
You enable screenshot upload in your Video Calling client and handle the notification callback from Agora on your callback server.
### Enable screenshot upload [#enable-screenshot-upload-3]
Call the `enableContentInspect` method to enable the local screenshot upload feature. After successfully enabling the feature, the SDK will capture screenshots at the specified frequency and upload them to the Agora cloud server. To implement this logic, refer to the following code:
```javascript
const inspectConfig = {
// Set the interval for local screenshot to 2000 milliseconds (2 seconds), with a minimum value of 1000.
interval: 2000,
// (Optional) Set the address prefix for third-party cloud storage.
ossFilePrefix: 'https://your-cloud-storage.com/',
// (Optional) Add additional information.
extraInfo: 'This is some additional information for content inspection.',
// Set the function type to \"supervise\".
inspectType: ['supervise'],
};
client
.enableContentInspect(inspectConfig)
.then(() => {
console.log('Content inspection enabled successfully.');
})
.catch((error) => {
console.error('Failed to enable content inspection:', error);
});
```
### HTTP notification callback [#http-notification-callback-3]
After a screenshot is successfully uploaded to the Agora SDRTN®, Agora sends a message notification callback to your application server in the form of an `HTTPS` `POST` request. The data format is `JSON`, and the character encoding is `UTF-8`.
Upon receiving the message notification, your application server must respond with status code `200`. The expected response body format is `JSON`. In any of the following cases, the notification is considered to have failed:
* No response is received from your server within 5 seconds after sending the message notification.
* The `HTTP` status code of the response is not `200`, or the response body format is not `JSON`.
The Agora service immediately retries after the first notification failure, and sends the message three times in total.
## Reference [#reference-3]
This section contains content that completes the information on this page, or points you to documentation that explains other aspects to this product.
### Pricing [#pricing-3]
Agora charges for local screenshot upload based on two metrics:
* **Screenshot fee**
* **QPS overage fee** (queries per second)
### local screenshot upload dynamic library [#local-screenshot-upload-dynamic-library-3]
You can find details about the name of the local screenshot upload dynamic library and the increase in app size after integration in [App size optimization](app-size-optimization.mdx).
### HTTP status codes [#http-status-codes-3]
The HTTP status codes for the application server responses are as follows:
| Status Code | Description |
| :---------- | :---------------------------------------------------------------------------------------------------------------------------------- |
| `200` | Successful request. |
| `201` | Successful request and creation of a new resource. |
| `206` | No user streamed during the entire screenshot process, or some screenshot files were not uploaded to the third-party cloud storage. |
| `400` | Syntax error in the request (for example, parameter error), and the server cannot understand it. |
| `401` | Unauthorized (App ID or Customer Certificate mismatch). |
| `404` | The server cannot find the requested resource (webpage). |
| `500` | Internal server error, unable to complete the request. |
| `504` | Internal server error. The server acting as a gateway or proxy did not receive a timely response from the upstream server. |