Turn a scan or production TIFF into a practical JPEG, with pages, colour model, depth and resolution reported before the reduction.
What changes when TIFF becomes JPEG
TIFF is a container for many combinations: compressed or uncompressed strips, multiple pages, alpha, high bit depth and sometimes CMYK. The local decoder states what it found, renders a page into browser-readable pixels and then hands those pixels to the same JPEG encoder used by the rest of the converter.
A TIFF alpha channel needs the same matte decision as a PNG. CMYK and deep inputs need a colour and depth reduction before an ordinary web JPEG can be produced; the queue names those cases so the output is not mistaken for an archival equivalent.
A short, inspectable workflow
- Drop one TIFF file or a whole selection. The queue reads the signature inside each file instead of trusting its extension.
- Inspect the detected type, dimensions and any format notice on each row before conversion.
- Choose JPEG quality and, where transparency exists, the colour that must replace it.
- Choose whether ordinary EXIF data survives and whether GPS coordinates are removed.
- Convert the queue. More than three finished files download as one ZIP so the browser does not open a stack of save prompts, and Download as ZIP bundles any two or more.
What the conversion cannot preserve
Multi-page structure, 16-bit channel precision, layers, spot colours and production-specific TIFF tags cannot live in the resulting JPEG. The route is for a viewing or upload copy. The TIFF remains the master for scanning, print production and later correction.
A converted file is a new JPEG, not the original format with a different filename. Keep the source whenever animation, layers, high bit depth, transparency or repeated future edits might matter.
Questions about this input
Which page of a multi-page TIFF is converted?
What happens to 16-bit TIFF colour?
Does the DPI survive?
Photos stay on your device.