TIFF — Aldus and Adobe Extensible Raster Format for Print and Archival

2026-05-2313 min read
TIFFAdoberasterlosslessmulti-pageprintarchivalBigTIFF

TIFF (Tagged Image File Format) is the "older sibling" of GeoTIFF: a container with a flexible tag-based architecture, born in 1986 at Aldus Corporation for desktop publishing and scanning needs, then inherited by Adobe in 1994 after the acquisition. Over four decades TIFF became the universal lingua franca for raster graphics that demand quality, lossless compression, multi-page capability, and long-term archival: from medical imaging and archival document scans to offset print prepress. If PNG lives on the web, JPEG in smartphones and social media, and GeoTIFF in GIS systems, then plain TIFF without geospatial tags is the format of print shops, libraries, museums, and medical labs. And it's exactly this extensibility that spawned a family of derived standards: GeoTIFF, BigTIFF, TIFF/EP, TIFF/IT.

Map generation of Amsterdam city center
Berlin Mitte, TIFF from osm2cdr.ru, opened in Adobe Photoshop. LZW compression, 300 dpi, 8-bit RGB — standard prepress configuration.

History: Aldus 1986 → Adobe 1994 → TIFF 6.0 → BigTIFF

TIFF's story began in the mid-1980s in Seattle, at a small company called Aldus Corporation, run by Paul Brainerd — the man who coined the term "desktop publishing." Aldus made PageMaker, the program that turned the personal computer into a layout tool for print. And it needed a raster format that scanners from different vendors could write to and that PageMaker could read from. The first TIFF specification shipped in 1986, developed jointly with scanner companies — Microtek, Hewlett-Packard, Xerox. The tag-based architecture idea was revolutionary: instead of a rigid header structure with fixed fields, TIFF proposed an extensible "tag-value" dictionary where any vendor could add metadata without breaking compatibility.

By 1992 the TIFF 6.0 specification shipped — the last major official revision of the format from Aldus. It locked in JPEG-in-TIFF compression, CMYK colorspace for prepress, YCbCr for video, and a host of other capabilities. TIFF 6.0 remains the canonical version to this day: everything that came later is either an informal extension (BigTIFF, GeoTIFF) or an industry subset (TIFF/EP for cameras, TIFF/IT for print).

In 1994 Adobe Systems acquired Aldus, and TIFF, alongside PageMaker, moved under Adobe's stewardship. Adobe publishes the TIFF 6.0 spec as part of its open standards portfolio, alongside PostScript and PDF. No royalty is required for using TIFF — one of the reasons the format took root in industrial applications where licensing risk is unacceptable.

After that the story branches into a series of extensions. In 1995 Niles Ritter at NASA/JPL proposed GeoTIFF — an extension with geospatial tags (covered in our GeoTIFF deep-dive). In 2004, around the problem of TIFF's 4 GB limit (32-bit offsets), Even Rouault and the GDAL team invented BigTIFF — a format with 64-bit offsets and magic number 0x002B instead of 0x002A. In 2001 DCF/EXIF took TIFF as the base for metadata in camera RAW files. And in the 2010s, COG (Cloud Optimized GeoTIFF) formalized TIFF for cloud streaming.

Inside TIFF: IFD, tags, data types, compression

A TIFF file consists of three logical pieces: an 8-byte header, one or more Image File Directories (IFD), and pixel data. The header begins with a byte-order marker — II (little-endian, Intel) or MM (big-endian, Motorola) — followed by a magic number: 42 for classic TIFF, 43 for BigTIFF. Then an offset to the first IFD.

The IFD is the heart of the format. It's a table of entries shaped like "tag number, data type, value count, value or offset." Each entry describes one image attribute: dimensions, bit depth, compression type, pixel data location, resolution, ICC profile, EXIF metadata. The base TIFF 6.0 tag set has about 70 standard positions:

  • ImageWidth (256) — width in pixels.
  • ImageLength (257) — height in pixels.
  • BitsPerSample (258) — bit depth per channel (1, 2, 4, 8, 16, 32).
  • Compression (259) — compression algorithm: 1 (none), 5 (LZW), 7 (JPEG new), 8 (Deflate/ZIP), 32773 (PackBits).
  • PhotometricInterpretation (262) — color model: 0/1 (grayscale), 2 (RGB), 3 (palette), 5 (CMYK), 6 (YCbCr).
  • StripOffsets (273) / TileOffsets (324) — where pixel data sits in the file (rows or tiles).
  • SamplesPerPixel (277) — channels per pixel.
  • XResolution / YResolution (282/283) — resolution in DPI.
  • ICCProfile (34675) — embedded ICC profile for color management.

The most interesting TIFF feature is multi-image support in one file via a chain of IFDs. Each IFD ends with a "next IFD offset" field (or 0 for the last one). That's multi-page TIFF: one file can hold hundreds of scanned document pages, each with its own resolution, size, compression. That's exactly why archival libraries and medical labs chose TIFF: the entire patient examination history or an entire archival volume sits in one self-contained file.

