Extract All Video Frames

Turn a video into a sequence of images

Sometimes the most useful thing in a video is the individual frames inside it. You might need sprite sheets for animation, reference stills for a report, every slide from a recorded presentation, training data for a small experiment or simply a handful of candidate thumbnails to choose from. This tool samples a local video at a frame rate you choose and saves each sampled moment as its own PNG image. Instead of pausing a player and screenshotting repeatedly, you get a clean, evenly spaced set of frames in one pass.

Everything happens in the browser. The selected video is written into ffmpeg.wasm's in-memory file system, ffmpeg samples frames at the rate you set, and the generated PNG files are read back and downloaded one after another. Nothing is uploaded, there is no account and the temporary files are cleared from the engine when the run finishes. That keeps private recordings, client footage and unreleased material entirely on your own device.

Choosing a frame rate and size

The frames-per-second value controls how densely the video is sampled. A rate of 1 produces one image every second, which is plenty for storyboards and overviews. Higher rates capture fast motion in finer detail but create many more files, so a thirty-second clip at ten frames per second yields hundreds of images. Fractional rates such as 0.5 or 0.25 thin the output to one frame every few seconds. You can also set a target width to shrink each frame and keep the download manageable; the height is scaled automatically to preserve the aspect ratio. Start low, check the result, then increase the rate if you need more detail.

Browser and download notes

Extracting many frames uses memory and triggers a series of separate downloads, so your browser may ask permission to save multiple files. Allow it so the full set is captured, and pick a download folder where the numbered PNGs can land together. Very long or high-resolution videos combined with a high frame rate can be slow or hit memory limits because all of the work runs on your device, so favour shorter clips and modest rates for large jobs. The first extraction may pause while the WebAssembly engine downloads, but later runs in the same tab start without that wait.