Video Frame Capture Tool
Batch capture stills from video at native resolution - faster and cleaner than pausing and screenshotting.
How to use
- 1Upload your video.
- 2Set how many frames to capture.
- 3Choose format and click Extract Frames.
- 4Preview and download as ZIP.
Batch capture versus doing it by hand
The manual method is pause, screenshot, crop, save, name, repeat. Realistically that is fifteen to twenty seconds per image once you include finding the right moment and cleaning up the file. It also degrades as you go, because attention drifts and cropping gets sloppier.
Batch capture is one setup step and then it runs. The time difference is not marginal - it changes what is worth attempting at all. Pulling four hundred reference frames from an hour of footage is a routine operation in batch and an entire afternoon by hand.
| Frames needed | Manual (approx) | Batch capture |
|---|---|---|
| 10 | 3 minutes | Under 30 seconds |
| 50 | 15 minutes | Under a minute |
| 200 | 1 hour | 1-2 minutes |
| 1,000 | Impractical | 5-10 minutes |
What you give up compared to FFmpeg
Being straightforward about the tradeoff: a browser tool does not replace command-line extraction in every case. FFmpeg decodes codecs no browser supports, including ProRes and DNxHD. It can filter by scene change to capture only where the picture actually shifts. It can extract by exact frame number, apply colour transforms, and run unattended across a hundred files.
What it costs is installation, a command syntax you have to look up every time, and no visual feedback until the job finishes. For most people who need a few dozen stills from footage they can already play, that overhead is not worth paying. If you are processing footage in bulk on a schedule, or working with professional codecs, FFmpeg is the right tool and this is not.
Native resolution capture
Frames are captured from the decoded video buffer, so they come out at source resolution regardless of window size, monitor, or zoom level. A 4K video produces 3840x2160 images even in a small browser window on a 1080p display.
The preview gallery downscales thumbnails to 320 pixels on the longest edge so the page stays responsive when you have extracted a thousand frames. That downscaling applies only to what you see in the browser - the files inside the ZIP are always full size.
FAQ
Is this better than pausing and screenshotting?
For more than a handful of images, substantially. Captured frames are at native resolution with no player controls, and a batch of two hundred takes a minute or two instead of an hour.
What resolution are captured frames?
The video’s native resolution, independent of window size or display. Gallery thumbnails are downscaled to 320px for page performance, but the ZIP contains full-size images.
Does it handle 4K video?
Yes. Extraction is slower and uses more memory at 4K, so for very large batches from high-resolution sources a desktop browser is a better bet than a phone.
When should I use FFmpeg instead?
When you need professional codecs like ProRes, scene-change detection, exact frame-number targeting, or unattended batch processing across many files.