How to convert TIFF to JPG
- Add your .tif or .tiff file. Every page shows up as a thumbnail, so a multipage scan is easy to check before you export.
- Leave Export as on JPG, and set the Quality you want.
- Export everything, or tick just the pages you need — a long archival scan rarely needs to come out in full.
- Press Export. One page downloads as a single JPG; several pages arrive as one ZIP, numbered in page order.
Why TIFF files are awkward to share
TIFF is a scanner and archive format, and it is good at that job: it can hold many pages in one file, it supports the bitonal compression that fax and document scanners produce, and it does not throw detail away. What it is not good at is being opened by other people. Browsers do not display TIFF, most chat apps refuse it, and plenty of web forms reject the extension outright.
JPG is the opposite trade. It is lossy, it holds exactly one image per file, and it has no transparency — but every device, browser, editor and upload form made in the last thirty years accepts it without comment. Converting is how a scan stops being an archive object and becomes something you can actually send.
A multipage TIFF becomes one JPG per page
- One page in the TIFF → one JPG, downloaded directly.
- Several pages → one JPG each, delivered as a ZIP.
- Only want some of them? Tick those pages before exporting and only they are converted.
This is the part worth understanding before you press Export. A JPG file holds a single image, so a ten-page TIFF cannot become a ten-page JPG — it becomes ten JPG files, one per page, named in page order and delivered as a single ZIP.
If what you actually want is one file that keeps all the pages together, export as PDF instead — it is in the same dropdown, and a PDF can hold every page of the scan in one document.
What this page supports
- Input: TIFF and TIF, single-page or multipage — including the CCITT Group 3/4 bitonal compression that document scanners and fax machines produce, as well as LZW, Deflate, PackBits, uncompressed and JPEG-in-TIFF.
- Output: JPG with a quality setting. PNG, WebP and PDF are one dropdown away.
- Page orientation: the TIFF orientation tag is applied when the file is opened, so pages come out the way they are meant to be seen.
- Transparency: JPG has none. If a TIFF page carries transparent areas, they are filled with the background colour rather than preserved — export as PNG if that matters.
- JPG is lossy: each exported page is re-encoded at the quality you choose. Fine detail in a high-resolution scan is softened at low quality settings; the original TIFF on your disk is untouched.
- Not supported: BigTIFF and the obsolete OldJPEG compression are rejected with a message that says which of the two it was — never disguised as a corrupt file.
- Limits: very large or unusually complex pages are refused before decoding rather than being half-opened, so you never end up with a file that loads but will not turn.
Questions
Is my scan uploaded?
No. The TIFF is read from your disk into your browser's memory, decoded there and re-encoded there. Nothing is sent to a server, so there is no server-side copy to delete afterwards.
My TIFF has 40 pages. Do I get one JPG or 40?
Forty — one per page, delivered as a single ZIP in page order. A JPG file can only hold one image. If you want all the pages in one document, export as PDF instead; it is in the same dropdown.
Will the quality drop?
Yes, to whatever degree you choose. JPG is a lossy format, so every exported page is an approximation of the scan. The quality slider controls how close an approximation. Your original TIFF is never modified.
Can I convert only a few pages?
Yes. Tick the pages you want and export — only those are converted. That is usually the sensible way to handle a long archival scan.
Is the text in my scan searchable afterwards?
No. A scanned TIFF page is a picture of a document, and exporting it as JPG keeps it a picture. There is no text recognition here, so nothing becomes searchable or selectable.
Why was my file rejected?
The two common reasons are BigTIFF — a separate variant of the format — and OldJPEG compression, which modern encoders no longer produce. Both are reported as exactly what they are, so you are not sent looking for damage that is not there.