Initializing... drag & drop files here
Supports: AVI
AVI is Microsoft's RIFF-based container, introduced with Video for Windows on November 10, 1992. It's still the lingua franca for older camcorders, scientific capture cards, surveillance DVRs, and legacy Windows software — but you can't open an AVI in Photoshop, send a frame to a print shop, or hand a still to a forensic analyst. TIFF, designed by Aldus in the late 1980s and now maintained by Adobe (TIFF 6.0 spec, June 1992), is the lossless image format those workflows expect. Common reasons to convert AVI → TIFF:
imread and ImageJ's TIFF importer both round-trip pixel data without modification.| Property | AVI | TIFF |
|---|---|---|
| Type | Video container (RIFF) | Single-image (or multi-page) raster |
| Year introduced | 1992 (Microsoft) | 1986 (Aldus); spec 6.0 in 1992 (Adobe) |
| Compression | Codec-dependent (DV, MJPEG, Xvid, Cinepak, RLE, uncompressed) | LZW, DEFLATE, PackBits, CCITT, ZSTD, JPEG, WebP, JP2K, or none |
| Bit depth | Codec-dependent, usually 8-bit per channel | 1, 8, 16, 32-bit per channel; supports float HDR |
| Audio | Yes | No |
| Max file size | 2 GB (legacy) / ~1 EB (OpenDML) | 4 GB classic TIFF; BigTIFF removes that cap |
| Universal viewers | VLC, MPC-HC, ffplay | Photoshop, GIMP, Preview, ImageJ, every print RIP |
| Best for | Capturing video / preserving raw recordings | Pixel-faithful stills, print, archival, analysis |
A 1080p uncompressed TIFF is roughly 1920 × 1080 × 3 bytes ≈ 5.9 MB per frame. Extract every frame of a 30-second 30 fps clip uncompressed and you'll generate ~5.3 GB across 900 files — pick LZW or DEFLATE if disk space matters.
| Compression | Lossless? | Typical size vs uncompressed | Best for |
|---|---|---|---|
| NONE | Yes | 100% | Forensic masters, any decoder ever built |
| LZW | Yes | 40-70% | Default lossless — Photoshop, GIMP, every TIFF tool reads it |
| DEFLATE (ZIP) | Yes | 35-60% | Smaller than LZW; widely supported on modern stacks |
| PackBits | Yes | 60-90% | Macintosh-era simple decoders, hospital PACS legacy |
| ZSTD | Yes | 35-55% | Fastest decode at LZW-class ratios; modern libtiff only |
| WebP | Yes/Lossy | 20-50% | New (libtiff 4.x) — small files, narrower viewer support |
| JPEG | No | 5-15% | When you need a tiny TIFF and DCT artifacts are acceptable |
| JP2K | No | 8-20% | Wavelet-based; archival JPEG 2000 workflows |
| CCITT Fax 4 | Yes | 1-5% | Bilevel only — scanned documents, line art |
If you pick NONE, LZW, DEFLATE, PackBits, or ZSTD for compression, the saved TIFF is a bit-exact copy of the decoded video frame — no quantization, no chroma subsampling beyond what the source codec already applied. The catch: most AVI files use a lossy video codec (Xvid, DivX, Cinepak, MJPEG), so the TIFF can only be as faithful as the codec's decoded output. To get a fully lossless chain, the AVI itself must use an uncompressed or lossless codec like Lagarith, HuffYUV, or FFV1. JPEG / JP2K / WebP TIFF compression is additionally lossy and should be avoided for forensic or archival work.
Because video codecs use temporal compression — a 30-second 1080p AVI at 5 MB stores frames as small differences from neighbors. TIFF stores every pixel of every frame independently. Uncompressed 1080p RGB is ~5.9 MB per frame, so 30 seconds at 30 fps becomes ~5.3 GB. Use LZW or DEFLATE to shave 40-65% off that, drop resolution to 720p, or extract fewer frames (every 5 seconds instead of every frame).
Functionally identical. Both contain the same TIFF byte stream — .tif is the original 8.3 DOS extension; .tiff is the four-letter modern variant. Some legacy Windows tools and old print workflows expect .tif; macOS, Linux, Photoshop, and every modern application accept both. If you're feeding a specific pipeline, match what it expects; otherwise either is fine.
Use Specific Frame mode and enter the timestamp in seconds (the timestamp box accepts decimals, so 12.5 picks the frame at 12.5 seconds). The extracted frame is the closest source frame to that timecode — for a 30 fps source, that's accurate to ±33 ms. For sub-frame accuracy (e.g., motion-interpolated mid-frame stills), no online tool can do it from a compressed AVI; you'd need optical-flow software like Twixtor or RIFE.
Both are lossless raster formats. PNG is locked to RGB or RGBA at 8 or 16-bit, uses DEFLATE, and is universal on the web. TIFF is more flexible — it carries arbitrary bit depths up to 32-bit float, supports CMYK / L*a*b* / multispectral color spaces, holds multiple images per file, and embeds richer metadata for print and scientific workflows. Pick PNG for web-bound stills; pick TIFF when the destination is print, forensics, scientific analysis, or a VFX pipeline. See AVI to PNG for the PNG path.
Yes — use Multiple Screenshots at a rate matching your source frame rate (24 / 25 / 30 / 50 / 60 fps presets are available, or set a custom interval). The output is a set of TIFFs you can download as a ZIP. Compositing apps will read the sequence by selecting the first frame and enabling "TIFF sequence" in the import dialog.
TIFF supports an alpha channel (RGBA). However, AVI frames are almost always opaque — RGB or YUV without an alpha channel, since video codecs don't carry transparency outside niche formats like WebM with VP9-alpha or specialized ProRes 4444. So in practice your AVI-sourced TIFFs will be flat RGB. If you need alpha, the source needs to be a format that carries it.
Classic TIFF uses 32-bit offsets and tops out at 4 GB per file. For larger images — gigapixel scans, hyperspectral cubes, microscopy mosaics — the BigTIFF extension (LibTIFF 4.x, stable since 2011) replaces those offsets with 64-bit values and effectively removes the cap. Single video-frame TIFFs from a 4K or below source will never come close to 4 GB, so the limit only matters if you're embedding many pages into one multi-page TIFF.
Yes. Drop in multiple AVIs and each converts in parallel within your browser session. Settings can apply to all files or be set per file. Download individually or as a single ZIP. For a single multi-clip job — for example, pulling cover stills from 50 surveillance AVIs — Multiple Screenshots at every 30 seconds with LZW compression typically finishes in a few minutes.