One-page report
- Input
- sample.pdf, one Letter page with text and a table, 21,438 bytes.
- Output
- 1224×1584 RGB TIFF, 65,202 bytes, deflate, 144 DPI tag, in 45 ms.
PDF → TIFF renders every page into a single multi-page TIFF with the resolution tag set, the container fax, archiving and OCR tools expect.
From real runs
| Element | Result | What happens |
|---|---|---|
| Pages | Kept | A two-page deck rendered into one TIFF with two frames; page order and count matched the PDF. |
| Resolution | Changed | Pages render at 144 DPI (1224×1584 pixels for Letter) and the TIFF stores that value in its XResolution and YResolution tags. |
| Compression | Changed | Every frame is deflate-compressed: the one-page sample is 65,202 bytes and the two-page deck 103,648 bytes. |
| Selectable text | Lost | The frames are pixels only; there is no text layer, so OCR must run on the TIFF to make it searchable again. |
| Colour | Changed | Frames are 8-bit RGB. There is no 1-bit or grayscale mode, so a black-and-white fax TIFF has to be produced elsewhere. |
| Transparency | Changed | Pages are opaque white paper unless transparent=true, which renders an RGBA frame with blank areas transparent. |
A two-page deck rendered into one TIFF with two frames; page order and count matched the PDF.
Pages render at 144 DPI (1224×1584 pixels for Letter) and the TIFF stores that value in its XResolution and YResolution tags.
Every frame is deflate-compressed: the one-page sample is 65,202 bytes and the two-page deck 103,648 bytes.
The frames are pixels only; there is no text layer, so OCR must run on the TIFF to make it searchable again.
Frames are 8-bit RGB. There is no 1-bit or grayscale mode, so a black-and-white fax TIFF has to be produced elsewhere.
Pages are opaque white paper unless transparent=true, which renders an RGBA frame with blank areas transparent.
We converted our PDF sample (21 KB) with Image engine on 2026-09-11. It took 45 ms and produced a 64 KB TIFF file, 3.0× larger than the input. The engine raised 1 warning, listed below.
Input · sample.pdf · 21 KB
PDF 1.7, 1 page, selectable text (LibertinusSerif-Bold-Identity-H, LibertinusSerif-Bold, LibertinusSerif-Regular-Identity-H, LibertinusSerif-Regular), 0 image objects
Output · sample.tif · 64 KB
1224 × 1584 px, deflate
Rendering a scanned PDF to TIFF simply re-encodes the scan pixels, so raise dpi to the scan's native resolution to avoid softening. If you need the words, PDF → TXT with AI Deep Read reads the pages directly for 1 credit each and skips the TIFF step.
PyMuPDF and Pillow
import fitz
from PIL import Image
import io
pages = [Image.open(io.BytesIO(p.get_pixmap(dpi=144).tobytes("png"))) for p in fitz.open("in.pdf")]
for p in pages: p.encoderinfo = {"compression": "tiff_deflate"}
pages[0].save("out.tiff", save_all=True, append_images=pages[1:], compression="tiff_deflate", dpi=(144, 144))Without setting encoderinfo on every frame, Pillow writes the appended frames uncompressed.
Ghostscript
gs -sDEVICE=tiff24nc -r144 -o out.tiff in.pdfUse tiffg4 for 1-bit fax output; tiff24nc writes uncompressed RGB.
The HTTP API and the MCP server run the exact engine this page uses (Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=pdf&to=tiff.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.pdf" -F "from=pdf" -F "to=tiff" \
-F 'options={"dpi":96}' \
--output output.tif| Key | Applies to | Type | Default |
|---|---|---|---|
| dpi | Reading PDF | number | 96 |
One multi-page TIFF by default, with each page as a frame. Set multipage to false to receive a ZIP of single-page TIFFs instead.
Yes. The dpi you choose (144 by default) is written to the resolution tags, so scanning software and OCR engines report the correct physical page size.
Not from this route; frames are 8-bit RGB with deflate compression. Convert with Ghostscript's tiffg4 device when a fax-style 1-bit file is required.