{"id":2959,"date":"2026-08-08T01:57:55","date_gmt":"2026-08-07T22:57:55","guid":{"rendered":"https:\/\/picajet.com\/articles\/formats\/multi-page-tiff\/"},"modified":"2026-08-08T02:05:47","modified_gmt":"2026-08-07T23:05:47","slug":"multi-page-tiff","status":"publish","type":"format","link":"https:\/\/picajet.com\/articles\/formats\/multi-page-tiff\/","title":{"rendered":"Multi-page TIFF"},"content":{"rendered":"

TIFF was never designed as a single-image-only format: its Image File Directory structure, present since Aldus’s original 1986 specification and carried through to the 1992 TIFF 6.0 baseline, links directories by file offset rather than assuming one image per file. That gave it, almost for free, the ability to hold an arbitrary sequence of images with independent compression and resolution settings each \u2014 a property the fax and document-imaging industry picked up on and formalized as the TIFF-F Class F profile in the late 1990s, standardized through the IETF as RFC 2301 and RFC 2306.<\/p>\n

Page content<\/th>Typical compression<\/th><\/tr><\/thead>
Bi-level scans \/ faxes<\/td>CCITT Group 3 or Group 4 (per the TIFF-F Class F profile)<\/td><\/tr>
Grayscale or color pages<\/td>LZW, or uncompressed<\/td><\/tr>
Mixed within one file<\/td>Legal \u2014 each IFD\/page can use a different scheme<\/td><\/tr><\/tbody><\/table><\/figure>

That heritage explains why multi-page TIFF still shows up heavily in scanned-document and records-management contexts rather than in photography: a document scanner with an automatic feeder produces one TIFF per multi-page document, each page bi-level and CCITT-compressed for a fraction of the size a grayscale scan would take, with a PageNumber tag recording each page’s position. For a DAM ingesting scanned contracts, legal files, or historical archives, this means the format itself is the page boundary \u2014 losing track of a document’s total page count or corrupting the IFD chain partway through silently truncates the record.<\/p>

The practical challenge for asset management is that multi-page TIFF support is inconsistent across tools in a way single-page TIFF isn’t: many web-facing image viewers and thumbnail generators render only the first page and give no indication that more exist, which can hide content from search or preview entirely. A DAM handling this format needs to actively enumerate and index every page as part of the same document asset, not just generate a thumbnail from page one and treat the rest as invisible.<\/p>","protected":false},"excerpt":{"rendered":"

Multi-page TIFF packs several images or scanned pages into one file as a chain of linked image directories, widely used for fax transmission, document scanning, and legal\/records archives.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"How does a single TIFF file hold multiple pages?","answer":"TIFF's structure links a chain of Image File Directories (IFDs) by file offset, with each IFD describing one page's image data, compression, and resolution independently. A reader walks the chain from the first IFD to the last to page through the document."},{"question":"Why do generic image viewers sometimes show only the first page of a multi-page TIFF?","answer":"Many lightweight viewers and thumbnail generators only parse the first IFD in the chain for speed, since that's sufficient for the common single-image TIFF case, and simply don't walk the rest of the directory chain to surface additional pages."},{"question":"What compression is typically used in multi-page TIFF scans?","answer":"Bi-level scanned documents commonly use CCITT Group 3 or Group 4 fax compression per the TIFF-F Class F profile; grayscale or color multi-page TIFFs more often use LZW or leave pages uncompressed, and different pages within one file can legally use different schemes."},{"question":"How can a DAM verify a multi-page TIFF hasn't lost pages during transfer or conversion?","answer":"By reading the IFD chain and comparing the resulting page count against the file's own PageNumber tag (which records total pages), and flagging any mismatch or broken offset link as a corrupted or truncated file rather than assuming a valid single-page TIFF."},{"question":"Is multi-page TIFF still relevant, or has it been fully replaced by PDF?","answer":"It remains common in scanning, fax, and records-management pipelines because many scanners and OCR\/document systems produce it natively as a lossless intermediate, even though PDF is usually the preferred format for final distribution and long-term access."},{"question":"Can different pages in one multi-page TIFF have different resolutions or color depths?","answer":"Yes \u2014 since each page is an independent IFD, one page could be scanned at 300 DPI bi-level while another is 600 DPI grayscale within the same file, which is technically valid but worth normalizing during archival processing for consistency."},{"question":"Should a DAM split multi-page TIFFs into individual page assets or keep them as one document?","answer":"Most records-management practice keeps the multi-page file as the single logical document asset (matching the source scan or fax) while still indexing and thumbnailing each page individually for search and preview, rather than breaking the file apart into separate assets."},{"question":"What's the risk of re-compressing a multi-page TIFF to save storage?","answer":"Bi-level CCITT-compressed scan pages are already near-optimally compressed for that content; converting them to a lossy scheme or downsampling can degrade text legibility, and blanket recompression across a mixed-compression file can also unintentionally alter pages that were fine as-is."}],"checked_date":"2026-08-07","sources":[{"statement":"TIFF Revision 6.0 was finalized by Aldus Corporation on June 3, 1992 as the format's long-standing baseline specification.","source_name":"Library of Congress \u2014 TIFF, Revision 6.0","url":"https:\/\/www.loc.gov\/preservation\/digital\/formats\/fdd\/fdd000022.shtml","checked":"2026-08-07"},{"statement":"TIFF-F specifies multi-page documents (NewSubfileType = 2) as the standard case for fax file exchange, with a PageNumber field recording page number and total page count.","source_name":"IETF RFC 2306 \u2014 Tag Image File Format (TIFF) \u2014 F Profile for Facsimile","url":"https:\/\/www.rfc-editor.org\/rfc\/rfc2306.html","checked":"2026-08-07"},{"statement":"TIFF is well suited to facsimile documents because it natively supports multi-page raster images.","source_name":"IETF RFC 3949 \u2014 File Format for Internet Fax","url":"https:\/\/datatracker.ietf.org\/doc\/html\/rfc3949","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"ext":"tif","full_name":"Multi-page Tagged Image File Format","vendor_name":"Aldus Corporation \/ Adobe Systems (TIFF baseline); TIFF-F fax\/document profile standardized by the IETF as RFC 2306","introduced":"Multi-image capability is inherent to TIFF's original 1986\/1992 (TIFF 6.0) IFD-chain design; formalized for document and fax exchange as TIFF-F Class F in RFC 2301 (1998) and RFC 2306 (1998)","container_notes":"TIFF's core structure already supports multiple images per file: each page is its own Image File Directory (IFD) with its own compression, resolution, and bit depth, and the IFDs are linked in sequence by file offsets so a reader walks through them like a linked list. This made TIFF a natural fit for fax and scanned-document exchange, formalized as the TIFF-F Class F profile, which commonly pairs multi-page IFD chains with CCITT Group 3 or Group 4 bi-level fax compression and a PageNumber tag recording each page's position and the total page count.","open_with":[{"platform":"macOS","how":"Preview opens multi-page TIFFs and displays a page sidebar for navigation, similar to a PDF."},{"platform":"Windows","how":"Windows Photos and the legacy Windows Fax and Scan viewer both page through multi-frame TIFFs natively."},{"platform":"Cross-platform \/ power tools","how":"IrfanView and XnView browse and split multi-page TIFFs; ImageMagick's convert\/identify and libtiff-based utilities (tiffsplit, tiffcp) inspect and manipulate individual pages from the command line."},{"platform":"Document workflows","how":"Adobe Acrobat and most document-management\/OCR suites import multi-page TIFF directly, often converting it to searchable PDF."}],"archive_advice":"Keep the compression scheme documented per file, since a multi-page TIFF can legally mix CCITT Group 4, LZW, or uncompressed pages within the same page chain, and blind re-compression can silently degrade bi-level fax\/scan pages. Verify the IFD chain and page count on ingest \u2014 a truncated or corrupted offset chain can drop trailing pages without any obvious error in a preview \u2014 and prefer lossless CCITT Group 4 for bi-level scans and LZW for grayscale\/color pages. For long-term access alongside preservation, many archives also generate a parallel PDF\/A derivative, since multi-page TIFF viewers are less universal than PDF readers even though the TIFF remains the higher-fidelity master.","related":[2958,2960,2613,2601,2597,2600],"tool_link":""},"silo":[23],"class_list":["post-2959","format","type-format","status-publish","hentry","silo-formats"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2959","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/format"}],"version-history":[{"count":1,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2959\/revisions"}],"predecessor-version":[{"id":3294,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2959\/revisions\/3294"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=2959"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=2959"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}