Initializing... drag & drop files here
Supports: TIFF, TIF
.tif and .tiff extensions and processes them as a sequence in filename order.TIFF is a lossless raster container favored by scanners, microscopes, satellite imagery, and archival workflows — single files can run hundreds of megabytes because every pixel is stored uncompressed (or losslessly compressed with LZW/ZIP). WebM, introduced by Google in 2010 and based on the Matroska container, is the open web's default video format: VP9 and Opus inside a royalty-free wrapper that plays in every major browser. Converting a TIFF sequence to WebM turns a folder of static frames into a single playable clip that's roughly 1-3% the size of the originals while staying perceptually lossless at the right bitrate.
<video> tag where animated GIF would balloon to 10x the size.| Property | TIFF (TIF) | WebM |
|---|---|---|
| Type | Still-image raster container | Video container (Matroska-based) |
| First released | 1986 (Aldus, now Adobe) | 2010 (Google / WebM Project) |
| Compression | Uncompressed, LZW, ZIP, JPEG, PackBits | VP8, VP9, or AV1 video; Vorbis or Opus audio |
| Color depth | 1, 8, 16, 32 bits/channel; CMYK, RGB, Lab, grayscale | 8-12 bits/channel YUV (codec-dependent) |
| Alpha channel | Yes (per-pixel, multiple channels) | VP9 / AV1 alpha supported in Chrome/Firefox |
| File size (1080p frame) | 6-25 MB uncompressed, 2-8 MB LZW | ~50-200 KB per frame at 4 Mbps VP9 |
| Animation | Multi-page TIFF (not a true video) | Native video with audio track |
| Browser playback | None natively — needs server-side conversion | Chrome 25+, Firefox 28+, Edge 79+, Safari 16+ |
| Primary use | Print, archival, scientific imaging | Web video, HTML5 <video>, chat embeds |
| Codec | Best for | Compression vs VP8 | Browser support |
|---|---|---|---|
| VP9 (default) | Most web use, 720p-4K | ~30-50% smaller files at same quality | Chrome 29+, Firefox 28+, Edge 79+, Safari 14.1+ |
| VP8 | Maximum compatibility with old browsers | Baseline | Chrome 25+, Firefox 28+, Edge 79+, Safari 16+ |
| AV1 | Smallest files, modern devices only | ~30% smaller than VP9 | Chrome 70+, Firefox 67+, Edge 121+, Safari 17.4+ |
Pair with Opus (modern, lower bitrate) or Vorbis (legacy) for audio — though TIFF-sourced sequences have no audio track by default.
WebM uses royalty-free codecs (VP8/VP9/AV1, Opus, Vorbis) so you can host clips without licensing concerns — relevant for open-source projects, Wikimedia uploads, and HTML5 <video> players that want to avoid the H.264 patent pool. MP4 with H.264 is still slightly more compatible (older Safari, smart TVs, embedded players), so pick MP4 if you need the broadest device reach. Need MP4 instead? Use TIFF to MP4.
Files are sequenced alphabetically by filename, so frame_001.tif, frame_002.tif, frame_003.tif will render in that order. If your camera or render software uses zero-padded numbering (e.g., 0001.tif rather than 1.tif), the order is deterministic. Mixed naming like frame_1.tif and frame_10.tif will sort 1, 10, 11, 2, 3 — rename or pad before uploading.
Each uploaded TIFF is treated as one image, so a multi-page TIFF contributes a single frame per upload, not one per page. If you need each TIFF page as its own video frame, split the multi-page TIFF into individual files first (ImageMagick: magick input.tif page_%03d.tif) and upload the resulting set.
For motion captured at a fixed cadence (time-lapse, microscopy, render output), pick a duration that matches your acquisition: 1/30s for a 30 fps capture, 1/24s for film-style 24 fps. For document or photo slideshows, 2-5 seconds per frame lets viewers read each image. The dropdown goes from 1/60s (60 fps) down to 10 seconds per frame, so you can produce both smooth video and slow flipbooks.
No. WebM's VP9 supports up to 12-bit per channel YUV (Profile 2/3), but most browsers only play the standard 8-bit Profile 0 reliably. The converter quantizes 16-bit TIFFs down to 8-bit (256 levels per channel) — fine for most viewing scenarios but a meaningful loss for scientific imaging or HDR archival work. For lossless intermediates, keep the originals.
Two likely causes. First, the resolution preset may be downscaling: the default 768p shrinks 4K TIFFs to 1366x768. Set the Video resolution to match your source (e.g., 1920x1080 for HD frames, custom width/height for unusual aspect ratios). Second, the Quality Preset may need a bump — the default is Very High but you can go higher, or switch from preset to a higher target bitrate (4-8 Mbps for 1080p VP9 is a good starting point).
Yes, on iOS 17.4+ and Safari 16+ on macOS. Earlier Safari versions (pre-16) and iOS before 17.4 lack native WebM playback — for those, encode to MP4/H.264 instead with TIFF to MP4, or provide both sources in a <video> tag and let the browser pick.
VP9 and AV1 both support alpha-channel WebM (used widely for stickers and overlays), and the WebM container preserves the alpha. Chrome, Firefox, and Edge play alpha WebM natively; Safari does not as of Safari 17, so transparent regions will render as black there. Pick a non-black Background Color in the advanced options if Safari users need a clean fallback.
ffmpeg with the libvpx-vp9 encoder produces effectively the same output — this converter wraps the same underlying open-source encoders so you don't have to install ffmpeg or memorize the input glob pattern. For repeatable batch jobs on hundreds of sequences, ffmpeg is faster; for one-off conversions, browser upload is simpler. If you also need the reverse direction, see WebM to MP4 or convert your sequence to other targets like PNG to WebM and JPG to WebM.