How this tool works
The video is played by your browser, each wanted frame is drawn onto a canvas, and the results are packed into a ZIP. Nothing is uploaded — the file is decoded on your own device, which is the main reason to use this rather than a service that wants the upload before it will do anything. You choose how often to take a frame, over what range, in which format and at what size.
Before extraction starts, the number of frames, the estimated size and the estimated time are calculated and shown. That is deliberate: both time and memory scale with the frame count rather than the length of the video, so a twenty-minute clip is comfortable at one frame per second and impossible at every frame. Being told before you commit is more useful than a tab that dies four minutes in.
What limits this and why
- Fifteen hundred frames is the ceiling: the ZIP is assembled in memory, and that is roughly where a mid-range phone runs out. Twenty minutes at every frame would be around thirty-six thousand images and several gigabytes — a job for ffmpeg on a desktop, and the tool says so rather than letting you find out the hard way.
- Only what your browser can play: MP4 and WebM everywhere, MOV usually. MKV, AVI and ProRes will not open at all. That is a limit of browser video support rather than a missing feature, and no setting works around it.
- Frame-exactness varies between browsers: Chrome, Edge and Safari can capture frame by frame precisely. Firefox has no equivalent, so frames there are taken by seeking to a timestamp, and one may occasionally repeat or be skipped.
- Keep the tab in front: browsers throttle background tabs heavily. Switching away mid-run does not lose the frames already captured, but extraction slows to a crawl until you come back.