MOV is Apple’s QuickTime container, and it is the format your iPhone records in, the format QuickTime exports, and the format a lot of professional cameras use. Converting one to JPG stills is straightforward roughly ninety percent of the time and mildly frustrating the rest, and the difference comes down to what is inside the file.
This covers the conversion, the specific reason MOV files fail more often than MP4s, and what to do about it.
The conversion
- 1Select your MOV file. Nothing uploads - the browser reads it from disk directly.
- 2Set how many JPG images you want across the duration.
- 3Choose JPEG and adjust the quality slider if you need to. The default of 92 is a sensible balance.
- 4Extract, then download everything as a ZIP.
Try FrameRipper - free, no upload
Extract frames from any video directly in your browser. No sign-up, no file size limits.
Open FrameRipperMOV holds several different codecs
The container tells you almost nothing about compatibility. A .mov file might contain any of these, and they behave very differently.
| Codec | Where it comes from | Browser support |
|---|---|---|
| H.264 | Most exports, older iPhones, Most Compatible mode | Everywhere |
| HEVC / H.265 | iPhone 7+ in High Efficiency mode | Safari yes, Chrome varies, Firefox no |
| ProRes | Professional cameras, Final Cut exports | Nowhere |
| Motion JPEG | Older cameras, some capture devices | Inconsistent |
| Animation / RLE | Legacy motion graphics workflows | Nowhere |
The HEVC issue in one paragraph
Every iPhone since the 7 defaults to recording HEVC, under Settings then Camera then Formats then High Efficiency. HEVC produces files roughly half the size of H.264 at the same quality, which is a real benefit when you are shooting 4K on a phone. The problem is licensing rather than technology: HEVC carries patent obligations that have kept browser support fragmented for years.
So an iPhone MOV that plays perfectly on the phone, and opens fine in Safari on a Mac, may simply refuse to load in Chrome on a Windows machine. Nothing is wrong with the file.
Three ways around it
Use Safari
Fastest fix if you have a Mac or an iPhone to hand. Safari decodes HEVC natively and reliably. This also applies on iOS, where every browser uses Apple’s engine underneath, so Chrome on an iPhone works just as well.
Let iOS convert on the way out
Under Settings then Photos, scroll to Transfer to Mac or PC and choose Automatic rather than Keep Originals. Videos then transcode to H.264 automatically when you transfer them off the phone. Most people do not know this setting exists and it removes the problem permanently.
Transcode with HandBrake
Free, open source, works on Windows, macOS and Linux. Load the MOV, choose the Fast 1080p30 preset, export. The output is H.264 in an MP4 container and opens anywhere. For extracting stills the quality loss at that preset is not something you will see.
ProRes and professional codecs
If your MOV came off a cinema camera or out of Final Cut, it may be ProRes. No browser decodes ProRes, and none is likely to - it is an editing codec, designed to be fast to scrub and forgiving to grade, at the cost of very large files. Nobody streams it, so no browser has reason to support it.
A ProRes file is easy to spot by size: a minute of ProRes 422 at 1080p runs to roughly 1.5 GB, where the H.264 equivalent is around 100 MB. If your one-minute clip is enormous, that is why.
Transcode to H.264 first. One important detail if the footage is log or 10-bit: apply your colour transform during the transcode. Log footage is deliberately flat and desaturated so it holds grading latitude, and extracted frames will look washed out unless you convert to a normal colour space on the way through. Fixing it afterwards on each individual JPEG is far more work than doing it once.
Why JPG for MOV footage
JPG is the right default here for the same reasons it usually is. It is universally supported, files are small enough to email without thinking, and at quality 92 the difference from lossless is invisible on live-action footage.
The cases where it is wrong are narrow. If you will edit the stills repeatedly, use PNG - every JPEG save re-compresses, and the degradation accumulates. If the MOV is a screen recording rather than camera footage, PNG will likely be both sharper and smaller. And if the stills are training data, PNG keeps compression artifacts out of the signal.
One thing JPG will not do is transparency, but that is not a limitation in practice: neither H.264 nor HEVC can store an alpha channel, so MOV frames are always fully opaque anyway.
Try FrameRipper - free, no upload
Extract frames from any video directly in your browser. No sign-up, no file size limits.
Open FrameRipperGetting the best stills out
A few things specific to MOV footage are worth knowing.
Resolution is often higher than expected. Recent iPhones default to 4K, so an extracted frame is around 8 megapixels - genuinely printable, and far better than screenshotting the video during playback on a laptop.
Rolling shutter affects phone and mirrorless footage. Sensors read out line by line rather than all at once, so fast horizontal movement skews vertical lines and quick pans introduce a subtle wobble. Frames caught during rapid motion will show it and nothing in post fixes it. Moving the camera slowly helps more than any setting.
Slow-motion is an underused trick. It is captured at 120 or 240 fps with a correspondingly short shutter, so individual frames are much sharper than normal-speed footage of the same action. Shooting in slo-mo specifically to pull a crisp still is a genuinely good technique.