Skip to main content

We are building a plugin that allows users to render figma prototypes as videos.


To support that we wanted to use WebCodecs API (Video processing with WebCodecs - Chrome Developers) which is already implemented in chrome.


It works in most modern browsers, but to our surprise trying to access window.VideoEncoder results in undefined exception.


It is however possible to access it if you specify a null-origin frame for your iFrame and serve it from our own servers.


We are wondering why that is? Is there a security concern? Is it just set to undefined because it hasn’t been whitelisted as an approved browser API yet?


It is a really powerful API that opens a lot of doors to creating really interesting things with Figma.

Be the first to reply!

Reply