Skip to content
Archival Conversion Compliance-ready TIFF output

PDF to TIFF API: Multi-page Archival Conversion

Convert PDFs to multi-page TIFF files for document archival, compliance, and healthcare workflows. Preserve every page in a single TIFF with LZW compression, custom DPI, and reversible conversion. Perfect for fax systems and long-term storage.

No credit card required • Free tier available

8,700+ teams use xspdf
Median latency: 520ms
99.95% uptime SLA

PDF to TIFF API Example

REST API
curl -X POST "https://api.xspdf.com/v1/convert/pdf-to-tiff" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "input_url": "https://files.example.com/contract.pdf",
    "options": {
      "dpi": 300,
      "compression": "lzw",
      "multipage": true
    }
  }'

Speed

520ms

Success

99.95%

Formats

40+

520ms

Median conversion time

99.95%

Success rate SLA

8,700+

Teams trust xspdf

Multi-page

All pages in one TIFF

Why PDF to TIFF Conversion Still Breaks Compliance Workflows

Healthcare, legal, and government systems require multi-page TIFF files for archival and fax transmission. But most PDF tools output single-page TIFFs or lose metadata. Engineers waste weeks debugging LibTIFF and Ghostscript to meet compliance standards.

Single-page Nightmares

Tools output one TIFF per PDF page. Archival systems require one multi-page TIFF.

Compression Confusion

LZW, CCITT, ZIP—picking the wrong compression breaks fax gateways.

Metadata Loss

Timestamps, author info, and ICC profiles vanish during conversion.

The hidden cost

Healthcare IT teams spend 60+ hours per quarter fixing TIFF conversion pipelines for PACS, EHR, and fax integrations. Failed audits cost $50,000+ in compliance penalties. One reliable API eliminates this entirely.

One API Call. Multi-page TIFF. Archival-Ready.

xspdf converts entire PDFs into single multi-page TIFF files with LZW compression, 300 DPI resolution, and preserved metadata. No LibTIFF dependencies, no manual page stitching. Perfect for healthcare, legal, and government archival systems.

520ms Median Latency

Convert 100-page medical records to TIFF in under 2 seconds. Batch-process thousands in parallel.

True Multi-page TIFF

All PDF pages in one TIFF file. No stitching, no separate files, no compliance headaches.

LZW & CCITT Compression

Lossless compression reduces file size by 80% while maintaining archival quality.

Read the FAQs

Python Example

import requests

response = requests.post(
    "https://api.xspdf.com/v1/convert/pdf-to-tiff",
    headers={"Authorization": f"Bearer {API_KEY}"},
    json={
        "input_url": "https://files.example.com/contract.pdf",
        "options": {"dpi": 300, "compression": "lzw", "multipage": True}
    }
)
tiff_url = response.json()["output_url"]

Built for Archival and Compliance

Every feature healthcare, legal, and government systems need for TIFF conversion.

Multi-page TIFF

All PDF pages in one TIFF. Perfect for PACS, EHR, and document archival.

LZW & CCITT Compression

Lossless compression reduces file size 80% while preserving print quality.

Custom DPI Control

72, 150, 300, or 600 DPI for archival, fax, or print workflows.

Metadata Preservation

Timestamps, author info, and XMP tags preserved for compliance.

Batch Processing

Convert thousands of PDFs in parallel with async webhooks.

Direct S3/GCS Storage

Output TIFFs straight to your archival cloud storage bucket.

FAQ: PDF to TIFF Conversion

Common questions about multi-page TIFF archival conversion

What is a multi-page TIFF and why do I need it?

A multi-page TIFF stores all PDF pages in a single TIFF file, unlike JPEG or PNG which require one file per page. Healthcare (PACS/EHR), legal, and government systems mandate multi-page TIFFs for document archival, fax transmission, and compliance. Single-file archival simplifies storage, indexing, and retrieval—critical for audits and legal discovery.

What TIFF compression should I use for archival?

Use LZW compression for color/grayscale documents—it reduces file size by 80% with zero quality loss. For black-and-white text documents (like faxes), use CCITT Group 4 compression for 95% size reduction. Avoid JPEG compression in TIFFs for archival—it introduces lossy artifacts. xspdf defaults to LZW for color and CCITT for monochrome.

Can I convert CMYK PDFs to TIFF without color shift?

Yes. xspdf preserves CMYK color space in TIFF output when requested via the "color_mode": "cmyk" option. Embedded ICC profiles are respected, ensuring print-accurate color. By default, xspdf converts to RGB for web/display workflows. If your archival system requires CMYK TIFFs (common in print production), explicitly request CMYK in the API call.

Does xspdf preserve metadata when converting to TIFF?

Yes. Creation date, author, title, and XMP metadata from the PDF are embedded in the TIFF output. This is critical for legal compliance and audit trails. If your PDF lacks metadata, you can inject custom tags via the "metadata" option in the API call. Metadata is preserved in TIFF headers and XMP packets, readable by archival and imaging software.

How do I batch-convert 10,000 medical records to TIFF?

Submit conversions in parallel with async mode enabled. xspdf returns a job_id immediately, then sends a webhook to your callback URL when the TIFF is ready (typically 520ms). For large batches, use our bulk endpoint: POST an array of PDF URLs and get back a manifest of TIFF outputs. No rate limits on enterprise plans. See API docs for healthcare integration examples.

Still have questions? Check the full API docs.

Stop Debugging LibTIFF. Start Archiving.

Join 8,700+ teams who replaced their PDF-to-TIFF pipelines with one API call. No LibTIFF dependencies, no multi-page stitching, no compliance audit failures.

See also: PDF to JPG API, TIFF to PDF API, and 40+ more PDF operations.