MOV to BMP Converter

How to Convert MOV to BMP Online

1. Upload Your MOV Files: Drag and drop or click "Add Files" to select one or more QuickTime .mov clips. iPhone recordings (H.264 or HEVC), screen captures, and ProRes masters are all accepted, and batch processing runs files back-to-back.
2. Pick Frame Selection: Choose Specific Frame to grab a single still — enter a precise time in seconds (e.g., 2.100 for 2 seconds, 100 ms) — or Multiple Screenshots to extract a series at a fixed interval ranging from every 0.1s up to every 10s per frame.
3. Choose a Quality Preset and Resolution (Optional): Pick a Quality Preset (Highest, Very High Recommended, High, Medium, Low, Very Low, or Lowest). Under Resolution, keep original, scale by percentage, pick a Preset Resolution from 4320p down to 144p, or type exact Width and Height with "Keep aspect ratio" enabled.
4. Convert and Download: Click Convert. Frames are processed in your browser session, then delivered as uncompressed .bmp files — no sign-up, no watermark, no upload to a third-party server.

Why Convert MOV to BMP?

MOV is the QuickTime container Apple introduced on December 2, 1991, and it remains the default capture format for iPhones, Macs, and ProRes editorial workflows. BMP (Windows Bitmap) is Microsoft's uncompressed raster format dating to Windows 2.0 — it stores raw pixel data with no lossy compression, which is exactly what you want when a downstream tool can't be trusted to handle JPEG artifacts or PNG decompression. Pulling stills out of a MOV as BMP is the cleanest path between Apple-side capture and Windows-side legacy software.

• Frame-accurate forensic and scientific review — Sports analysts, accident reconstruction, and microscopy review all need bit-exact frames where pixel-level differences carry evidentiary or measurement weight; BMP avoids the chroma subsampling and 8x8 DCT artifacts that JPEG introduces.
• Legacy Windows / WinForms / GDI integration — BMP is a native GDI bitmap, the fastest path into a System.Drawing.Bitmap or a Win32 LoadImage() call, with no decoder dependency. Older industrial vision software, kiosk applications, and in-house tools written before PNG was ubiquitous frequently accept BMP only.
• Embedded systems and microcontrollers — Resource-constrained boards (e.g., low-power MCUs driving small TFT displays) often parse uncompressed bitmaps directly from a framebuffer because they lack the flash space or cycles for a PNG/JPEG decoder.
• Print and prepress proofs — When pulling a hero still from iPhone footage for a print piece, BMP hands a pixel-exact 24-bit RGB image to InDesign or Photoshop with zero generation loss before color-managed conversion to CMYK.
• Contact sheets and timeline overviews — Multiple Screenshots at a 1s or 2s interval gives editors a quick visual index of an entire interview or B-roll reel without the lossy pass JPEG would impose on each thumbnail.
• Machine-vision and ML training data — When labeling pipelines compare pixels across frames (optical flow, change detection, OCR ground truth), starting from BMP eliminates compression noise as a confounding variable.

MOV vs BMP — Container vs Still Format

BMP vs JPG vs PNG for Frame Extraction

Frequently Asked Questions

How many BMP files will I get from one MOV?

In Specific Frame mode you get exactly one BMP — the frame at the timestamp you entered. In Multiple Screenshots mode the count is floor(duration / interval). A 60-second MOV at "every 1 second per frame" yields 60 BMPs; the same clip at "every 0.1s" yields about 600. Keep an eye on size — see the next answer for why batch BMPs add up fast.

Why are the BMP files so much larger than the source MOV?

A 1920x1080 BMP at 24 bits per pixel stores 1920 x 1080 x 3 bytes plus a small header — roughly 6.2 MB per frame. The MOV is small because H.264 / HEVC discards perceptually redundant data and uses inter-frame prediction; BMP stores every pixel independently with zero compression. If file size matters more than pixel-exact fidelity, extract as JPG via MOV to JPG or as PNG via MOV to PNG.

Can I capture a frame at sub-second precision?

Yes. The Time field accepts decimal seconds, so 12.75 lands at 12 seconds, 750 ms. The actual frame returned is the nearest decoded frame to that timestamp; on a 30 fps source the snap-to grid is roughly 33 ms, on 60 fps about 16 ms. For a frame-by-frame walk, switch to Multiple Screenshots and use a small interval like 0.05s or 0.1s.

Does this work with iPhone HEVC (H.265) MOV files?

Yes. iPhone 8 and later default to HEVC in the "High Efficiency" camera setting introduced in iOS 11 (fall 2017); iPhone 7 supports HEVC capture but ships set to "Most Compatible" (H.264). The decoder handles both, plus ProRes MOVs from iPhone 13 Pro and later when ProRes recording is enabled (requires iOS 15.1+).

Will rotation metadata be respected?

Yes. iPhone clips are stored in their native sensor orientation with a rotation matrix in the MOV header (so portrait videos play upright in QuickTime even though the underlying frame is landscape). The extractor reads that rotation and emits the BMP in the orientation you actually see during playback, not the raw sensor orientation.

What bit depth and color format are the BMPs?

24-bit RGB (BI_RGB, no compression) — the most universally compatible BMP variant, readable by every Windows version since 2.0, every major image viewer, and System.Drawing.Bitmap / LoadImage() / OpenCV / Pillow without extra flags. Frames are encoded BGR-bottom-up in the file (the BMP standard) but every modern reader inverts that transparently.

My downstream tool wants 8-bit indexed BMP. Can I get that?

Not directly — frames come out as 24-bit RGB. Convert in a second pass using ImageMagick (magick frame.bmp -colors 256 -type Palette out.bmp), Photoshop (Image > Mode > Indexed Color), or GIMP (Image > Mode > Indexed). Going from 16+ million colors down to 256 is a perceptual choice (which palette? dithered or not?) that's better made on the still than on the video.

Is the BMP smaller if I drop resolution?

Linearly. BMP file size scales with width x height x bytes-per-pixel, so halving each dimension quarters the file. A 960x540 24-bit BMP is ~1.5 MB versus ~6.2 MB at 1080p. If you're staying inside an embedded display that's only 320x240, drop to that resolution at extraction time rather than letting the device down-sample at runtime — you save flash and CPU on the target.

Anything I should do after to shrink large batches?

If you only need lossless storage (not pixel-exact-as-bitmap), zip the folder — uncompressed bitmaps from similar frames compress aggressively in DEFLATE. For long-term archival of stills you need to view often, consider compressing the BMP set with optional palette reduction, or convert the source MOV to a more efficient codec via MOV to MP4 and extract on demand instead of storing thousands of bitmaps.