Step 1: Deliver your M4V files using the button above or by place and set.
Step 2: Click the 'Process' button to start the processing.
Step 3: Obtain your converted TIFF files.
M4V to TIFF Processing FAQ
How do I extract frames from a M4V video as TIFF images?
+
Upload the M4V file and the converter exposes a frame-extraction picker: every Nth frame, frames at specific timestamps, or one frame per second. Each chosen frame is encoded as a separate TIFF file and bundled as a ZIP archive for download.
At what resolution does the extracted TIFF image come out?
+
Same resolution as the M4V video — a 1080p source produces 1920×1080 TIFF frames; a 4K source produces 3840×2160 TIFF frames. Use /resize-image/ after extraction if you need smaller thumbnails or social-media-sized assets.
Can I extract every frame from a M4V file as TIFF?
+
Yes, but be careful with file count — a 30 fps 1-minute video produces 1,800 frames, and a 60 fps 10-minute video produces 36,000. We pack them into a ZIP automatically. For long clips use the "1 per second" option or specific timestamps to keep the bundle manageable.
Will the TIFF images preserve the M4V color grading?
+
Yes — colour is decoded with the same matrix the source uses (BT.709 for HD, BT.2020 for 4K HDR). HDR sources are tone-mapped to SDR when extracting to TIFF (PNG / JPG cannot store HDR pixel ranges natively); the tone-mapping curve is the same one used by mpv / ffmpeg.
What is the file size of one extracted TIFF frame?
+
Depends on resolution and target. A 1080p PNG frame is 2-5 MB; a 1080p JPG at quality-85 is 200-500 KB; a 1080p WebP at quality-85 is 100-300 KB. Multiply by frame count to size the ZIP — every-frame extraction of a 10-minute 1080p video as PNG is ~50 GB.
Does the extracted TIFF keep any camera metadata?
+
The M4V container does not store per-frame EXIF the way a still camera does, so the extracted TIFF files come out with empty EXIF. We embed a `creation_time` field pointing at the source frame timestamp so you can re-sort the bundle by chronology after download.
How long does frame extraction from M4V to TIFF take?
+
Frame extraction is fast — typically 20-30% of source duration on the standard pipeline. A 5-minute M4V → TIFF bundle finishes in about a minute regardless of frame count, because the bottleneck is the TIFF encoder, not the demuxer.
Can I extract frames at specific timestamps in the M4V video?
+
Yes — the advanced option accepts a comma-separated list of timestamps (e.g. `00:01:23,00:05:00,00:10:42`) and produces one TIFF file per timestamp. Useful for chapter thumbnails, scene reference shots, or generating poster frames for HTML5 video.
Is my M4V video private during frame extraction?
+
Yes — same privacy model as every conversion. The source video and extracted frame bundle are processed in isolated workers and deleted within minutes of completion. No frame is ever shown to a human reviewer.
Why are my extracted TIFF frames blurry?
+
Almost always motion blur from the source (the camera was moving when the frame was captured). Try picking timestamps from static scenes, or extract several adjacent frames and choose the sharpest. The pipeline does not synthesize sharpness — for that, use /upscale/ on the extracted TIFF afterwards.
Does this tool support extracting one frame per scene change?
+
Not in the basic flow — use the "1 per second" option as an approximation, then visually pick scene-change frames. A dedicated scene-detection extractor (PySceneDetect-equivalent) is on the roadmap.
Can I use the extracted TIFF frames commercially?
+
Yes, subject to whatever licence governs the source M4V content. The format change adds no claim — we add no watermark, embed no tracking, and claim no licence over the TIFF output. Public-domain video produces public-domain frames; your own footage stays your own.