Initializing... drag & drop files here
Supports: TIFF, TIF
.tiff / .tif files. Multipage TIFFs are accepted, and batch upload is supported.TIFF (Tagged Image File Format) was introduced by Aldus in 1986 as a flexible container for high-fidelity raster images, and it remains the standard for scanned documents, microscopy, geospatial imagery, professional photography, and print archives. A single .tif file can hold one image or hundreds — the spec calls each page a "subfile," a design originally aimed at multipage faxes that today is heavily used for medical slides, satellite tiles, and book scans. The problem: almost nothing in 2026 plays a .tif natively. Browsers don't render it (Chrome and Firefox lack a decoder), iOS Photos won't open a multipage file, and uploading a 200 MB TIFF burst to social media is a non-starter. Encoding the same frames as MP4 produces something every device plays and every platform accepts.
| Property | TIFF | MP4 (H.264) |
|---|---|---|
| Container year | 1986 (Aldus) | 2003 (ISO/IEC 14496-14) |
| Type | Still image (or multi-frame still) | Video container |
| Multipage support | Yes, native "subfiles" | Yes, as video frames |
| Typical size per frame | 5-50 MB (uncompressed) | 50-500 KB (H.264) |
| Color depth | 1, 8, 16, 32-bit per channel | 8-bit (10-bit with HEVC) |
| Max file size | ~4 GiB classic / 18 EB BigTIFF | 2^64 bytes per ISO base |
| Browser playback | No (Chrome/Firefox lack decoder) | Yes (~96% global support) |
| Audio | No | Yes (AAC by default) |
| Lossless option | Yes (LZW, ZIP, no compression) | Yes (with H.264 lossless profile) |
| Best for | Archival, print, scanning | Distribution, streaming, playback |
| Duration setting | Effective FPS | Typical use |
|---|---|---|
| 1/60s per frame | 60 fps | Smooth scientific time-lapse, high-FPS slow-mo source |
| 1/30s per frame | 30 fps | Standard web/streaming output |
| 1/24s per frame | 24 fps | Cinematic feel (film standard) |
| 0.5s per frame | 2 fps | Slow scroll through scanned pages |
| 2 seconds per frame | 0.5 fps | Photo slideshow pacing |
| 5 seconds per frame (default) | 0.2 fps | Brochure pages, document review |
| 10 seconds per frame | 0.1 fps | Long-dwell reading or inspection |
Yes. When the converter detects a multipage .tif, every subfile (page) is rendered as a frame in the output video in document order. Combined with the Merge images strategy across multiple uploaded files, you can render a single 50-page scan plus three more files as one continuous MP4. If you'd rather keep each source file separate, switch to Video per image to get one output video per input TIFF.
MP4 with H.264 video (the default). H.264 has roughly 96% global browser support per caniuse data, plays natively in Safari, Chrome, Edge, Firefox, iOS, Android, smart TVs, and basically every editor since 2010. Pick MOV if the deliverable is for Final Cut or QuickTime workflows, MKV if you need subtitle tracks, WebM (VP9) for open-source web embedding, and HEVC/H.265 only when you control the playback target — H.265 is patent-encumbered and not universally supported in browsers.
That's the Background Color filling letterbox areas when your TIFF aspect ratio doesn't match the output resolution. A portrait-oriented scanned page rendered into a 1920x1080 landscape frame will get vertical black bars by default. Switch Background Color to White for scanned documents, or set a custom resolution that matches your TIFF aspect ratio (e.g. for an A4 portrait scan, render at 1080x1527 instead of 1080p).
Set Duration to 1/24s (single frame at 24fps). Each TIFF becomes a single frame at 24 fps — useful for stop-motion sequences, time-lapses, or astrophotography stacks. For a more conventional document slideshow where each page should be read, pick 2-5 seconds per frame instead; the player will sit on each frame for that long before advancing.
The classic TIFF spec uses 32-bit offsets, capping files near 4 GiB. BigTIFF (released December 2011) uses 64-bit offsets and scales to 18 exabytes — common in geospatial (OME-TIFF, GeoTIFF) and pathology imaging. Server-side processing is constrained by available RAM, so a multi-gigabyte BigTIFF may exceed our server's memory budget. If you hit issues, split the file with a tool like libtiff's tiffsplit and convert in chunks.
No. TIFF is a still-image format with no audio track, so the output MP4 has video only. If you need a soundtrack, convert the TIFF to MP4 here first, then mux in audio with a separate tool such as MOV to MP4 for re-wrapping or a desktop editor like DaVinci Resolve / Shotcut.
Not in this converter — every frame switches at the duration you set, with no crossfade. For transition effects between images, render the MP4 here at one frame per image (1/24s or 1/30s), then import the resulting clip into a video editor and apply fades there. Alternatively, render at 5+ seconds per frame and let your video player handle pacing.
Most TIFFs use AdobeRGB or ProPhoto color spaces, while MP4 video (H.264) defaults to BT.709 (Rec.709) for HD content. The converter remaps colors during encoding, which compresses the wider gamut. For color-critical work, export your TIFF to sRGB first in Photoshop or GIMP, then convert. Also note H.264 is 8-bit per channel by default — if your TIFF is 16-bit, banding may appear in gradients.
processing happens on our servers, so the practical limit is upload size and connection speed. Most desktop browsers comfortably handle individual TIFFs up to a few hundred MB and total batches up to about 2 GB. For larger inputs — long scientific time-lapses, full GeoTIFF tiles — split into batches or use the Video Compressor on the output if the resulting MP4 is too big for upload.