Compression in TIFF is diverse. LZW (Lempel-Ziv-Welch) is the most popular lossless option for line-art, maps, text scans. Deflate (the same algorithm as ZIP and PNG) is the modern alternative, slightly more efficient on large images. PackBits is a simple RLE inherited from Mac. CCITT Group 3/4 is special compression for black-and-white scans (fax) giving fantastic compactness on text documents. JPEG-in-TIFF is lossy compression for photo-style imagery within a TIFF container. LZMA and Zstd are modern high-efficiency algorithms in recent GDAL/libtiff.

Use cases: where TIFF without geo tags is irreplaceable

Prepress for offset print. Any high-quality print — magazines, books, posters, packaging — goes through TIFF. Three reasons: CMYK colorspace support (which PNG and base JPEG lack), lossless compression that preserves subtle gradients through repeated editing, and embedded ICC profiles for predictable color reproduction on print equipment. The designer saves raster elements as TIFF, lays out in InDesign, and the print shop receives files with guaranteed color match.

Archival scanning of documents and books. National libraries (Library of Congress, Russian State Library, British Library) store scanned rarities in TIFF. It's the archival-quality format: lossless, supports 16-bit depth for subtle halftones, multi-page for entire volumes, and free from patent or licensing risk. ISO 19005 (PDF/A) allows embedded TIFF as a container for raster pages.

Medical imaging. While DICOM is formally separate, many modalities (microscopy, histology, fluorography, dermatoscopy) export images as multi-page TIFF. ImageJ — the main tool for biological imaging — works with TIFF natively, including multi-channel stacks (Z-stack, time-lapse, multi-channel fluorescence). A pathologist or cytologist opens one TIFF file and sees 200 section slides of one sample.

Art reproductions and museum archives. A digital copy of a museum painting, tapestry, or medieval manuscript page is always 16-bit TIFF. Lossless, wide color gamut, ICC profile for calibration against a museum monitor. Adobe Photoshop, GIMP, and Krita natively save layers inside TIFF (via the Adobe Layers tag extension).

Map design for print shops. And here TIFF intersects with our world. When a city administration orders a print run of paper tourist maps for a district or plans outdoor advertising with a raster image of the territory, the print shop demands TIFF — not GeoTIFF, not PNG, not JPEG. The map gets exported via OSM2CDR into TIFF at 300 dpi resolution, needed CMYK profile, and LZW compression.

Map generation of Samara city center
Dubai Burj Khalifa, TIFF in GIMP. 300 dpi, RGB 8-bit, LZW lossless — standard config for tourist board print materials.

TIFF vs GeoTIFF vs PNG vs JPEG

Parameter TIFF GeoTIFF PNG JPEG
CRS embedded No Yes No No
Multi-page Yes Yes No No (MPO only)
CMYK Yes Yes No Yes
Lossless Yes (LZW/Deflate) Yes Yes No
16/32-bit depth Yes Yes 16-bit No
Browser support No No Native Native
BigTIFF (>4 GB) Yes Yes No No
Layers Adobe ext. Adobe ext. No No
Typical 1 km² 15–80 MB 15–80 MB 5–40 MB 0.5–4 MB

Pick TIFF when you need archival-grade quality without georeferencing — for print, museum storage, medical imaging. GeoTIFF is the same TIFF plus six geospatial tags, needed in GIS work. PNG for the web and illustrations when CMYK and multi-page aren't required. JPEG for photos and rapid distribution at the cost of quality loss across resaves.

A critical detail: any program that reads GeoTIFF reads plain TIFF too. And vice versa: a classic TIFF viewer (Photoshop, IrfanView) opens GeoTIFF and just ignores the geospatial tags, showing the image without CRS. That's the essence of TIFF's extensible architecture: extensions don't break compatibility.

BigTIFF: breaking the 4 GB barrier

Classic TIFF uses 32-bit offsets for data locations inside the file, capping total size at four gigabytes. For most tasks that's enough: even a 600 dpi A3 archival book scan rarely exceeds 200 MB per page. But in specialized domains the limit becomes a serious problem:

  • Microscopy. A digital pathology scanner outputs a 100,000 × 100,000 pixel section image — tens of gigabytes.
  • Large geographic coverage. A map of Moscow or all of Russia at 600 dpi runs into the billions of pixels.
  • Aerial and satellite imagery. A high-resolution Sentinel-2 scene can exceed 4 GB.

BigTIFF, developed in the GDAL/libtiff project in 2004, solves this via 64-bit offsets. Technically it's a different format: magic number 43 in the header instead of 42, distinct signature. But logically and by tags — the same TIFF. Modern programs (GDAL 2.4+, QGIS 3.x, ImageMagick 7+, libtiff 4.0+) handle BigTIFF transparently. Older Photoshop versions (pre-CC 2014) or IrfanView-class viewers may fail to open BigTIFF — then a fallback to classic TIFF or a move to more modern software is needed.

OSM2CDR automatically switches to BigTIFF on TIFF export when the estimated output file exceeds 3.5 GB. This is rare — typically only when ordering a major city map at 600 dpi.

