Why TIFF Has So Many Compression Options
TIFF (Tagged Image File Format) was designed in 1986 as a flexible container. Multiple compression methods coexist because TIFF was meant to handle any image type: scanned text, photography, graphics, fax, geospatial. Different compression suits different content.
In 2026, six compression methods are commonly used:
- None: uncompressed, maximum size, universal compatibility
- PackBits: simple RLE, common on Mac
- LZW: Lempel-Ziv-Welch, lossless, broad support
- ZIP (Deflate): similar to LZW, slightly better compression
- JPEG: lossy compression for photographs in TIFF
- JPEG 2000: lossless or lossy, less common
This post covers when to use each, the file size and compatibility trade-offs, and the conversion workflows. For broader TIFF context, see TIFF vs DNG vs PSD.
Size and Quality Comparison
For a 4000×3000 16-bit RGB photograph:
| Compression | File size | Lossless | Compatibility |
|---|---|---|---|
| Uncompressed | 72 MB | Yes | Universal |
| PackBits | 65 MB | Yes | Mac, mostly Windows |
| LZW | 38 MB | Yes | Most modern tools |
| ZIP (Deflate) | 36 MB | Yes | Most modern tools |
| JPEG (quality 85) | 4 MB | No | Limited TIFF support |
| JPEG 2000 lossless | 32 MB | Yes | Limited |
| JPEG 2000 lossy | 1.5 MB | No | Very limited |
For most lossless work: LZW or ZIP. For maximum compatibility: uncompressed. For lossy where size matters: JPEG-in-TIFF (but consider native JPG instead).
When to Use Each
Uncompressed when:
- Maximum compatibility is critical (legacy software)
- Speed of read/write matters more than file size
- Storage is unlimited
- Print services that may not handle compressed TIFF
LZW when:
- Standard archival workflow
- Industry default for many image libraries
- Good balance of size, speed, compatibility
ZIP (Deflate) when:
- Slightly smaller than LZW
- Newer tools (modern Photoshop, ImageMagick)
- Same use cases as LZW
JPEG-in-TIFF when:
- You need TIFF container but don't need lossless
- File size is the primary constraint
- Use case where TIFF wrapper matters more than content
For most scenarios in 2026: LZW or ZIP. Uncompressed only when compatibility demands it.
Compression Method Details
PackBits: simple run-length encoding. Effective for images with large solid-color areas. Limited compression on photographs (often only 5-10% reduction).
LZW: dictionary-based compression. Works on most content. Industry default since 1990s for TIFF.
ZIP (Deflate): same algorithm as ZIP archives and PNG. Slightly better compression than LZW (5-10% smaller files). Slower to encode/decode.
JPEG-in-TIFF: standard JPEG compression but wrapped in TIFF container. Provides JPG compression with TIFF metadata flexibility.
Compatibility Matrix
| Tool | Uncompressed | LZW | ZIP | JPEG | JP2 |
|---|---|---|---|---|---|
| Photoshop | Yes | Yes | Yes | Yes | Limited |
| GIMP | Yes | Yes | Yes | Yes | Yes |
| ImageMagick | Yes | Yes | Yes | Yes | Yes |
| LightRoom | Yes | Yes | Yes | Yes | Yes |
| Affinity Photo | Yes | Yes | Yes | Yes | Limited |
| macOS Preview | Yes | Yes | Yes | Yes | Yes |
| Windows Photos | Yes | Yes | Yes | Yes | No |
| Print services | Yes (always) | Mostly | Mostly | Limited | Rare |
| Web browsers | No (TIFF not native) | No | No | No | No |
For print and professional use: uncompressed or LZW is safest. ZIP is the modern alternative. JPEG and JPEG 2000 in TIFF are niche.
Encoding Examples
For converting to LZW-compressed TIFF:
# ImageMagick
convert input.tif -compress lzw output_lzw.tif
# GraphicsMagick
gm convert input.tif -compress lzw output_lzw.tif
For ZIP compression:
convert input.tif -compress zip output_zip.tif
For JPEG-in-TIFF:
convert input.tif -compress jpeg -quality 85 output_jpeg.tif
For batch processing:
for f in *.tif; do
convert "$f" -compress lzw "compressed/${f}"
done
For batch automation, see Batch Processing Files Guide.
File Size in Production
For a typical photo library (1000 16-bit RGB images at 6000×4000):
| Compression | Total storage |
|---|---|
| Uncompressed | 144 GB |
| PackBits | 130 GB |
| LZW | 76 GB |
| ZIP | 72 GB |
| JPEG quality 90 | 18 GB |
For long-term archival of 10,000+ images: LZW or ZIP saves 50% storage with no quality loss. For multiplied scale, the savings matter.
Bit Depth Effects
Compression efficiency varies by bit depth:
| Bit depth | LZW reduction |
|---|---|
| 1-bit (B&W) | 80% (very effective) |
| 8-bit grayscale | 40% (moderate) |
| 8-bit RGB | 35% |
| 16-bit RGB | 50% (more reducible due to high-bit data patterns) |
| 32-bit float | 30% |
LZW is more effective on higher-bit-depth data because there's more redundancy to exploit. For 16-bit photo masters: LZW is highly recommended.
Predictor Options
Both LZW and ZIP support a "predictor" option that improves compression on photographic data:
# Standard LZW
convert input.tif -compress lzw output.tif # ~38 MB
# LZW with predictor
convert input.tif -compress lzw -define tiff:predictor=2 output.tif # ~30 MB
The predictor encodes pixel differences instead of absolute values. Photographic content (gradient skies, smooth surfaces) compresses 15-25% better with predictor enabled.
For Photoshop output: enable in Image > Mode > Save Options > Compression > LZW > Predictor.
For our image converter, TIFF compression options are exposed.
Multipage TIFF
TIFF supports multiple pages in one file (used for fax archives, scanned documents):
# Combine multiple TIFFs into one multi-page TIFF
convert page_*.tif -compress lzw output_multipage.tif
For document archives: multipage TIFF is convenient. Each page can have different compression (text pages with PackBits, photo pages with LZW).
Common Issues
Tool reports TIFF corrupted: encoding mismatch. Some older tools don't support ZIP-in-TIFF. Convert to LZW instead.
File size larger after compression: highly random data (already-compressed JPGs, encrypted data) doesn't compress further. Skip compression in these cases.
Slow read/write performance: ZIP is slower than LZW. For frequently-accessed files: LZW. For archival: ZIP slightly smaller.
Color shift after JPEG-in-TIFF: JPEG is lossy. Don't use for color-critical work.
Multi-page support inconsistent: some viewers show only the first page. Test with target viewer.
For background on TIFF in cinema, see DPX Cinema Scanning Format.
Frequently Asked Questions
Should I always compress TIFFs?
For modern workflows: yes, with LZW or ZIP. Storage savings are significant. Lossless compression has no quality cost.
What about CCITT compression?
CCITT (Group 3 / Group 4) is for 1-bit B&W images, originally for fax. Compression is dramatic (90%+) for line art. Use only for B&W content.
Can I convert JPEG to TIFF without quality loss?
The JPEG decoding is fixed (information already lost). The TIFF encoding is lossless. So you preserve what's in the JPEG without further loss, but can't recover what JPEG threw away.
Is JPEG 2000 better than JPEG?
For lossless: JP2 is much better (smaller files at same quality). For lossy: JP2 is slightly better, but compatibility is poor.
Does TIFF support transparency?
Yes. 4-channel RGBA TIFF supports per-pixel alpha. PNG is more universal for transparency-heavy work.
What about WebP or AVIF inside TIFF?
Not supported in standard TIFF. WebP and AVIF have their own native containers; no need for TIFF wrapping.
Related Reading
Bottom Line
For TIFF compression in 2026: LZW for industry-standard archival, ZIP for slightly better compression with modern tools, JPEG-in-TIFF only when size matters more than quality. Add predictor for photographic content. Uncompressed only when compatibility demands. Our image converter handles TIFF compression options.



