Initializing... drag & drop files here
Supports: TIFF, TIF
TIFF (Tagged Image File Format, released by Aldus in 1986) is the workhorse of scanning, archival, and pre-press — it stores lossless 16-bit-per-channel pixel data, multiple pages in a single file, and rich metadata. GIF (released by CompuServe on June 15, 1987) is the opposite: indexed 8-bit color (max 256 colors), LZW lossless compression, and native looping animation. The conversion is almost always about shrinking a heavy archival asset into something a browser, Slack thread, or email client can render inline — and when the TIFF has multiple pages, each page becomes one frame of an animated GIF.
<img> tags; Safari does on macOS but not on iOS. Converting to GIF removes that compatibility problem entirely.| Property | TIFF | GIF |
|---|---|---|
| Released | 1986 (Aldus, now Adobe) | June 15, 1987 (CompuServe) |
| Color depth | Up to 16 bits per channel (48-bit RGB) | 8-bit indexed, max 256 colors per frame |
| Compression | LZW, ZIP, PackBits, JPEG, or uncompressed | LZW lossless, indexed |
| Animation | Multi-page via IFDs (no native timing) | Native looping with per-frame delay |
| Transparency | Full 8-bit alpha channel | 1-bit (on/off) per pixel |
| Typical file size | 5-100+ MB for a single high-res image | 50 KB - 2 MB for typical web GIFs |
| Browser support | None natively in Chrome/Firefox/Edge; Safari macOS only | Universal since the mid-1990s |
| Best for | Print masters, scanned archives, scientific imaging | Looping web animations, lightweight previews, reactions |
| Setting | Pick for flat graphics | Pick for photo / continuous tone | Pick for scanned text |
|---|---|---|---|
| Colors palette | 32-64 (smaller file) | 256 with dither | 16 (B/W) or 64 (grayscale) |
| Framerate | N/A for stills | 10 FPS (recommended) | 2-5 FPS (slideshow) |
| Image Quality | 60-80% | 80-90% | 70-80% |
| Resolution preset | Keep original or 720p | 1080p or 720p | Keep original |
| Expected size (single frame, 1080p) | 50-200 KB | 300 KB - 1.5 MB | 100-400 KB |
Yes — each Image File Directory (IFD) in the source TIFF is exported as one frame of the resulting GIF, in the order they appear in the file. The TIFF specification has no native per-frame delay, so all frames receive the same uniform delay derived from your Framerate setting (10 FPS = 100 ms per frame). If your TIFF is single-page, you get a static GIF.
GIF is an indexed-color format limited to a single 256-color palette per frame, while TIFF commonly stores 24-bit or 48-bit color. When a photograph or smooth gradient is reduced to 256 colors, you'll see banding in skies, skin tones, and shadow gradients. Turn dithering on in the Colors panel — it scatters the palette error as noise, which the eye reads as smoother gradation. For photographs you would generally do better converting to TIFF to WebP (24-bit color, animation supported) or TIFF to PNG for stills.
Single TIFF uploads up to several hundred MB are accepted; processing time scales with the page count and resolution of the source. Multi-page TIFFs with dozens of pages take longer because every IFD has to be decoded, palette-quantized, and re-encoded as a GIF frame.
Yes. xconvert writes the Netscape Application Extension block (NETSCAPE2.0) that the GIF format uses to indicate looping, and sets it to infinite loop by default. Every modern browser, Slack, Discord, and email client honors this. If your TIFF was a single page, looping is irrelevant — you get a static one-frame GIF.
Only partially. TIFF can store a full 8-bit alpha channel (256 levels of opacity), while GIF supports only 1-bit transparency — a pixel is either fully transparent or fully opaque. During conversion, partially-transparent TIFF pixels are flattened against a background color (white by default). For workflows that need smooth alpha, use TIFF to PNG or TIFF to WebP instead.
It can be, but multi-page TIFFs trip people up. A 50 MB TIFF with 20 high-resolution pages becomes a 20-frame animated GIF; each frame still has to encode unique pixel data, so file size adds up. To shrink further: drop the resolution preset to 720p or 480p, reduce the Colors palette from 256 to 64, lower Image Quality to 50-60%, or remove frames you don't need before uploading. You can also follow up with Compress GIF to drop more frames or downsize.
Standard TIFF files are capped at 4 GB by the 32-bit offset field; BigTIFF (used for GeoTIFF, slide-scanner output, and OME-TIFF microscopy) uses 64-bit offsets and can exceed that. xconvert handles standard TIFF reliably; BigTIFF up to several hundred MB is generally fine. For multi-gigabyte scientific files, downsample to a manageable size in QGIS, ImageJ, or Photoshop before uploading.
If your TIFF has fewer than ~30 frames and the content is graphic (line art, charts, scans), GIF is best for universal compatibility — it inlines in email, GitHub README files, and chat apps. If you have 60+ frames or photographic content, MP4 or WebM produces dramatically smaller files at the same visual quality because of inter-frame compression — GIF stores each frame independently and bloats fast.
No. Uploaded TIFFs and the resulting GIFs are processed in your session and deleted from our servers shortly after conversion completes. No accounts, no permanent storage, no third-party sharing.