The browser method in three steps
1) Open the Video Frame Extractor. 2) Drop in your video and choose how many frames (6–48) — evenly spaced across the whole runtime. 3) Download the timestamped JPGs or PNGs, one click for the batch. Nothing is installed, nothing is uploaded, and the tool keeps working offline once loaded.
How it works without ffmpeg
Browsers already contain a complete media stack — the same decoders that play YouTube also decode your local file. The tool loads the video into a media element, seeks to chosen timestamps, and draws each decoded frame onto a canvas, which becomes your image. You are using the browser's decoder directly instead of shelling out to a CLI binary.
What you give up vs ffmpeg
Three honest limits: caps (48 frames per run instead of thousands), formats (whatever your browser plays — which covers H.264/MP4, WebM and most phone footage, but not exotic codecs), and scripting (no pipelines or folder loops). For everyday jobs — reference stills, evidence frames, storyboards — the cap is rarely binding: run it twice with different spacing if you need more.
Locked-down machines and privacy
Because the tool is a web page that runs its computation on your device, it works where installs are blocked and it never exports your footage anywhere — the file is read from disk by your own browser instance. For CCTV exports, HR material or client files, that property is not a convenience; it is the requirement.