• Public
  • Public/Protected
  • All

Namespace VideoProcessor


Amazon Chime SDK for JavaScript contains easy-to-use APIs for adding frame-by-frame processing to an outgoing video stream.

Amazon Chime SDK for JavaScript defines a video processing stage as an implementation of the VideoFrameProcessor interface, which takes an array of VideoFrameBuffers, applies builder-defined processing, and outputs an array of VideoFrameBuffers. The outputs of each processor can be linked to the inputs of the next processor, with the last processor in the chain required to implement asCanvasImageSource to return CanvasImageSource so that the resulting frames can be rendered onto a HTMLCanvasElement and transformed into a MediaStream.

To integrate video processing into meeting session, VideoTransformDevice should be used, which internally uses a VideoFrameProcessorPipeline to complete the aforementioned linking of stages and final canvas rendering.

A typical workflow would be:

  1. Create an array of custom VideoFrameProcessors.
  2. Create a VideoTransformDevice from a Device and the array of VideoFrameProcessors.
  3. Call meetingSession.audioVideo.chooseVideoInputDevice with the VideoTransformDevice.

Browser compatibility

The APIs for video processing in Amazon Chime SDK for JavaScript work in Firefox, Chrome, Chromium-based browsers (including Electron) on desktop, and Android operating systems. A full compatibility table is below. Currently, the APIs for video processing do not support Safari/Chrome/Firefox on iOS devices due to Webkit Bug 181663. WebRTC Unified Plan is also required. Unified Plan is by default enabled in MeetingSessionConfiguration.enableUnifiedPlanForChromiumBasedBrowsers. If Unified Plan is disabled in the meeting, the call meetingSession.audioVideo.chooseVideoInputDevice with the VideoTransformDevice will throw an error.

Browser Minimum supported version
Firefox 76
Chromium-based browsers and environments, including Edge and Electron 78
Android Chrome 78
Safari on MacOS 13.0
iOS Safari Not supported
iOS Chrome Not supported
iOS Firefox Not supported

Video Processing APIs


VideoTransformDevice allows VideoFrameProcessors to be applied to to a Device and provide a new object which can be passed into meetingSession.audioVideo.chooseVideoInputDevice.

DefaultVideoTransformDevice is the provided implementation of VideoTransformDevice. It requires four parameters: (1) Logger (2) Device (3) Array<VideoFrameProcessor>. The DefaultVideoTransformDevice uses VideoFrameProcessorPipeline under the hood and hides its complexity.

Construction and Starting Video Processing

The construction of the DefaultVideoTransformDevice will not start the camera or start processing. The method meetingSession.audioVideo.chooseVideoInputDevice is needed to be called. The device controller will use the inner Device to acquire the source MediaStream and start the processing pipeline at the same frame rate. "Inner device" in this context refers to the original video stream coming from the selected camera. The parameters to chooseVideoInputQuality are used as constraints on the source MediaStream. After the video input is chosen, meetingSession.audioVideo.startLocalVideoTile can be called to start streaming video.

Switching the Inner Device on VideoTransformDevice

To switch the inner Device on DefaultVideoTransformDevice, call DefaultVideoTransformDevice.chooseNewInnerDevice with a new Device. DefaultVideoTransformDevice.chooseNewInnerDevice returns a new DefaultVideoTransformDevice but preserves the state of VideoFrameProcessors. Then call meetingSession.audioVideo.chooseVideoInputDevice with the new transform device.

Stopping VideoTransformDevice

To stop video processing for the chosen DefaultVideoTransformDevice, call meetingSession.audioVideo.chooseVideoInputDevice with a different DefaultVideoTransformDevice or null to stop using previous DefaultVideoTransformDevice. The method meetingSession.audioVideo.stopLocalVideoTile can also be used to stop the streaming.

After stopping the video processing, the inner Device will be released by device controller unless the inner Device is a MediaStream provided by users where it is their responsibility of users to handle the lifecycle.

After DefaultVideoTransformDevice is no longer used by device controller, call DefaultVideoTransformDevice.stop to release the VideoProcessors and underlying pipeline. After stop is called, users must discard the DefaultVideoTransformDevice.DefaultVideoTransformDevice.stop is necessary to release the internal resources.

