How tiff2pdf.app converts TIFF to PDF without losing quality
This page is the evidence behind the claims on the TIFF to PDF converter: what happens to each kind of TIFF, how the converter is tested, where its limits are, and how you can check for yourself that your files stay on your device.
Updated
Why a TIFF can become a PDF without being compressed again
A TIFF holds each page as image data in one of several compressed forms. A PDF page holds image data too, and three of the forms PDF reads are forms TIFF uses: fax compression (CCITT Group 3 and Group 4), JPEG, and Flate, which TIFF calls Deflate or ZIP.
When a TIFF's data is already in one of those forms, the converter writes a PDF page around the same bytes. Nothing is decoded, so no pixel can change, the PDF is about the size of the TIFF, and a scan of several hundred megabytes converts without being loaded into memory. Every other TIFF is decoded and stored again with lossless compression.
What happens to each kind of TIFF
| What the TIFF holds | What the converter does | Do pixels change? |
|---|---|---|
| Fax compression (CCITT Group 3 or Group 4) in one strip | Copies the data unchanged | No |
| JPEG, 8-bit, in one strip or in several strips | Copies the data unchanged (several strips are joined into one JPEG) | No |
| Deflate (ZIP) in one strip | Copies the data unchanged | No |
| LZW, PackBits or uncompressed data; tiles; fax or Deflate data in several strips | Decodes it and stores it again without loss: black-and-white pages as Group 4, others with Flate | No |
| 16-bit grayscale or color, CMYK, palette color | Keeps the bit depth and the color model; carries over an embedded color profile | No |
| JPEG in tiles | Decodes it and stores the decoded pixels with Flate | No, but the PDF is about 4 times the size of the TIFF |
| Transparency | Places the image on white, because a PDF page is white | Transparent areas become white |
| 32-bit floating-point, CIELab, LogLuv and old-style JPEG images | Converts the page to 8-bit RGB and says so on the file's row | Yes |
A multi-page TIFF is handled page by page, so one file can mix these. Page size comes from the resolution the TIFF states (72 dpi if it states none), and a rotation stored in the TIFF is applied to the page.
How it is tested
The converter is tested on a set of 77 TIFF files made for the purpose: 63 that cover each compression method, color type, bit depth, strip and tile layout, byte order, rotation and resolution setting; 3 TIFF files that ship with macOS; 3 large files (a 108-megapixel color image, a 560-megapixel fax page and a 400-page fax); and 8 damaged files, which must be refused with a clear message rather than crash the page.
For every page of every file, three things are checked. The PDF must have the same number of pages as the TIFF. Each page must have the physical size the TIFF states, to within half a point (1/144 inch). And the page, rendered back to pixels, must match what the TIFF itself decodes to: exactly for black-and-white pages, within 1 level out of 255 for other lossless pages, and within an average of 2 levels for JPEG pages, because JPEG decoders round differently.
The rendering is done in three independent PDF renderers: Poppler 26.03, Ghostscript 10.07 and Apple's Quartz. Using three matters. An early version passed in Poppler and Quartz while showing wrong colors for one kind of JPEG in Ghostscript, and only the third renderer caught it.
Page counts and sizes are also compared with tiff2pdf from libtiff 4.7.2, the reference TIFF library. Its PDFs are not used as the standard for pixels, because on the same files eight of libtiff's nine PDFs of JPEG-compressed TIFFs showed blank pages in Poppler.
The page itself is tested in Chrome and in WebKit, the engine of Safari: converting, combining, a batch of 60 files, working offline, damaged files, a phone-width screen, and the network check described below.
Last tested: November 19, 2026. Result: 77 of 77 files passed.
Known limits
A page that has to be decoded can be at most 1 gigapixel. Pages whose data is copied have no such limit. Beyond that, the largest image you can convert depends on your device's memory.
TIFFs that hold JPEG data in tiles are converted without loss from their decoded pixels, but the PDF is about 4 times the size of the TIFF.
Not tested yet: Firefox, Safari on an iPhone, and the converted PDFs in Chrome's built-in viewer and in Adobe Acrobat. They are expected to work, since the PDFs pass in three other renderers, but we have not measured them.
The converter does not recognize text (OCR), does not make PDF/A files and does not add passwords.
How to check that nothing is uploaded
You do not have to take this on trust. Three checks, from quickest to most thorough:
- Go offline. Load the converter, turn off Wi-Fi or unplug the network cable, then convert a file. It works, which it could not do if the file had to reach a server.
- Watch the network. Open your browser's developer tools, go to the Network tab and add a file. You will see the page fetch its own converter code from tiff2pdf.app. If analytics is on, you will also see small requests to Google Analytics and Microsoft Clarity. Open any of them: none contains your file, its name or its contents.
- Read the security policy. The site sends a Content-Security-Policy header with every page. It tells the browser to block the page from sending data anywhere except tiff2pdf.app itself and the two analytics services. A request to any other address fails.
We run the second check automatically before each release. A test adds files with a marker in their names while Google Analytics and Clarity are running, records every request the page makes, and fails if the marker or any part of a file appears in one.
What the analytics services do receive (page visits, and counts such as "2 files converted, 14 pages") is listed in full on the privacy page. You can switch them off with "Cookie settings" at the bottom of any page.