PDF to TIFF: every pixel, at the resolution the professional specified
The direct answer: the converter renders each PDF page at the DPI you choose and encodes it as a real TIFF — uncompressed and lossless — delivered as one TIFF per page in a ZIP. Nobody chooses TIFF for pleasure. It is demanded — by print pipelines, legal archives, older document-management systems — and what the demand actually specifies is pixels without lossy compression at a stated resolution. PDF to TIFF meets it literally, and its page states the consequence without flinching: TIFF files are uncompressed and large — a single 300 DPI page can be 25 MB or more — because that bulk is precisely the point: nothing was thrown away. The DPI guidance is equally quotable: 300 DPI for print and archiving, 200 for everyday use, 150 when file size matters more than sharpness. This article explains the demand, the arithmetic of the bulk, and the one-TIFF-per-page arrangement.
Why TIFF is demanded: the lossless argument
The direct answer: JPG and WebP achieve their small sizes by discarding pixel information permanently; TIFF declines to discard, so an archive holding TIFFs holds everything the render produced — the only honest master format among the common image types. Print makes the same demand for a different reason: a press pipeline wants the full pixel grid at production resolution, not an approximation tuned for screens. One quotable piece of arithmetic explains the file sizes: a 300 DPI A4 page is roughly 2,480 × 3,500 pixels — about 8.7 million pixels — and at three bytes per pixel uncompressed, that is the 25 MB the tool warns about. The number is not bloat; it is the page, all of it. Where a system asks for TIFF, it is asking for that completeness, and sending a JPG instead is answering a different question.
The delivery arrangement is the compatibility choice: one TIFF per page, in a ZIP, rather than a single multi-page TIFF. Multi-page TIFF is a real variant — the scanner world lives on it, and the reverse converter TIFF to PDF unpacks it frame by frame — but single-page files are the most widely accepted arrangement across the mixed bag of systems that demand TIFF, each page independently openable by anything that reads the format at all.
DPI: the only real decision
The direct answer: DPI decides how many pixels the page is rendered with — 300 for print and archive masters, 200 for everyday professional use, 150 when the file must travel light — and no later step can add resolution the render did not produce. This is the same render-first law as every page-image conversion in the kit: the render is the master, the encoding is its container. Doubling back to re-render at 300 after sending 150 is possible only because the PDF survives as the source — one more reason the PDF remains the master from which TIFF editions are struck.
Convert a PDF to TIFF, step by step
The direct answer: drop the PDF, choose the DPI the demanding system specified (or 300 for print/archive), press Convert to TIFF, and download the TIFF — or the ZIP of TIFFs for a multi-page document.
Step 1 — read the demand precisely. The print shop or archive named a resolution, or a purpose from which it follows: print and archiving mean 300.
Step 2 — drop the PDF onto PDF to TIFF. Rendering and encoding happen in your browser — a 25 MB-per-page output is generated locally, not shuttled through a server.
Step 3 — choose the DPI and press Convert to TIFF. 300 print/archive, 200 everyday, 150 size-first.
Step 4 — download and budget the bulk. Multi-page results arrive as a ZIP of one TIFF per page. A 40-page archive at 300 DPI is a gigabyte-class artefact — plan its transport (drive, link, physical media) rather than discovering it at an email limit.
TIFF's place in the family
The direct answer: TIFF is the master/archive end of the page-image spectrum — PNG for lossless screen graphics at sane sizes, JPG for photographs at small sizes, WebP for the web, TIFF when a professional system demands every pixel. Choosing among them is choosing what may be discarded; TIFF's answer — nothing — is occasionally exactly what the job requires.
When they ask for TIFF, they mean every pixel. Send every pixel.
Honest renders at 150, 200 or 300 DPI, encoded uncompressed — one TIFF per page, zipped.
Open PDF to TIFFA worked example: the archive that would not take PDF
The direct answer: a firm's document-management system — old, mandated, immovable — accepts TIFF only, so a 12-page executed agreement is rendered at 300 DPI into twelve TIFFs totalling roughly 300 MB, delivered on the firm's own file share rather than by email. The walkthrough's craft is in the logistics the format forces: the DPI was confirmed against the archive's written spec before rendering (300, not a guess); the ZIP's arrival was verified page by page against the PDF; and the PDF stayed in the firm's modern files as the working copy, the TIFFs existing solely as the archive of record. Two editions, two systems, one document — the TIFF edition struck from the master like a print from a negative.
Edge cases
The fax-era demand. Some “TIFF” requirements mean a specific bitonal fax profile, not full-colour pages. Read the spec's fine print; a greyscale or B&W page set may be what is actually wanted, at a fraction of the bulk.
Colour pages for print. A screen PDF is RGB; a press may want CMYK. This converter renders the page as it is — if the print shop's spec says CMYK, that conversation belongs with the shop before the render, not after.
Enormous documents. Hundreds of pages at 300 DPI is a rendering marathon and a storage event. Split the PDF and convert in parts, matching the archive's own intake batches.
Before you finish: the 60-second check
- The demanding system's DPI was read from its spec — 300 for print/archive, not guessed
- Transport was planned for the bulk: ~25 MB per 300-DPI page is the format's nature
- Delivery is one TIFF per page in a ZIP — verified page by page against the PDF
- The PDF remains the working master; TIFFs are the archive edition
- Fax-profile or CMYK fine print in the spec was checked before rendering
Fair questions
How do I convert a PDF to TIFF at 300 DPI?
Drop the PDF onto PDF to TIFF, choose 300 DPI — the print and archiving setting — and press Convert to TIFF. Each page renders honestly at that resolution and encodes as an uncompressed TIFF; multi-page PDFs download as a ZIP of one TIFF per page.
Why is the TIFF so much bigger than the PDF?
TIFF stores every pixel without lossy compression: a 300 DPI page is about 2,480 × 3,500 pixels, which uncompressed runs to 25 MB or more. That bulk is exactly why archives trust it — nothing was discarded.
Do I get one multi-page TIFF?
No — you get one TIFF per page in a ZIP, the most widely compatible arrangement. Each page opens independently in anything that reads TIFF.
Which DPI should I pick?
300 for print and archival, 200 for everyday use, 150 when file size matters more than sharpness. If a system specified a resolution, its word governs.
Is TIFF better than PNG for archiving?
Both are lossless. PNG compresses its lossless data, so files are far smaller and ideal for screen graphics; TIFF's uncompressed form is what legacy archives and print pipelines are built to ingest. The demanding system decides.
Is my PDF uploaded?
No — rendering and encoding happen in your browser, which matters at these file sizes: nothing enormous is shuttled anywhere.
Tool behaviour — uncompressed TIFF encoding, the 25 MB+ warning for a 300 DPI page, one TIFF per page delivered in a ZIP, and the 300/200/150 DPI guidance — is from PDFJadoo's own PDF to TIFF page. Checked 18 November 2026.
Keep reading
TIFF to PDF: every frame a page
The scanner archive's return: multi-page TIFFs unpacked into a shareable PDF.
PDF to PNG: the lossless choice
Lossless at sane sizes: the screen-graphics end of the same spectrum.
PDF to JPG: which DPI?
The render arithmetic in full: what a DPI buys, page by page.
PDF Inspector: a file checkup
Before striking archive editions: the source file's full structural chart.