Initializing... drag & drop files here
Supports: F4V
This walks you through pulling one frame out of an F4V video and saving it as a TIFF — a lossless raster image built for archiving, print, and precision editing rather than the web. F4V is Adobe's Flash-era MP4 variant: an ISO-base-media container that usually carries H.264 video, so its frames are far cleaner than anything the older FLV/Sorenson era produced. By the end you will have a single still at the exact moment you want, in a format that preserves every pixel the decoder produced — and you will know the one setting that quietly decides whether your "TIFF" is actually lossless.
.f4v file onto the page, or click "+ Add Files" to browse. Several files queue and run with the same settings.12.5 captures the frame 12.5 seconds in. That single frame becomes your TIFF.The single thing worth slowing down for is Compression Type, because on this page it defaults to JPEG — and JPEG-in-TIFF is lossy even though the file still ends in .tiff. If you are reaching for TIFF specifically to keep a pristine, re-editable frame, leaving that default in place quietly defeats the purpose. The fix is one dropdown change before you convert. Here is how to pick:
You can also scale the frame before download with Resolution Percentage, Preset Resolutions, or Width x Height; the frame is captured at the video's native resolution by default.
.tiff extension alone does not guarantee lossless data.<img> tag, and MDN lists it among image types to avoid for web content. Use F4V to PNG for a lossless, web-friendly still instead.A few F4V files resist a clean grab. DRM-protected or partially downloaded streaming files may decode to nothing or corrupt frames — the H.264 data simply is not all there. Heavily damaged headers can stop the decoder before it reaches your timestamp. And because Adobe Flash Player reached end of life on 31 December 2020, some genuinely old .f4v files were authored with non-standard tooling that wrote the container loosely; if a frame extracts garbled, re-mux the file to a clean MP4 first with F4V to MP4, then pull the frame from the MP4. For a frame you only need to view or post rather than archive, a web format like F4V to JPG sidesteps TIFF's tooling quirks entirely.
No — and this is the honest catch. TIFF stores the decoded frame without adding any further loss, but it cannot recover detail the H.264 encode never kept. The good news is that F4V is an H.264-era container, so the source is usually far cleaner than a frame pulled from the older FLV/Sorenson era — you generally have decent pixels to preserve. TIFF keeps those exact pixels verbatim; it does not upscale or sharpen them. Think of it as a faithful, re-editable wrapper for whatever the decoder produced.
Both are lossless, so neither changes image quality — the choice is size versus compatibility. Deflate/ZIP typically produces a slightly smaller file, while LZW is the most broadly supported compressed-TIFF scheme and opens in older software too. Pick None only when you need maximum compatibility with legacy tools that reject any compressed TIFF, accepting a larger file. For a single extracted frame the absolute sizes stay small either way, so leaving lossless compression on is the sensible default.
The output is a standard baseline TIFF conforming to TIFF 6.0, published 3 June 1992 — still the current revision. TIFF was created by Aldus in 1986, and the specification passed to Adobe when it acquired Aldus in 1994; it has stayed stable since, which is part of why TIFF remains a dependable archival container decades later. The frame opens in Photoshop, GIMP, ImageMagick, and essentially any imaging tool.
Adobe introduced F4V on 3 December 2007 alongside Flash Player 9 Update 3, building it on the ISO base media file format so Flash could stream H.264 video and AAC audio — the older FLV layout could not carry that codec stack cleanly. Because it is MP4-family rather than the old FLV structure, the H.264 frame inside extracts much like a frame from a modern .mp4. Adobe Flash Player reached end of life on 31 December 2020, so no mainstream browser plays F4V natively now, though desktop players like VLC still decode the H.264/AAC streams directly.
It depends on resolution and the compression you pick. In our testing, a 1280×720 H.264 frame pulled from an F4V and saved as uncompressed 8-bit RGB TIFF landed near 2.6 MB, matching the raw pixel math (1280 × 720 × 3 bytes ≈ 2.65 MB). Turning on LZW or Deflate trimmed that noticeably on natural-image content with zero quality loss — which is why we recommend a lossless compressed scheme rather than leaving the file uncompressed. There is also a dedicated F4V to TIF converter if your other tools expect the three-letter .tif spelling; the bytes are identical.
Your F4V is uploaded over an encrypted (TLS) connection, processed on our servers, and then deleted automatically a few hours after conversion. There is no sign-up, no watermark on the output, and your files are never shared or made public. The frame is captured at the video's native resolution, and you can scale it down with the Resolution Percentage or Width x Height controls before downloading.