Initializing... drag & drop files here
Supports: WEBM
WebM is a Google-led web video container that wraps VP8, VP9, or AV1 video and is the default format for many screen recorders, browser-based capture tools, and <video> tags on the open web. TIFF (Tagged Image File Format) was first published by Aldus in autumn 1986, and Adobe inherited the spec when it acquired Aldus in 1994; TIFF 6.0 from June 1992 is still the reference revision. The format is deliberately built for archival and prepress use, supporting 1-, 8-, and 16-bit channels, multiple lossless compression schemes, and multi-image files. Pulling a still frame out of a WebM into TIFF is the right move when the destination is print, museum/library preservation, or an editing pipeline that demands lossless source images.
| Property | WebM | TIFF |
|---|---|---|
| Type | Video container | Still-image container |
| Codecs / compression | VP8, VP9, AV1 video; Opus/Vorbis audio | None, LZW, ZIP/Deflate, JPEG, PackBits, CCITT G3/G4, ZSTD, WebP |
| Lossless option | VP9 and AV1 support lossless mode; rarely used | Yes (None, LZW, ZIP, PackBits, CCITT) — standard archival use |
| Bit depth | 8, 10, 12 bits per channel (codec-dependent) | 1, 8, 16, 32 bits per channel; floating-point allowed |
| Multi-image | Yes (frames over time) | Yes (multi-page via subfiles / IFDs) |
| Typical size (one HD still) | ~50-500 KB encoded across a frame | 2-8 MB uncompressed; 0.5-3 MB with LZW/ZIP |
| Browser playback / view | Native in Chrome, Firefox, Edge, Safari 16+ desktop / 17.4+ iOS | No native browser support; requires desktop or plugin |
| Best for | Streaming, embedded web video, screen recording | Print, archive, scientific imaging, prepress |
| Year introduced | 2010 (Google, based on Matroska) | 1986 (Aldus); 6.0 spec frozen 1992 |
| Compression | Lossless? | Best for | Notes |
|---|---|---|---|
| None | Yes | Maximum compatibility, scientific masters | Largest files; opens anywhere |
| LZW | Yes | General archival, 8-bit photos | Wide support; can enlarge 16-bit files due to dictionary overhead |
| ZIP (Deflate) | Yes | 16-bit photo archive, smallest lossless | Better ratio than LZW on high-bit-depth content; not all legacy tools read it |
| JPEG | No | Smaller files when lossy is acceptable | Quality tradeoff; avoid for masters that will be re-saved |
| PackBits | Yes | Legacy Mac / QuickDraw pipelines | Low compression; mostly historical |
| CCITT Group 4 | Yes | 1-bit bitonal scans, fax, document archive | Only valid for true black-and-white |
WebM is interframe-compressed: each second of video reuses pixels from neighboring frames, so per-frame cost is tiny. TIFF stores each image in full as raw pixels (optionally entropy-coded with LZW or ZIP). A 1080p frame is 1920 × 1080 × 3 bytes ≈ 6 MB uncompressed; even with LZW it usually lands in the 1.5-3 MB range. That's expected, and it's why TIFF is an archival format rather than a delivery format.
For lossless archival of 8-bit color frames, LZW is the safest choice for compatibility. For 16-bit images, ZIP (Deflate) compresses better because LZW's dictionary approach can actually grow 16-bit files. Pick None when the destination is an old RIP or a scientific tool that struggles with compressed TIFFs. Only use JPEG inside TIFF if you specifically want smaller files and accept generation loss on re-saves.
Yes. Use the Multiple Screenshots option in Advanced Options to pull a series of frames across the clip. You'll get one TIFF per extracted frame; if you need them bundled into a single multi-page TIFF, combine them downstream in Photoshop ("Save As" with the multi-page option) or ImageMagick (convert frame*.tif -compress lzw output.tif).
All three codecs that WebM legitimately carries — VP8, VP9, and AV1 — decode through the standard pipeline used here, so frame extraction works regardless of which encoder produced the source. WebM files with non-standard codecs (rare in the wild) may fail; in that case re-mux to MP4 with ffmpeg first.
The DPI tag stored in a TIFF is metadata; it tells print software how to interpret the pixel grid but does not change pixel count. A 1920 × 1080 frame is 1920 × 1080 pixels regardless of the DPI value. If you set DPI to 300 in your image editor afterward, the same image prints at 6.4 × 3.6 inches; at 150 DPI it prints at 12.8 × 7.2 inches. To get more pixels for larger prints, start from a higher-resolution WebM (4K or 8K source).
Only if the WebM was authored with VP9 or VP8 alpha (a Matroska feature used mainly for transparent overlays). Most WebMs have no alpha, and the resulting TIFF is opaque RGB. When a source does include alpha, frames are extracted with a transparent background and the TIFF is saved as RGBA.
PNG is lossless 8-bit RGBA, ideal for web and screenshots but capped at 16 bits per channel in PNG-2 (limited tool support). JPG is small and lossy — fine for sharing but wrong for archival. TIFF beats both for prepress and preservation because it accepts 16-bit channels, multiple compression schemes, layers, and ICC profiles in a single file the print industry has supported for nearly 40 years.
Conversion runs on our servers, so the practical limit is upload size and connection speed and the time you're willing to wait. Clips up to ~500 MB usually convert without issue on a modern laptop. For longer recordings, trim to the segment you actually need first, or process on a desktop where RAM headroom is larger.
files are processed on our servers and deleted automatically after a few hours for this conversion. There's no account, no watermark, and files are cleared from the session after you're done. If you'd rather start from a different source format, see MP4 to TIFF or the general Video to TIF tool, which accepts most container formats.