Initializing... drag & drop files here
Supports: TIFF, TIF
.tif / .tiff frames. Multi-page TIFFs are supported, and so are numbered sequences (frame_0001.tif, frame_0002.tif...). Batch uploads queue together so a whole timelapse becomes a single HEVC clip.TIFF is the archival workhorse of scientific imaging, photography, GIS, and print — a single 16-bit RGB frame at 4K can be 50 MB or more, and a 1,000-frame microscopy session easily fills 50 GB. HEVC (H.265) was finalised by ITU-T in 2013 and routinely delivers around 50% smaller files than H.264 at matching quality, which makes it the practical container for sharing or reviewing a TIFF sequence once analysis is done.
| Property | TIFF (input) | HEVC / H.265 (output) |
|---|---|---|
| Type | Still image / multi-page raster | Video bitstream (typically in .hevc, .mp4, or .mov container) |
| Year released | 1986 (Aldus, now Adobe) | ITU-T H.265 Rec. approved 2013 |
| Compression | None / LZW / Deflate / JPEG / ZSTD (mostly lossless) | Lossy block-based inter-frame (CTUs up to 64x64) |
| Typical file size, 1080p frame | 6-50 MB per frame uncompressed | ~0.1-1 MB per second of 1080p video |
| Bit depth | 1, 8, 16, 32 (incl. float) | 8-bit Main, 10-bit Main 10, 12-bit |
| Color | RGB, CMYK, Lab, grayscale, alpha, multi-channel | YUV 4:2:0 / 4:2:2 / 4:4:4 |
| Native browser playback | None (no <img> autoplay; needs JS viewer) |
Safari 13+, Chrome 107+ (partial), Firefox 137+ (partial), Edge (partial via Windows codec) |
| Best for | Archival masters, scanning, scientific frames | Sharing, streaming, embedded video |
Source: caniuse.com/hevc; ITU-T H.265 recommendation; Adobe TIFF spec.
| Setting | What it does | When to change |
|---|---|---|
| Quality Preset = Very High | x265 defaults tuned for visually-lossless output | Leave for archival / publication-grade clips |
| Quality Preset = High / Medium | Lower CRF target, faster encode | Web review copies; previews |
| Constant Quality (CRF 18-22) | Quality stays constant, bitrate floats | Time-lapses with varied motion (microscopy, weather) |
| Constant Quality (CRF 23-28) | Smaller file at modest quality cost | Social posts, Discord uploads under 10 MB |
| Duration = 1/24 sec per frame | True 24 fps cinematic playback | Astrophotography, art timelapses |
| Duration = 1/30 sec per frame | 30 fps NTSC-style smoothness | YouTube uploads, drone shots |
| Duration = 1-10 sec per frame | Slow slideshow / explainer | Pathology screening, photo review |
| Resolution = Keep original | No resampling — sharpest output | When TIFF frames are already at delivery size |
| Resolution = 1080p / 720p preset | Downscale to share-friendly target | Source is 4K+ but target is web |
| Background Color | Fills letterbox/pillar bars | Mixed-aspect-ratio TIFF sequences |
You choose. "Merge images" stitches every uploaded TIFF (in filename order) into one HEVC clip — the standard timelapse workflow. "Video per image" produces one short HEVC file per input frame, which is useful when each TIFF is a separate scene rather than a frame in a sequence. For numbered sequences (frame_0001.tif, frame_0002.tif...), Merge is almost always what you want.
Pick 1/24 second for 24 fps cinema-style, 1/30 second for 30 fps NTSC, or 1/60 second for 60 fps action footage. The default 5 seconds per frame is meant for slideshow-style playback — useful for a manuscript scan or pathology slide review, but it produces a very slow video for a 1,440-frame microscopy session. A 1,440-frame stack at 1/30 second runs 48 seconds; at the 5-second default it would run two full hours.
Yes. Each page in a multi-page TIFF (common from scanners and microscopy software like Fiji/ImageJ) becomes one video frame in document/filename order. If page order matters (z-stacks, time series) confirm your imaging software exports pages in capture order, or export to numbered single-page TIFFs first.
Safari has full HEVC support from Safari 13 onward (macOS 10.13+ and iOS 11+) — that's Apple's home codec. Chrome added partial support in version 107 (mostly relying on platform hardware decoders), Firefox added partial support in version 137 (Windows-first), and Edge supports it partially via the Windows HEVC Video Extensions. For maximum cross-browser playback, wrap the HEVC stream in an MP4 container (convert HEVC to MP4) or fall back to H.264 (HEVC to MP4) for older audiences.
Dramatically smaller. A 1,000-frame, 1920x1080 TIFF stack at 8-bit RGB is roughly 6 GB uncompressed. The same content as HEVC at CRF 22 is typically 5-40 MB depending on motion complexity — savings of 99% or more. Versus an H.264 re-encode at matched perceptual quality, HEVC saves another 25-50% (ITU-T figure; cam-do.com observed 98% reduction on a GoPro timelapse).
Not at full precision in standard HEVC delivery. Main 10 (10-bit) is the highest profile in wide playback support; Main 12 exists but is rare in consumer decoders. If you started with 16-bit microscopy TIFFs, the conversion clips to 10-bit YUV — fine for visual review, but keep the raw TIFFs for any quantitative analysis. For lossless intermediates, TIFF to MP4 with a high CRF or TIFF to MOV with ProRes-like settings preserve more dynamic range.
The encoder pads to the largest frame and fills the empty area with your chosen Background Color (Black by default, plus White / Gray / 20+ named colors). To avoid pillarboxing, crop or resize the source TIFFs to a uniform size first (resize TIFF) or pick a Fixed Resolution preset so the encoder scales each frame to fit. For best HEVC efficiency, stick to even widths/heights (1920x1080, 1280x720); odd dimensions get padded by 1 px.
x265 is the reference open-source HEVC encoder maintained by MulticoreWare; it's what FFmpeg ships and what most professional pipelines use. Hardware encoders (NVENC, Quick Sync, VideoToolbox) are faster but typically 10-30% less efficient at matched quality, which matters when you're encoding hundreds of frames into a single archive copy. For one-off web previews the difference is negligible.
Yes — under Advanced Options you can set a start time and duration so only a slice of the merged sequence is encoded. Useful when only the first 200 of 2,000 frames are interesting. For source video already in HEVC, the dedicated trim HEVC page is faster than re-encoding.
There's no hard per-file cap on the free tier, but very large jobs (thousands of multi-gigabyte TIFFs) are best split into batches so the browser session stays responsive. For very large sequences, downsizing to 1080p or 720p with Fixed Resolution first usually pays off — most viewers can't tell the difference and the encode finishes faster.