Receiving lifecycle notifications with an observer

To receive notifications of lifecycle events, DefaultVideoTransformDeviceObserver can be added to the DefaultVideoTransformDevice. The full list of the callbacks:

  1. processingDidStart

processingDidStart will be called when video processing starts.

  1. processingDidFailToStart

processingDidFailToStart will be called when video processing could not start due to runtime errors. In this case, developers are expected to call chooseVideoInputDevice again with a valid VideoInputDevice to continue video sending.

  1. processingDidStop

processingDidStop will be called when video processing is stopped expectedly.

  1. processingLatencyTooHigh(latencyMs: number)

processingLatencyTooHigh will be called when the execution of processors slows the frame rate down by at least half.


VideoFrameBuffer is an abstract interface that can be implemented to represent images or video sources. It is required to implement asCanvasImageSource to return CanvasImageSource; optionally, developers can implement asCanvasElement or asTransferable to facilitate processing algorithm to work with HTMLCanvasElements or Workers respectively.


VideoFrameProcessor represents a processing stage. Internally, processors are executed in a completely serial manner. Each pass will finish before the next pass begins. The input VideoFrameBuffers are the video sources. Changing the property of buffers such as resizing will likely modify properties of the video sources and should be performed with care.

Building a simple processor

The following example shows how to build a basic processor to resize the video frames. We first define an implementation of VideoFrameProcessor:

class VideoResizeProcessor implements VideoFrameProcessor {
  constructor(private displayAspectRatio: number) {}

  async process(buffers: VideoFrameBuffer[]): VideoFrameBuffer[];
  async destroy(): Promise<void>;

To keep the properties of the original video, the processor has to copy the frame onto its own staging buffer in process:

class VideoResizeProcessor implements VideoFrameProcessor {
  private targetCanvas: HTMLCanvasElement = document.createElement('canvas') as HTMLCanvasElement;
  private targetCanvasCtx: CanvasRenderingContext2D = this.targetCanvas.getContext('2d') as CanvasRenderingContext2D;
  private canvasVideoFrameBuffer = new CanvasVideoFrameBuffer(this.targetCanvas);

  private renderWidth: number = 0;
  private renderHeight: number = 0;
  private sourceWidth: number = 0;
  private sourceHeight: number = 0;

  async process(buffers: VideoFrameBuffer[]): Promise<VideoFrameBuffer[]>;

During processing, the incoming video is painted onto the internal canvas like in the following abbreviated:

async process(buffers: VideoFrameBuffer[]): Promise<VideoFrameBuffer[]> {
  const canvas = buffers[0].asCanvasElement();
  const frameWidth = canvas.width;
  const frameHeight = canvas.height;

  // error handling to skip resizing
  if (frameWidth === 0 || frameHeight === 0) {
    return buffers;

  // re-calculate the cropped width and height

  // copy the frame to the intermediate canvas
  this.targetCanvasCtx.drawImage(canvas, this.dx, 0, this.renderWidth, this.renderHeight,
    0, 0, this.renderWidth, this.renderHeight);

  // replace the video frame with the resized one for subsequent processor
  buffers[0] = this.canvasVideoFrameBuffer;
  return buffers;

Video Processing Usage

Custom processor usage during meeting

import {
} from 'amazon-chime-sdk-js';

const stages = [new VideoResizeProcessor(4/3)]; // constructs  processor

const transformDevice = new DefaultVideoTransformDevice(
  'foobar', // device id string

await meetingSession.audioVideo.chooseVideoInputDevice(transformDevice);

Custom processor usage during meeting preview

import {
} from 'amazon-chime-sdk-js';

const processor = new VideoResizeProcessor(4/3);
const videoElement = document.getElementById('video-preview') as HTMLVideoElement;
const transformDevice = new DefaultVideoTransformDevice(
  'foobar', // device id string

await meetingSession.audioVideo.chooseVideoInputDevice(transformDevice);

Give feedback on this guide

Generated using TypeDoc