How multi-page TIFF encoding works inside your browser
Each selected PDF page is rendered onto an off-screen browser canvas and transferred to a Web Worker that writes an 8-byte little-endian TIFF header followed by chained Image File Directories. Every page becomes a self-contained raster strip sequence without uploading 1 byte of your document.
Choosing multi-page .tif archives or separate page files
Selecting Multi-page .tif chains every rendered page sequentially inside a single .tif container. According to the Library of Congress TIFF Revision 6.0 Format Description, baseline TIFF files use a chained IFD directory structure so fax servers and court portals read multi-page filings as one cohesive packet.
Using a browser-based multipage TIFF converter avoids uploading sensitive legal or medical records to third-party servers. Choosing Separate .tif writes each page as its own standalone TIFF file and bundles them into one .zip download, or you can assemble scanned TIFF pages back into PDF locally in one step.
Rendering PDF pages safely up to the 4096 px limit
Wide architectural drawings or oversized posters can exceed browser canvas memory limits if scaled blindly at high DPI. To prevent tab crashes, the converter caps the longest rendered edge at 4096 px and floors the effective resolution at 36 DPI.
Each page is divided into horizontal strips targeting 32768 bytes per strip before compression. Keeping strip sizes bounded lets large multi-page PDFs encode steadily without exhausting browser memory.
Color modes, Deflate vs PackBits compression, and DPI settings
Choosing the right combination of bit depth, compression algorithm, and resolution keeps your exported TIFF accepted by strict e-filing gateways while avoiding bloated archives. The table below compares every mode available in the Color mode, Compression, and Resolution controls.
| Setting group | Option | Bit depth / spec | Best use case | File size impact |
|---|---|---|---|---|
| Color mode | Grayscale (8-bit) | 8-bit luminance | Reports, forms, and mixed text with shading | Moderate |
| Color mode | Black & white (1-bit) | 1-bit bilevel (threshold 165) | Fax servers, legal filings, and high-contrast text | Smallest |
| Color mode | Full color (24-bit RGB) | 24-bit RGB channels | Brochures, charts, and color scans | Largest |
| Compression | Deflate lossless | zlib level 6 | Modern archival storage and smallest lossless size | Smallest |
| Compression | PackBits RLE | Run-length encoding | Legacy imaging systems and older fax viewers | Medium |
| Resolution | 150, 200, or 300 DPI | Scaled from 72 pt PDF | 200 DPI for standard fax; 300 DPI for fine print | Scales quadratically |
Under IETF RFC 3949 File Format for Internet Fax, standard facsimile and archival profiles rely on 200 DPI or 300 DPI grids to keep small serif text legible. When converting color-heavy documents for monochrome portals, using pre-converted grayscale PDF pages first lets you inspect tonal contrast before rasterizing to TIFF.
Handling alpha transparency, page ranges, and worker memory
PDF pages frequently contain transparent vector overlays, signatures, or vector drawings without an explicit white background rectangle. During pixel extraction, every transparent pixel is blended against pure white before converting to 24-bit RGB, 8-bit grayscale using standard luminance weights, or 1-bit bilevel ink using a luminance threshold of 165.
Compositing transparent PDF backgrounds onto white paper
Without white background compositing, transparent regions in 1-bit or 8-bit TIFF files can render as solid black blocks in legacy viewers. Blending alpha channels against white ensures every signature, diagram, and form field looks identical to a printed sheet.
Once pixels are flattened, Deflate lossless encodes each strip with zlib level 6 compression. As defined in the IETF RFC 1951 DEFLATE Compressed Data Format, LZ77 dictionary matching and Huffman coding shrink repetitive white margins dramatically without discarding a single pixel.
Exporting selective page ranges with Web Worker transfers
Entering specific ranges such as 1-3, 5 into Pages (optional) restricts rendering to only the pages you need, skipping cover sheets or appendices. If your source material starts as a presentation deck, you can turn slide decks into fixed PDF pages before archiving and then export only selected slides to TIFF.
When should you archive as TIFF instead of PDF or PNG?
Choose TIFF when a downstream court portal, medical imaging repository, or enterprise fax server explicitly requires multi-page .tif containers. Unlike PNG, which stores only one image per file, a single TIFF file holds hundreds of sequential pages with embedded DPI tags.
Court e-filing, fax servers, and legacy DMS requirements
Many government and insurance portals reject standard PDFs because they want flat, script-free raster pages with deterministic dimensions. Exporting at 200 DPI in Black & white (1-bit fax / archive) with PackBits RLE or Deflate lossless satisfies strict intake validators without leaking fonts or active annotations.
According to the MDN Web Workers API Documentation, transferring pixel buffers to a background worker keeps the browser interface responsive during heavy multi-page encoding. Your original PDF never leaves local memory during this conversion.
Preparing exported TIFF pages for searchable text workflows
Raster TIFF pages store raw pixels rather than selectable characters, which means you cannot highlight or copy text inside a .tif viewer. If you need searchable text alongside archival output, run OCR PDF on your source document before exporting or archiving.
Tip: Start with 200 DPI, Grayscale (8-bit), and Deflate lossless for mixed office documents, then switch to Black & white (1-bit fax / archive) if a portal enforces strict upload size limits.