Reference Formats
TIFF
A flexible, tag-based container supporting lossless (and select lossy) compression, high bit depths, and full EXIF/IPTC/XMP/ICC metadata — the de facto archival master format for scanned and photographic images.
Extension
.tif
Full name
Tagged Image File Format
Introduced
Autumn 1986 (Revision 3.0); final Revision 6.0 published 1992
Vendor
Originally Aldus Corporation; maintained by Adobe Systems since Aldus's 1994 merger
What is inside the container
TIFF's tag-based structure supports uncompressed storage plus lossless LZW, Deflate/ZIP, PackBits, and CCITT Group 3/4 compression, and via later extensions, lossy JPEG or JPEG 2000. Color support spans 1-bit bitonal through 48-bit RGB and CMYK. Because the EXIF spec itself is built on TIFF's tag structure, TIFF natively and reliably carries EXIF, IPTC-IIM, XMP, and ICC profiles per image file directory — the broadest and most robust metadata support of any format covered here, which is why it's the standard DAM preservation-master choice.
How to open it
For archives
Yes — TIFF is a defensible DAM archival master format. It is explicitly recognized by FADGI (the Federal Agencies Digital Guidelines Initiative, hosted by the Library of Congress) and used by libraries, museums, and government agencies as the preservation format for scanned and photographic masters, thanks to its lossless compression options, wide color-depth support, and full EXIF/IPTC/XMP/ICC metadata capacity.
TIFF was published by Aldus Corporation (maker of PageMaker) in autumn 1986 to solve a real mid-1980s mess: every scanner vendor was inventing its own incompatible bitmap format, and desktop publishing needed one common standard to rely on. Aldus merged into Adobe in 1994, which has maintained the spec — last fully revised as version 6.0 in 1992 — ever since. Its tag-based structure is what makes it so extensible: rather than a fixed layout, TIFF is a set of tagged fields that readers can selectively interpret, which is also why the EXIF standard was built directly on top of TIFF’s tag system.
This is the backbone of TIFF’s DAM role. It’s the default “preservation master” tier in most serious DAM implementations: ingest keeps the TIFF untouched while the system generates JPEG or WebP derivatives for web preview and thumbnails. Its rich tag structure is what lets a DAM reliably extract and index EXIF (camera data), IPTC (rights, captions, keywords), and XMP (editorial workflow state) — and unlike JPEG or PNG, TIFF can carry independent metadata per page in a multi-page document, and layered TIFFs (an Adobe/Photoshop-specific extension, not part of core TIFF 6.0) preserve editable structure similarly to PSD.
The recurring metadata pitfall in DAM systems is not absence but duplication: because EXIF, IPTC, and XMP can all coexist in the same TIFF, they can drift out of sync across resaves — stale IPTC captions next to updated XMP keywords is a known headache for metadata-management teams. Institutions like the U.S. Government Printing Office selected variants like TIFF_G4 specifically as bitonal preservation masters, underscoring TIFF’s institutional standing as an archival format, but a DAM still needs a clear policy for which metadata field wins when they conflict.
Frequently asked
Is TIFF a defensible DAM archival master format?
Yes. TIFF is explicitly recognized by FADGI (the Federal Agencies Digital Guidelines Initiative, hosted by the Library of Congress) and used by libraries, museums, and government agencies as the preservation format for scanned and photographic masters.
Does TIFF display natively in web browsers?
No — TIFF is not natively supported for inline display in any major browser, so a DAM must generate JPEG or WebP derivatives for web delivery.
What metadata does TIFF support?
TIFF natively and reliably carries EXIF, IPTC-IIM, XMP, and ICC profiles per image file directory — the broadest and most robust metadata support of any format in this comparison, since the EXIF spec itself is built on TIFF's tag structure.
What compression options does TIFF offer?
Uncompressed storage, lossless LZW, Deflate/ZIP, PackBits, and CCITT Group 3/4 compression, plus lossy JPEG or JPEG 2000 via later extensions.
Can TIFF metadata conflict across resaves?
Yes — because EXIF, IPTC, and XMP can all coexist in the same TIFF, they can drift out of sync across resaves, such as a stale IPTC caption sitting next to an updated XMP keyword list. A DAM needs a clear policy for which field wins.
Does TIFF support multi-page or layered content?
Yes — TIFF can carry independent metadata per page in a multi-page document, and layered TIFFs (an Adobe/Photoshop-specific extension, not part of core TIFF 6.0) preserve editable structure similarly to PSD.
What color depth does TIFF support?
1-bit bitonal through 48-bit RGB and CMYK.
What's the typical DAM ingest pattern for TIFF?
Ingest keeps the TIFF untouched as the preservation master while the system generates JPEG or WebP derivatives for web preview and thumbnails.
Sources
- TIFF Revision 3.0 was published by Aldus Corporation in autumn 1986; Revision 6.0, the final version, followed in 1992. checked 2026-08-07 — TIFF File Format Summary
- TIFF is recognized in FADGI's raster format comparison as a preservation-suitable master format. checked 2026-08-07 — FADGI Raster Format Comparison
- The Federal Agencies Digital Guidelines Initiative documents TIFF's role in digitization and preservation standards. checked 2026-08-07 — digitizationguidelines.gov