Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting PDF to TIFF renders the page as an uncompressed picture that every printer, scanner and archive system can read. Choose the page and the resolution — 150 dpi for a screen, 300 dpi for print — and it is produced on your own machine. The document is never uploaded.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
PDF to TIFF
TIFF is not a format anyone chooses for convenience. It is chosen for it: by print shops whose workflow was built around it, by document-management and records systems in law, insurance and healthcare, by fax and archive gateways, and by scanning software that has written TIFF since the 1980s and sees no reason to stop.
What all of those have in common is that they want a picture of a page with nothing clever in it — no fonts to substitute, no compression scheme to disagree about, no embedded objects. TIFF gives them exactly that, and its stubborn size is the price of being readable by a machine nobody has updated in fifteen years.
A PDF page is a set of instructions: draw this glyph from this font at this position, stroke this line, place this image. A TIFF is the result of following those instructions once, at one particular resolution, and then forgetting them. The page looks the same and behaves completely differently.
Concretely: the text is no longer selectable, copyable or searchable, links stop being links, form fields stop being fields, and the file no longer scales — it looks right at the resolution you chose and soft above it. If any of that matters, keep the PDF as well. Converting to TIFF is something you do for a specific recipient, not something you do to your only copy.
The DPI setting decides how many pixels the page is rendered into, and it drives both the quality and the size. At 150 dpi an A4 page comes out around 1240 by 1754 pixels — comfortably sharp on any screen. At 300 dpi it is 2480 by 3508, which is the standard requirement for printing and for most archive specifications. At 600 dpi it is 4960 by 7016, and worth it only for fine line art or very small type.
If the system you are feeding has published a number, use that number. Where none is given, 300 is the safe default for anything that might be printed and 150 for anything that will not.
The TIFF written here is uncompressed baseline RGBA: every pixel stored as four plain bytes, red, green, blue and alpha, with no encoding scheme wrapped around them. That is a deliberate choice, because it is the one variant of TIFF that every reader in existence accepts. LZW and the various JPEG-in-TIFF flavours are smaller and are exactly where old software starts refusing files.
The arithmetic follows from that. An A4 page at 300 dpi is about 8.7 million pixels, so roughly 35 megabytes. At 150 dpi it is nearer 9 megabytes. This is normal for TIFF and not a sign that something went wrong — if the file needs to travel by email, ZIP it, because uncompressed pixel data compresses very well.
Each page becomes its own TIFF. Leave the Pages box empty and the whole document is rendered; name a range — 1-3, 7, 10- — to get less. Anything past a single page arrives as a ZIP with one numbered file per page, rather than as a single multi-page TIFF. Fifty pages is the ceiling for one run, because a page being drawn at 300 dpi is about 35 MB before it is compressed.
That matches how the systems asking for TIFF usually work — one image per page, named in sequence — and it avoids quietly producing a 350-megabyte file from a ten-page document. If you genuinely need a multi-page TIFF, it has to be assembled by a dedicated imaging tool afterwards.
The page is rendered in full colour with an alpha channel and stored that way. A scanned black-and-white document converted at 300 dpi is still a colour TIFF containing black and white pixels — visually identical, structurally different.
Some archive standards specify bitonal (one bit per pixel) or greyscale TIFF, usually with Group 4 fax compression. That is not a format conversion but an imaging decision — a threshold has to be picked, and picking it badly destroys thin strokes and light stamps. Software built for scanning does it properly; a converter guessing at it would not.
If nobody has specifically demanded TIFF, they are almost certainly the better answer. PNG holds exactly the same pixels as the uncompressed TIFF, losslessly, at a fraction of the size, and every program made this century opens it. JPG is smaller still and fine for a page that is mostly a photograph.
Reach for TIFF when a specification, a submission portal or a print operator names it. Otherwise the same page as PNG is the identical picture in a file people can actually email.
The PDF is rendered and the TIFF written by code running inside your browser tab. Nothing is uploaded, so there is no server-side copy, no retention period to ask about and no queue to wait in. The free tier takes files up to 100 MB each, which is well clear of the input side even when a single page turns into 35 megabytes of TIFF.
Given what typically gets converted to TIFF — signed contracts, patient records, court filings, insurance claims — that is not a detail. The safest handling of a confidential document is the kind where it never travels.
| TIFF | ||
|---|---|---|
| Full name | Portable Document Format | Tagged Image File Format |
| File extension | .tif, .tiff | |
| Media type | application/pdf | image/tiff |
| Compression | Either, depending on the setting | Lossless — nothing is discarded |
| First published | 1993 | 1986 |
| Published by | Adobe | Adobe |
| Specification | ISO 32000-2 | TIFF 6.0 |
| Licensing | Open standard | Published, not standardised |
| Standing today | Current | Current |
| Bit depth | — | 32 |
| Colour it can describe | RGB, CMYK, greyscale | RGB, CMYK, greyscale, Lab |
| Opens in a browser | Every browser | Some browsers |
| Considered instead | DOCX, HTML | PNG, DNG |
TIFF holds one page. A multi-page PDF converts a page at a time rather than in one file.
TIFF has nowhere to put the document properties, so that goes no further than the PDF. Worth checking before the original is deleted, and worth knowing if the point was to strip it.
Transparency survives. Both PDF and TIFF store an alpha channel, so a cut-out stays cut out and nothing is filled in behind it.
TIFF is a working format and PDF is a finished one. What comes back is editable text and objects rather than a picture of a page, which is usually the reason for the conversion and also where its limits are.
Only some browsers read TIFF. It is the less portable of the two, so it is worth being sure the program at the other end accepts it before sending one.
The usual programs do not overlap: PDF opens in Adobe Acrobat, Preview and LibreOffice Draw, TIFF in Adobe Photoshop, Affinity Photo and ImageMagick — so whoever receives the result needs something from the second list.
PDF is Adobe's format, published in 1993. The specification is ISO 32000-2, and it is worth reading if the file has to outlive the tool that wrote it.
TIFF comes from Adobe and dates from 1986, specified as TIFF 6.0. Adobe Photoshop, Affinity Photo and ImageMagick all read it.
No. This conversion runs entirely inside your browser, so the file never leaves your device. You can confirm it yourself: open the network tab of your browser's developer tools and convert something. You will see the page load, plus the analytics and advertising the site is paid for with — and nothing carrying your file. The engine behind this particular pair is PDF.js, Mozilla's PDF engine, the one Firefox itself uses; your browser fetches it once and caches it.
Use what the receiving system asked for. If nobody said: 150 dpi is right for anything read on a screen, 300 dpi is the normal requirement for printing, and 600 dpi is only worth it for line art or small type that will be enlarged. Higher settings multiply the file size without adding anything a reader can see.
Because it is written uncompressed, which is what makes it readable by every scanner, printer and archive tool. An A4 page at 300 dpi is roughly 2480 by 3508 pixels, and storing each of those with four bytes comes to about 35 megabytes for one page. At 150 dpi the same page is around 9 megabytes.
No. The page becomes a picture of itself, so the letters are shapes rather than characters. Keep the PDF if you need the text, or run the TIFF through OCR at the other end. Systems that ask for TIFF usually do their own OCR on arrival.
One page per conversion. Set the page number, convert, then change the number and convert again. A single multi-page TIFF is not produced here — most systems that accept TIFF want one file per page anyway.
Colour, with an alpha channel, exactly as the page renders. If your archive requires bitonal or greyscale TIFF, this is not the right conversion — those need a thresholding step that belongs in scanning software rather than a format change.
No. The page is rendered and encoded by code running in your own browser, so the document never leaves your machine. That is worth knowing for the contracts, medical records and case files that make up most of what gets converted to TIFF.
The claims this page makes about PDF and TIFF are checkable, and these are the documents that settle them.