FFmpeg in a browser tab
The workhorse program behind most of the video conversion on the internet has been rebuilt to run inside a web page, arriving as a 31-megabyte download the first time a tab needs it.
Open the MP4 tab on Simon Willison's animated-drawing viewer and the page quietly starts pulling down 31 megabytes of software: a complete copy of FFmpeg, the command-line tool that sits under most of the video conversion on the internet, recompiled to run inside the browser. The page then steps through the animation, freezing it into frames, and encodes those frames into a video file. None of it required an install.
A privacy policy you never have to read, because there is no server to send the file to.
The encoder is ffmpeg.wasm, an MIT-licensed port that has been on GitHub since 2019 and has not shipped a release since January 2025. It is not news, and it is worth knowing anyway, because it is the load-bearing piece under a habit that has crept up quietly. WebAssembly, the portable machine code every modern browser now runs, made it practical to ship a decades-old C program as a web page, and a one-afternoon personal tool can now assume a full video encoder the way it assumes a font.
The bill comes in three parts. The conversion runs roughly five to twenty times slower than the same job on your own machine. A browser tab can address only two gigabytes of memory, which rules out anything feature-length. And the fast multi-core mode requires the site to serve a particular pair of security headers, so it is not quite free for the publisher either. For clip-length work those are cheap prices, and what they buy is a different shape for heavy software: fetched when the tab needs it, gone when you close it, installed nowhere.
Willison's SVG-to-video page is the two-click demo; the repo's Getting Started docs take you from one npm package to a file transcoded in your own tab.
Open the repo at github.com →The lenses
The facts
Concepts
How this connects
Tap a node to open it