MP4 is the most common video format in the world, which makes converting one into a set of still images one of the most common things people want to do with video. The good news is that it is also one of the easiest, provided you understand one thing about what an MP4 actually is.
This guide covers the conversion itself, the format choice at the other end, and why a small minority of MP4 files refuse to cooperate.
The conversion, start to finish
The whole process runs inside your browser. Your file is never uploaded, so there is no transfer wait and no size ceiling beyond what your own machine can handle.
- 1Select your MP4 file. It is read from disk directly by the browser and stays on your device.
- 2Set how many images you want. They are distributed evenly across the full duration.
- 3Choose JPEG, PNG or WebP. If you choose JPEG or WebP you can also set a quality level.
- 4Click Extract Frames and watch the gallery populate.
- 5Download the ZIP. Files are numbered in sequence so they sort correctly anywhere.
Try FrameRipper - free, no upload
Extract frames from any video directly in your browser. No sign-up, no file size limits.
Open FrameRipperMP4 is a container, not a codec
This single distinction explains almost every MP4 problem anyone ever has.
MP4 is a box. The box holds a video stream, usually an audio stream, and some metadata. What matters for decoding is the compression format of the video stream inside the box, and MP4 can hold several different ones.
The overwhelming majority of MP4 files in circulation use H.264, which every browser on every platform decodes without complaint. If your file came from a phone in compatibility mode, a screen recorder, a download from most websites, or an export from any consumer editing app, it is almost certainly H.264 and it will simply work.
The exceptions are worth naming. HEVC, also called H.265, appears in footage from newer iPhones, most 4K action cameras and many drones. It compresses to roughly half the size for equivalent quality, which is why manufacturers adopted it, but browser support is inconsistent and often depends on hardware decoding being available. AV1 is newer, compresses even better, and has good support in recent Chrome and Firefox while lagging elsewhere.
H.264 has profiles too
A subtler failure case: a file can be genuinely H.264 and still not decode.
H.264 defines several profiles, which are essentially feature sets. Consumer footage uses Baseline, Main or High profile with 8-bit colour and 4:2:0 chroma subsampling, and all of that works everywhere. Professional cameras frequently record High 10 profile with 10-bit colour, or 4:2:2 chroma for more grading latitude.
Those professional profiles are legitimately H.264, and a browser will often refuse them anyway. If a file from a cinema camera fails despite being labelled H.264, this is usually why. The fix is the same as for any other unsupported file: transcode to 8-bit High profile.
Choosing your output format
The decision is genuinely simple once you know what the images are for.
| Use case | Format | Reason |
|---|---|---|
| Sharing, email, documents | JPEG | Universal support, small files |
| Editing or compositing | PNG | No generational loss when re-saving |
| Machine learning datasets | PNG | No compression artifacts in the signal |
| Screen recordings and slides | PNG | Often smaller AND sharper than JPEG |
| Images for a website | WebP | Smaller than JPEG at matched quality |
| Not sure | JPEG | Correct answer most of the time |
What the JPEG quality setting does
JPEG quality runs from 1 to 100 and controls how aggressively detail is discarded. The scale is not linear, and the file-size relationship gets very steep near the top.
The default of 92 sits at a deliberate sweet spot. It is high enough that the difference from lossless is invisible on ordinary footage, while producing files a fraction of the size of a maximum-quality export. Pushing to 100 can roughly double file size for a change nobody will notice. Dropping below about 75 starts producing visible blocking in gradients - skies, out-of-focus backgrounds, anything with smooth tonal transitions.
| Quality | Typical 1080p frame | What you would notice |
|---|---|---|
| 100 | ~800 KB | Nothing over 92 |
| 92 (default) | ~320 KB | Nothing at normal viewing size |
| 80 | ~180 KB | Slight softening in fine texture |
| 60 | ~95 KB | Blocking in skies and gradients |
These figures are for typical live-action content. A frame with lots of fine detail compresses far worse than a slide with a plain background, so treat them as a rough guide rather than a promise.
Fixing a file that will not load
When an MP4 refuses to open, work through this in order.
- Try another browser. Chrome and Edge have the broadest general coverage; Safari is the only reliable choice for HEVC.
- Identify the codec: QuickTime Movie Inspector on macOS, the Details tab in file Properties on Windows, or Codec Information in VLC anywhere.
- If it is HEVC, AV1, or a 10-bit or 4:2:2 profile, transcode to 8-bit H.264 with HandBrake using the Fast 1080p30 preset.
- If the file plays nowhere at all, it is likely damaged rather than unsupported. Try re-downloading or re-exporting from the source.
Try FrameRipper - free, no upload
Extract frames from any video directly in your browser. No sign-up, no file size limits.
Open FrameRipperHow many images should you extract?
Work backwards from the interval you want rather than guessing a count. Duration in seconds divided by your target gap gives the number.
For most purposes, capturing more than you need is the right call. Extraction runs fast, storage is cheap, and deleting surplus frames takes moments. Discovering you sampled too sparsely means starting over.
The one place to be careful is very dense sampling on long files. A single extraction is capped at 10,000 frames because every frame stays in memory until the ZIP is built, and high-resolution sources can hit memory pressure before reaching that number. A two-hour video at one frame per second needs 7,200 and is fine; the same video at four frames per second is not.