Workflow in OSM2CDR: TIFF for print prepress

Our tiff_exporter.py is a simplified version of geotiff_exporter.py: the same QGIS layout rendering pipeline, same DPI/size/style support, but WITHOUT writing geospatial tags to the output file. You get a plain TIFF that prepress systems (Adobe InDesign, QuarkXPress, print shop RIPs) treat as a standard raster image with no geographic specificity.

Step 1. On osm2cdr.ru pick TIFF in the format list (Raster category, next to GeoTIFF). Note: if the map is for GIS analysis in QGIS/ArcGIS, pick GeoTIFF. For print, presentation, museum archive — pick TIFF.

Step 2. Draw the export area. Remember: file size grows quadratically with area and linearly with DPI. A 1×1 km district at 300 dpi is around 50 MB; the same area at 600 dpi is around 200 MB.

Step 3. Pick DPI. For offset or digital print — 300 DPI is standard. For large-format print (posters, banners) — 150 DPI is enough at typical viewing distance. For web or slides — 96-150 DPI. For archival quality — 600 DPI.

Step 4. Pick the cartographic style. For print we recommend contrast (bright borders, good on paper) or standard (classic OSM colors). For special needs — monochrome for technical basemaps or night for dark themes.

Step 5. Click Export. Rendering takes 30-120 seconds depending on size and DPI. Download the .tif file — open in Adobe Photoshop, GIMP, any image viewer.

Step 6. Before sending to the print shop, convert to CMYK if needed (Image → Mode → CMYK Color in Photoshop) and embed the print shop's ICC profile. Our exporter outputs RGB by default because the final ICC profile depends on the specific print shop equipment and is best applied locally.

Get a TIFF Map of the District in 90 Seconds

Map generation of Nizhny Novgorod city center
Manhattan, TIFF at 600 dpi for a city guidebook print order. IrfanView confirms 8-bit RGB, LZW lossless.

Software that opens TIFF

Adobe Photoshop ($23/month subscription, Windows/macOS) — the industry standard for editing TIFF. Supports 32-bit depth, CMYK, ICC profiles, layers inside TIFF, multi-page via File → Open → Page Index.

GIMP (free, GPL, cross-platform) — open-source Photoshop alternative. Reads and writes TIFF completely including LZW, Deflate, multi-page. CMYK support is limited (via the Separate+ plugin).

ImageJ / Fiji (free, public domain, Java) — the main tool for biological and medical imaging. Opens multi-page TIFF as a stack, supports hyperstacks (Z-time-channel). imagej.net/software/fiji

IrfanView (free for personal use, Windows) — lightweight fast viewer, opens every TIFF variant including BigTIFF and multi-page. Good for quick previews of large files.

Preview on macOS (built-in) — opens single-page TIFF without compression and with LZW. May struggle with BigTIFF and rare compression schemes.

GDAL / libtiff (free, MIT) — the base C libraries and CLI. tiffinfo file.tif shows all tags, tiffcp copies/converts.

Pillow (Python, MIT) — the standard Python tool for TIFF in scripts. Image.open("file.tif") to read, image.save("out.tif", format="TIFF", compression="lzw") to write.

FAQ

How is TIFF different from GeoTIFF? GeoTIFF is regular TIFF with six additional tags describing the coordinate system. Any TIFF viewer opens GeoTIFF as a regular image, ignoring geo tags. And vice versa: a GIS program opens TIFF without geo tags as an image without CRS.

Can I use TIFF on a website? Technically yes, but browsers don't render it natively. In practice for the web you always convert to PNG (lossless, supports transparency) or JPEG (lossy, for photos). TIFF on a site is a redundant download for the user.

Why multi-page TIFF in 2026 when PDF exists? Multi-page TIFF is simpler and lighter than PDF: pure raster with no layers, fonts, or scripts. The scanning standard for archival documents and medical imaging is exactly TIFF, not PDF. TIFF also opens faster, doesn't depend on font rendering, and is always bit-for-bit reproducible.

Which compression to pick for TIFF? LZW — the standard safe choice, reads everywhere. Deflate — for modern software, slightly more efficient. JPEG-in-TIFF — photo-style only, not for line art. No compression — maximally compatible but huge size.

What's BigTIFF and do I need it? BigTIFF is TIFF with 64-bit offsets, removing the 4 GB classic limit. Needed only for huge maps (>4 GB): cities at 600 dpi, microscopic scans, gigapixel panoramas. Most modern software supports it.

Conclusion

TIFF is the format that has quietly served the industries where quality and long-term storage matter more than file size and web distribution for forty years. Print, libraries, museums, medicine, science — anywhere a raster image must live for decades without loss and stay compatible across dozens of software generations, TIFF is the choice. The extensible tag-based architecture has spawned a family of derived standards: GeoTIFF for GIS, COG for the cloud, BigTIFF for large files, TIFF/EP for cameras, TIFF/IT for prepress. If your OSM map heads to the print shop, archive, or museum — export it as TIFF on osm2cdr.ru, not PNG or JPEG. It's the right technical choice for print prepress and archival storage.

Sources

← All articles