Video Frame Extractor
Upload any video. Extract frames. Download as ZIP. Nothing leaves your device.
What each setting does
- Frames. How many images to take, spread evenly across the whole video. The line above the controls shows the gap that works out to, for example "10 frames every 6.0s". Each frame comes from the middle of its slice of the video, so the first one is never the black frame at 0:00.
- Format. JPEG for everyday use. PNG when you will edit the images, or when the video is slides, a screen recording or animation. WebP for images going straight onto a website.
- Quality. Applies to JPEG and WebP. The default of 92 looks the same as lossless on normal footage at a fraction of the size. PNG ignores it.
- Abort. Stops early and still gives you a ZIP of every frame captured up to that point.
- Download ZIP. Files are named frame_0001, frame_0002 and so on, in order, at the video’s full resolution. The previews on this page are shrunk to keep it fast; the files in the ZIP are not.
- On iPhone. Play the video once before extracting. Safari does not reliably hand over frames until playback has started. Why that is.
Free, and the limits that are real
Most online converters upload your video and process it on a server. Servers cost money, so that cost comes back as a watermark, a file size cap, a daily limit or a paid tier. FrameRipper does the work inside your browser, and the only thing the server does is send you this page. That is why there is no account, no watermark and no quota.
The limits that remain come from your device, not from a pricing plan:
- 10,000 frames per run. Every frame stays in memory until the ZIP is built, and past that point browser tabs start to crash.
- Memory on big sources. Thousands of 4K frames can run out of memory before reaching 10,000, especially on a phone. Split long jobs into a few runs.
- Codecs. Whether a file opens depends on what your browser can decode, shown below.
Which videos your browser can open
A file extension only names the container. What decides whether a video opens is the codec inside it, and each browser supports a different set:
| Browser | H.264 | VP8 / VP9 | HEVC | AV1 |
|---|---|---|---|---|
| Chrome / Edge | Yes | Yes | Hardware dependent | Yes |
| Firefox | Yes | Yes | No | Yes |
| Safari (Mac) | Yes | Yes (14+) | Yes | Partial (17+) |
| Safari (iPhone, iPad) | Yes | Yes | Yes | Partial |
| Chrome (Android) | Yes | Yes | Usually | Yes |
If a file will not load, try a different browser first (Safari for iPhone footage), then re-encode the video to H.264. Step-by-step fixes for files that will not load.
Compared with pausing and screenshotting
Pausing, taking a screenshot, cropping and saving takes 15 to 20 seconds per image. The screenshot is also limited to your screen's resolution and picks up the player controls. Extraction reads each frame from the video itself, at full resolution, with nothing on top.
| Frames needed | Pause and screenshot | This tool |
|---|---|---|
| 10 | About 3 minutes | Under 30 seconds |
| 50 | About 15 minutes | Under a minute |
| 200 | About an hour | 1-2 minutes |
| 1,000 | Not realistic | 5-10 minutes |
It keeps working offline
Once this page has loaded, extraction itself makes no network requests. Decoding the video and encoding the images are both built into your browser. Load the page, turn off Wi-Fi, and it still works. How to check this yourself.
When you need more than a browser can do, such as ProRes files, scene-change detection or batch jobs across a folder, FFmpeg is the better tool. FFmpeg vs browser extraction.