Extract frames from a video
JPEG stills from any length of video, without uploading it.
Choose a video
…or drop one anywhere in this box.
Your video never leaves this browser. Nothing is uploaded, whatever its size.
Settings
Choose a video to see the frame count.
Frames
Extracted frames appear here.
Take still images out of a video at whatever rate you choose — one a second to skim a long recording, or twenty-four to catch the exact moment something happens.
Your video is never uploaded. It is read from your disk by this page and every frame is produced here, on your device. That is the whole point of it: the tools that do this on a server have to receive your file first, which is why they cap what they accept — ezgif, the best of them, stops at 200 MB and keeps what you send for an hour afterwards. There is no cap here because there is no transfer, and nothing to delete afterwards because no copy was ever made.
Why do it in the browser
No upload, so no size limit. Your video is read from disk by this page. Nothing is transferred, so there is no upload wait and nothing that has to fit through one — a 4 GB screen recording is the same to this tool as a 4 MB clip. The tools that run on a server have to cap what they accept; ezgif, the best of them, stops at 200 MB.
Nothing is left on anyone’s server. A site that processes your video has to store it while it works, and then for some time afterwards — an hour is typical. That is a copy of your footage on a machine you do not control. Here there is no copy, because there was never a transfer.
It works on things you would not upload. Screen recordings with credentials on screen, footage of your family, unreleased work, anything under an agreement about where it may be stored. The question of whether the site is trustworthy does not arise when the file does not leave the device.
The trade-off, stated plainly. Server-side tools run ffmpeg, so they read every format ever made and can pull every frame with exact accuracy. This one is limited to what your browser can decode, and seeks to a timestamp rather than to a numbered frame. For pulling stills out of ordinary footage that difference does not matter; for frame-exact work on an unusual codec, it does.
How to use it
Choose the video. It is read on this device. Large files are fine — nothing is uploaded, so there is no wait before you can start.
Narrow the range if you only want part of it. Set a start and end time. This is what makes a high frame rate usable: twelve frames a second across ten seconds is a reasonable set of images, and across ten minutes it is not.
Pick a frame rate. One frame a second is right for reviewing a long recording. Higher rates are for catching a moment — a facial expression, a ball crossing a line, the frame a fault appears in. The number of images is shown before extraction starts.
Take them individually or as one ZIP. A single frame downloads on its own. More than one comes as a ZIP, because browsers block repeated downloads. The images are stored in the archive without further compression, since JPEG data does not compress again.
This tool uses the video support already built into your browser, which is what lets it work without uploading anything. MP4 and MOV files using H.264 — what phones, cameras and screen recorders produce by default — work, as do WebM files. AVI, WMV, FLV and older formats do not, and neither do some newer iPhone recordings saved as HEVC. Where a file cannot be read you are told immediately, and told why, rather than being left with a folder of blank images.
Read more about this
- How to extract frames from a video without uploading it →
Seeking lies, the first frame is often black, and codec support is a real limit rather than a bug.
Frequently asked questions
- Is my video uploaded anywhere?
- No. The video is read from your disk by this page and every frame is produced on your device. Nothing is sent to us or to anyone else, and no request leaves the browser while it works. You can disconnect from the network and the tool still works.
- Is there a size limit?
- No. Because there is no upload, file size is not a constraint the way it is for a site that has to receive your video first — those commonly cap at a few hundred megabytes. What limits this tool is the number of frames you ask for, not the size of the file they come from.
- Which video formats work?
- This tool uses the video support already built into your browser, which is what lets it work without uploading anything. MP4 and MOV files using H.264 — what phones, cameras and screen recorders produce by default — work, as do WebM files. AVI, WMV, FLV and older formats do not, and neither do some newer iPhone recordings saved as HEVC. Where a file cannot be read you are told immediately, and told why, rather than being left with a folder of blank images.
- Why can I not extract every single frame?
- Because a five-minute clip at thirty frames a second is nine thousand images, which is a folder nobody will look through and enough work to make the tab unresponsive. Choosing a frame rate and a time range gets you the moment you actually wanted. The tool caps a single run at 600 frames and tells you the count before it starts.
- Will a video shot on a phone come out sideways?
- No. Phone videos are often recorded in one orientation and tagged to be displayed in another, and the frames here are drawn the way the video is displayed, so a portrait recording produces portrait images.
- Are the frames exactly the ones in the video?
- They are the frames the browser shows at the timestamps requested, which for ordinary footage is the frame you would see if you paused there. It is not the same as numbering every frame in the file and pulling frame 1,247 — that needs a full decoder, which is what server-side tools run and what would mean downloading tens of megabytes of code to this page.
Need those frames on another device?
Mubifiles sends files and text between two devices with a six-digit code. No account, nothing to install.
Start a session →