FFmpeg is the software the entire video industry runs on. It is free, it has existed since 2000, and essentially every streaming service, editing suite and video website has it somewhere in the pipeline. If you need to do something with video, FFmpeg can do it.

Browser-based extraction is a much smaller idea: use the decoder your browser already ships with, capture what it produces to a canvas, save the result. It handles a narrower set of situations and handles them without installing anything.

Both are the right answer sometimes. This is an honest comparison of which is which.

The short version

	FFmpeg	Browser
Install required	Yes	No
Codec coverage	Essentially everything	What your browser supports
Batch across many files	Yes	One at a time
Scene-change detection	Yes	No
Exact frame numbers	Yes	Timestamps only
Visual preview while running	No	Yes
Learning curve	Real	None
Privacy	Local	Local

Where FFmpeg wins outright

Four capabilities have no browser equivalent, and if you need any of them the decision is made for you.

Codecs browsers cannot decode

ProRes, DNxHD, CineForm, uncompressed formats and various broadcast codecs will never open in a browser. FFmpeg handles all of them. If you work with footage straight off a cinema camera, this alone settles the question.

Scene-change detection

Instead of sampling at fixed intervals, FFmpeg can capture only where the picture actually changes by more than a threshold you set. For footage with long static stretches punctuated by cuts, this is dramatically more efficient than interval sampling - you get every distinct shot and nothing redundant.

Exact frame targeting

FFmpeg can address frame number 4,127 specifically. Browser extraction works in timestamps, which is the right model for variable frame rate footage but not for analysis work where frame indices matter.

Unattended batch processing

Point a shell loop at a folder of two hundred files and walk away. Nothing browser-based does this.

One frame every 5 seconds

ffmpeg -i input.mp4 -vf fps=1/5 frame_%04d.jpg

Capture only on scene changes above 30%

ffmpeg -i input.mp4 -vf "select='gt(scene,0.3)'" -vsync vfr scene_%03d.jpg

A single frame at 00:01:23

ffmpeg -ss 00:01:23 -i input.mp4 -frames:v 1 still.png

Every file in a folder

for f in *.mp4; do ffmpeg -i "$f" -vf fps=1 "${f%.mp4}_%03d.jpg"; done

Where the browser wins

The browser’s advantages are less dramatic on paper and matter more in practice than people expect.

There is nothing to install, which sounds trivial until you are on a work laptop with locked-down permissions, a borrowed machine, a Chromebook, or a phone. FFmpeg is not an option in any of those situations and a browser always is.

There is no syntax to remember. FFmpeg’s flags are powerful and genuinely hard to recall - most people who use it occasionally look up the command every single time. A form with a number field and a format dropdown requires nothing.

And there is a live preview. You see frames appearing as they are captured, which means you know within seconds whether your interval was sensible. With FFmpeg you find out when the job finishes and you open the output folder.

Try FrameRipper - free, no upload

Extract frames from any video directly in your browser. No sign-up, no file size limits.

Open FrameRipper

The privacy question, honestly

A claim worth correcting: browser-based is not inherently more private than FFmpeg. FFmpeg runs entirely on your own machine and sends nothing anywhere. On privacy grounds they are equivalent.

What is true is that browser-based extraction is more private than most other online tools. The majority of web converters upload your file to a server, process it there, and hand back a link - which means your footage sits on infrastructure you do not control, for a period you do not choose. Browser-based extraction avoids that while keeping the convenience.

So the real comparison is three-way. Server-based online tools are the convenient-but-exposed option. FFmpeg is the private-but-effortful one. Browser extraction is private and effortless, at the cost of a narrower feature set.

Speed, in practice

FFmpeg is faster per frame, particularly at high volumes and high resolutions. It decodes more efficiently and writes files without the overhead of a browser tab.

That advantage is often irrelevant. For a hundred frames from a five-minute video, both finish in seconds and the difference is swamped by the time it takes to type the FFmpeg command. The gap only becomes meaningful at thousands of frames or across many files - exactly the workloads where you should be using FFmpeg anyway.

Both approaches also beat any server-based tool by a wide margin on real-world time, because neither involves uploading a two-gigabyte file and waiting for it to come back.

Choosing

The decision reduces to a few questions.

Does your footage use a professional codec like ProRes? FFmpeg.
Do you need scene detection or exact frame numbers? FFmpeg.
Are you processing dozens of files, or doing this regularly on a schedule? FFmpeg.
Do you need it done in the next two minutes? Browser.
Are you on a machine where you cannot install software? Browser.
Do you want to see results as they happen? Browser.
Is this a one-off, on a normal MP4 or MOV? Browser.

Using both

They are not mutually exclusive and the combination is often the most sensible workflow.

A common pattern: use FFmpeg once to transcode awkward footage into browser-friendly H.264, then do all the actual frame selection in the browser where you can see what you are getting. You pay the command-line cost once, for the one thing FFmpeg is uniquely good at, and keep the fast visual loop for the part that benefits from being visual.

The other direction works too. Use the browser to sample a file quickly and figure out roughly what interval you need, then run the real job in FFmpeg once you know what you are asking for.