MOV to TIFF Converter

How to Extract TIFF Frames from MOV Online

1. Upload Your MOV File: Drag and drop or click "+ Add Files" to select a QuickTime MOV — iPhone recordings, Final Cut Pro exports, DSLR captures, and ProRes masters are all supported. Batch upload works for multi-take shoots.
2. Pick a Quality Preset and Compression Type: Default is Very High (Recommended). Drop to High or Medium for proxy-grade frames, or step up to Highest for archival masters. Set Compression Type to LZW for lossless 8-bit, JPEG for the smallest file at a quality cost, Deflate (ZIP) for 16-bit images, PackBits for legacy publishing pipelines, or None for absolute fidelity.
3. Set Resolution and Frame Selection (Optional): Keep original to match the source (4K MOV stays 3840×2160), pick a Preset Resolution, scale by Resolution Percentage, or enter custom Width/Height with aspect lock. Under Frame Selection choose Specific Frame (enter the second mark) or Multiple Screenshots (set an interval in Seconds) — useful for thumbnailing or scientific frame-by-frame analysis.
4. Convert and Download: Click Convert. processing runs on our servers — no sign-up, no watermark, uploaded only to xconvert’s own servers, auto-deleted after a few hours. Multi-frame jobs return a ZIP.

Why Extract TIFF from MOV?

MOV is Apple's QuickTime container — the default for iPhone 13 Pro and newer ProRes recordings, Final Cut Pro exports, and most DSLR/mirrorless video. TIFF (Tagged Image File Format), in use since the Adobe-published 6.0 specification of June 1992, is the long-standing lossless reference for print, archival, and analysis. Extracting frames as TIFF preserves every pixel the camera captured — no JPEG ringing, no chroma subsampling, no generation loss when you re-edit.

• Print and publishing stills — A 4K MOV frame at 3840×2160 hits ~8.3 megapixels, enough for a sharp 11×17 inch print at 300 DPI. Magazines, catalogs, and broadcast press kits ask for TIFF specifically because the workflow assumes lossless input.
• Scientific and medical imaging — Microscopy, motion capture, and clinical video analysis rely on TIFF because every frame is bit-exact and supports 16-bit depth. JPEG's 8-bit lossy compression discards data needed for quantitative measurement.
• VFX plates and rotoscoping — Compositors load TIFF sequences into Nuke, After Effects, or Fusion to preserve linear color and alpha for keying, tracking, and matte painting. Lossless input is non-negotiable when you'll be re-rendering 200 times.
• Long-term archival — TIFF is the Library of Congress's recommended preservation format for raster imagery, alongside formats like PNG and JPEG 2000. Frames stored as uncompressed or LZW TIFF will still open in 2050.
• Astrophotography stacking — Planetary and deep-sky imagers extract every frame from a MOV capture, then stack the sharpest in software like AutoStakkert! or PixInsight. TIFF preserves the dynamic range needed for noise reduction.
• OCR and document capture — Whiteboard, lecture, and document video benefits from TIFF's lossless edges; downstream OCR engines (Tesseract, ABBYY) get cleaner glyphs than from re-compressed JPEG.

MOV vs TIFF — Container vs Frame Format

TIFF Compression Type Guide

Frequently Asked Questions

Will the TIFF frames match my source MOV's resolution exactly?

Yes, if you keep "Original" resolution. A 1920×1080 MOV produces 1920×1080 TIFFs; a 3840×2160 ProRes export from an iPhone 15 Pro produces 3840×2160 TIFFs. Choose Resolution Percentage or enter custom Width/Height to downscale (useful for proxies) — upscaling beyond source resolution will not add detail.

Which TIFF compression should I pick?

LZW for 8-bit photography (the safe default and what print shops expect). Deflate/ZIP for 16-bit or HDR work — LZW actually makes 16-bit TIFFs bigger than uncompressed, so it's the wrong choice there. None if a downstream tool refuses any compression. Avoid JPEG-in-TIFF — it's lossy, defeats the format's purpose, and an actual.jpg is more interoperable. See our TIFF to JPG converter if you decided you want JPG instead.

How big will the TIFF files be?

Roughly: a 4K frame at 8-bit RGB with LZW is ~10–15 MB; uncompressed it's ~25 MB; ZIP-compressed 16-bit can be 40+ MB. A 60-second 30 fps clip exported as a TIFF sequence is 1,800 frames — plan for 15–30 GB. Use frame intervals or trim the source if you only need keyframes.

Can I extract one specific frame at a timestamp?

Yes. Pick Specific Frame and enter the second mark (e.g., 12.5 for twelve and a half seconds in). For multiple frames at fixed intervals — say one frame every two seconds for a thumbnail strip — use Multiple Screenshots and set the interval.

Does ProRes 422 / ProRes 4444 input preserve 10-bit or 12-bit color?

We decode the MOV's full bit depth, but TIFF output bit depth depends on the Image Bit Depth setting. For 10-bit ProRes 422 footage, choose 16-bit TIFF (the smallest container that holds >8-bit cleanly). For 12-bit ProRes 4444 with alpha, also use 16-bit; true 12-bit packing isn't a baseline TIFF feature, so 16-bit is the standard delivery target.

Why not just extract JPGs instead?

JPEG is 8-bit, lossy, and re-compresses every time you save. That's fine for web preview but unacceptable for print proofing, color grading, scientific measurement, or any workflow that will edit the frame later. If web sharing is the only goal, our MOV to JPG converter is a better fit. TIFF wins when fidelity matters more than file size.

Can I batch process multiple MOV files?

Yes — drag in several MOV files and each is processed in sequence with the same settings. Each input produces its own TIFF (single frame) or ZIP of TIFFs (multiple frames). Browser memory is the limit; for 4K ProRes masters longer than a few minutes, run them one at a time.

Does this work for iPhone Cinematic mode or Spatial Video MOV files?

The video track is extracted normally — frames come out as TIFF stills at the recording resolution. Cinematic mode's depth map and rack-focus metadata are video-track features and won't survive as a still; you'll get the rendered frame as the camera composed it. For Spatial Video (stereo MV-HEVC), you'll get one eye's frame per output; the second view isn't preserved in a flat TIFF.

How does this compare to running ffmpeg locally?

ffmpeg's -vf fps=N output_%04d.tif is the canonical CLI workflow and gives you maximum control. This page is the no-install version: you get the same frame-extraction result with a quality preset, compression dropdown, and frame-selection UI, without setting up ffmpeg, learning filter syntax, or writing a shell script. For one-off jobs or non-developers, the browser route is faster end-to-end. For other formats, see MOV to PNG for lossless 8-bit web frames or Video to TIFF if your source isn't a MOV.