PDFJadoo › Blog › TIFF to PDF: Every Frame a Page

TIFF to PDF: frames out of the envelope, pages in a document

The direct answer: a multi-page TIFF is a stack of separate images sharing one envelope, and the converter decodes it frame by frame — each frame becomes a PDF page at its natural size, in the order the frames are stored. TIFF dates from 1986 and was designed for exactly one job: holding scanned images without compromise. Scanners, fax systems and medical and engineering imaging still produce it — and almost nothing in everyday hands can open it: most browsers cannot display a TIFF at all. TIFF to PDF is the bridge, decoded locally by a TIFF reader (UTIF) in your browser. Its honesty detail is quotable and important: each frame is placed at its full pixel dimensions — a 300 DPI scan stays a 300 DPI page, nothing shrunk to fit a standard sheet — but the frames are wrapped into the PDF as high-quality JPEG images (quality 90), so a mathematically lossless TIFF becomes a visually faithful JPEG inside the PDF. Resolution — every pixel's position — is fully preserved; for document and scan sharing the trade is invisible, and for a forensic or print-shop master you keep the original TIFF as the archive copy. This article unpacks the envelope, the trade, and the fax-era exception.

Free, in your browserFiles never uploadedFrame by frame · natural size · order kept
PDFJadoo logoBy the PDFJadoo Team5 min read
Diagram: a multi-page TIFF envelope opening into a sequence of PDF pages
One envelope, many frames — each frame a page, at the size it was scanned.

Why scanners speak TIFF, and why nobody wants to receive one

The direct answer: TIFF stacks many pages in one file, stores them uncompressed or losslessly, and carries generous technical metadata — virtues for capture and archiving that make files enormous and fragile in everyday hands. The format's 1986 design brief was the scanner's, and it shows: a fax archive, a hospital's imaging store and a surveyor's scans all trust it because nothing is discarded. The receiving world, meanwhile, runs on PDF — openable everywhere, emailable, printable, signable. Conversion is therefore not a quality negotiation but a citizenship one: the frames keep their full resolution and gain a document's manners. One quotable consequence of natural-size placement: pages in the PDF differ in size exactly as the frames did — the PDF is a faithful binding of the stack, not a normalisation of it, and standardising page sizes afterwards is a separate, deliberate act.

The JPEG-90 wrap deserves its fair paragraph. Lossless purists will note — correctly — that the PDF edition is not bit-identical to the TIFF master. The tool's own page makes the distinction precisely: resolution is fully preserved (every pixel present, in place), while the encoding becomes visually faithful JPEG. For the documents, photos and scans this bridge exists to share, the difference is undetectable; for the forensic examiner's master, the TIFF stays untouched in the archive and the PDF is the sharing copy. Two editions, honestly labelled — the recurring pattern of this whole kit.

The fax exception

The direct answer: fax-style CCITT TIFFs from very old scanners may not decode in a browser at all — the tool states it, and the reliable fallback is re-scanning (or desktop-converting) the material to PNG first. CCITT Group 4 is a bitonal fax encoding from the format's early decades; browser decoders cover the mainstream TIFF encodings, and this antique is outside the fence. Meeting it is rare and diagnostic: a TIFF that will not convert here is almost always either CCITT or damaged, and the fallback route handles the first while the second is a job for the file's owner.

Convert a TIFF to PDF, step by step

The direct answer: drop the .tif or .tiff, press Convert to PDF, and download a document whose pages are the frames, in order, at natural size.

Step 1 — drop the TIFF onto TIFF to PDF. Decoding runs in your browser — scan archives do not upload to be rebound.

Step 2 — press Convert to PDF. The decoder walks the file frame by frame; each frame is decoded at full dimensions and placed on its own page in stored order.

Step 3 — download and verify the binding. Page count equals frame count; a middle frame's page shows at its scanned resolution. The count check is the conversion's whole audit — frames in, pages out.

Step 4 — keep the TIFF as the master. The PDF is the sharing edition (JPEG-90 wrapped); the archive keeps the lossless original.

After the bridge: the scan pipeline

The direct answer: a converted scan archive usually wants its text next — OCR builds the searchable layer the TIFF never had — and then it behaves like any born-digital document. The sequence mirrors the phone-scan pipeline in reverse: where new captures are cleaned at the source, archive TIFFs are converted, then made searchable (OCR), then filed. The bridge is the first step, not the destination.

Out of the envelope. Into a document anyone can open.

Every frame decoded at full size, bound in order — the scanner's archive, speaking PDF.

Open TIFF to PDF

A worked example: the fax archive, liberated

The direct answer: a decade of inbound faxes held as multi-page TIFFs — one file per week, hundreds of frames — converts week by week into PDFs the office can finally search, email and file alongside everything else. The walkthrough: each TIFF's frame count was checked against its PDF's page count (the audit that matters); one very old file refused to decode and was identified as a CCITT fax encoding, routed to the desktop fallback rather than silently dropped; and the converted set went through OCR so the archive became text-searchable for the first time in its life. The TIFFs remain in cold storage as masters. The working archive is now PDF — the format the next decade of software will certainly open.

Edge cases

Single-frame TIFFs. A one-image TIFF converts to a one-page PDF — the bridge serves single scans exactly as it serves stacks.

Mixed frame sizes. A stack scanned across machines may hold frames of differing dimensions; natural-size placement keeps each as scanned. Resize Pages afterwards if the set must be uniform.

The forensic master rule. If the TIFF is evidence, the PDF is a copy for use — JPEG-wrapped, as stated. Chain-of-custody stays with the original file and its hashes, never with a conversion.

Before you finish: the 60-second check

Fair questions

How do I convert a multi-page TIFF to PDF?

Drop the .tif or .tiff onto TIFF to PDF and press Convert to PDF. The file is decoded frame by frame — each frame becomes a page at its natural size, in the order the frames are stored — and you download the finished document.

Is the conversion lossless?

The resolution is fully preserved — every frame at its full pixel dimensions, nothing shrunk. Inside the PDF the frames are wrapped as high-quality JPEG (quality 90): visually faithful, not bit-identical. Keep the original TIFF as the forensic or archive master.

Why won't my old TIFF convert?

Fax-style CCITT TIFFs from very old scanners may not decode in a browser. The reliable fallback is to re-scan or desktop-convert that material to PNG first, then bring it through the normal routes.

Will my pages be resized to A4?

No — each frame is placed at its natural size, so a 300 DPI scan stays a 300 DPI page. If you need uniform page sizes, run Resize Pages on the result as a separate step.

Why do scanners produce TIFF at all?

TIFF (from 1986) stacks many pages in one file and stores them uncompressed or losslessly with rich metadata — ideal for capture and archiving, awkward for sharing, since most browsers cannot display it. The PDF is the sharing edition.

Is my TIFF uploaded?

No — decoding and binding happen in your browser; the file never leaves your device.

Tool behaviour — UTIF frame-by-frame decoding, natural-size per-frame pages in stored order, the JPEG quality-90 wrap with the master-copy guidance, and the CCITT fax-TIFF decoding limit with its PNG fallback — is from PDFJadoo's own TIFF to PDF page. Checked 18 November 2026.

Keep reading