Multi-Page TIFF Limitations When Converting to PNG

One container, different models

A multi-page TIFF can store a scan sequence in separate image file directories. The Library of Congress format description notes multi-page support. A standard still PNG has one main image; it is not a document container equivalent.

PixelConvert currently decodes the first TIFF frame and writes one PNG. It does not concatenate pages, create numbered files for every frame, or produce a PDF. The converter page and preparation response disclose the first-frame behavior.

The structural difference is worth making concrete. A TIFF file is organised as a chain of directories, each describing one image with its own dimensions, colour model, compression, and tags. A reader follows the chain from one to the next. Three scanned pages in a TIFF are three complete images in one file, not one tall image and not three files.

PNG has no equivalent chain. The format defines a single image, and while it has extensions for animation, those describe frames of a moving image rather than pages of a document. There is no arrangement of PNG features that faithfully represents a three-page scan as one file.

Why this surprises people

TIFF is unusual among image formats in that most people meet it through scanners and fax systems rather than through cameras or the web. A flatbed scanner set to scan a ten-page document into one file produces a multi-page TIFF, and the resulting file looks like a document in every way that matters to the person who made it.

So when that file is converted to PNG and a single page comes out, it reads as data loss or as a bug. It is neither — it is the honest consequence of moving from a container that holds many images to one that holds a single image. The alternative behaviours a converter could choose are all worse if they happen silently: producing only page one without saying so, stitching the pages into one very tall image, or emitting a ZIP when the user asked for a file.

PixelConvert takes the position that the limitation should be stated before conversion rather than discovered afterwards. The converter page names the first-frame policy, and the response reports it. That is less convenient than a tool that appears to handle everything, and considerably less annoying than discovering nine missing pages later.

What else may not map

TIFF compression can be lossless or lossy, and files may include profiles, tags, unusual bit depths, or print-oriented color spaces. A web-friendly PNG derivative may not preserve every TIFF tag or the same print interpretation.

Colour model is the most consequential of these. TIFF is widely used in print workflows where images are stored as CMYK — four ink channels rather than three light channels. PNG has no CMYK mode. Converting a CMYK TIFF to PNG requires converting the colour into RGB, and that conversion is an approximation: the two models do not cover identical ranges of colour, so some values have no exact equivalent. For a proof, a press check, or anything colour-critical, the TIFF is the file that matters.

Bit depth is the second. Scientific, medical, and high-end photographic TIFFs may store 16 or 32 bits per channel, giving far more tonal gradation than the 8 bits per channel typical of web images. PNG does support 16-bit channels, but many downstream tools do not, and a conversion that reduces to 8 bits discards tonal information permanently.

Orientation is applied before output. Metadata is not copied into Upload-Ready derivatives. Preserve the original TIFF when it is a scan master, print asset, or archival record.

Getting every page

When you genuinely need all the pages, the right tool depends on what you intend to do with them.

If the goal is a readable, shareable document, convert to PDF rather than to images. A PDF is a document container: it holds multiple pages natively, it is universally readable, it can be searched if text recognition is applied, and it stays one file. Most operating systems and many scanner utilities can produce a PDF from a multi-page TIFF directly. This is the right answer far more often than people expect, because the underlying need is usually 'send someone this document', not 'obtain image files'.

If the goal is genuinely separate images — extracting figures, editing individual pages, feeding pages into another process — use software that enumerates frames explicitly. Desktop image editors, document management tools, and command-line utilities such as ImageMagick can list the frame count and export each one as a numbered file. Doing it explicitly also lets you confirm the page count before you start, which is worth knowing.

Check the page count first either way. A TIFF that you believe has three pages and actually has four is a common and quiet failure, especially with files produced by fax gateways or older scanners.

Choose a workflow intentionally

Use TIFF-to-PNG when you need a broadly usable image of the first page. For every page, use document or imaging software that lets you inspect the page count and export each frame explicitly. For a reading document, PDF may be more appropriate than multiple PNG files.

After conversion, compare dimensions, color, and visible page content. Do not delete the source based only on a successful download.

That last sentence is the one that costs people real work when ignored. A scan is frequently the only copy of a physical document that no longer exists or is no longer accessible. A print master represents someone's paid time. Both are exactly the kind of file that should be archived rather than replaced by a derivative made for one immediate purpose. Storage is cheap; rescanning is not, and sometimes it is impossible.

When TIFF is the right format to keep

TIFF persists in professional use for reasons that remain valid. It is lossless, so repeated opening and saving does not degrade the image. It handles CMYK and high bit depths that consumer formats do not. It carries extensive metadata tags. It has been stable for decades, which matters enormously for archival collections that must remain readable long after any particular application has gone.

Those properties make it a good master format and a poor delivery format. It is large, it is not displayed by web browsers, and many everyday applications handle it awkwardly or not at all. The sensible arrangement is the one that applies to every master-and-derivative relationship: archive the TIFF, generate a PNG or JPG when you need to show someone something, and never confuse the two roles.

If you are choosing a format for a new scanning project, TIFF for the archival master and PDF for the readable document is a combination that will still make sense in twenty years.