TIFF vs JPG: When You Really Need Lossless

One photo, two formats: the core idea

Picture the exact same shot saved twice. As a TIFF it's 80 MB and holds every pixel precisely as the camera or scanner recorded it. As a JPG the same frame is 4 MB — twenty times smaller — but the format has already thrown some data away, betting your eye won't miss it.

That's the whole dilemma. TIFF is built to store an image losslessly: it's the "master file," the reference. JPG is built to store an image lossily: it's the lightweight copy for everyday life. Arguing "which is better" is pointless — it's like arguing whether the original painting beats a sharp print of it in a catalog. Each has its role.

"Lossless" and "lossy" in plain English

These two words are the root of every difference, and an analogy makes them click.

Lossless compression (TIFF) works like a ZIP archive of a document: the file gets smaller, but when you unzip it you get back the exact same text, byte for byte. Not a letter is lost. TIFF does this with the LZW and ZIP (Deflate) methods — or it simply stores pixels "as-is," uncompressed.

Lossy compression (JPG) works differently. It splits the picture into 8×8-pixel blocks and, through a mathematical transform (the DCT), describes each block as a set of "waves." Then it rounds off or discards the subtle details your eye barely registers. The harder the compression, the more is thrown out — and the more visibly blocky "squares" and halos appear along high-contrast edges, the so-called artifacts.

The crucial bit: discarded data can't come back. A JPG can't be "un-compressed" into the original, because the original isn't in there anymore — only a clever approximation of it is.

Generation loss: why JPG ages

Here's the effect many people don't suspect — and it settles the debate almost more than anything. Every re-save of a JPG runs the compression again and throws away a little more data. Open a JPG, nudge the brightness, save — lost some. Open it again, crop, save — lost some more. This is generation loss: distortions accumulate from generation to generation, like photocopying a photocopy.

One or two saves at high quality you probably won't notice. But by the tenth pass the image visibly softens, colors muddy, and halos spread around contrasty lines. TIFF simply doesn't get this disease: lossless compression discards nothing, so re-save the file a hundred times and it stays identical to the first.

File size: a 10–50× gap

The price for TIFF's precision is size. On the very same shot the gap is huge: what's 3–5 MB as a JPG easily becomes 50–150 MB as a lossless TIFF. For photographs that's roughly a 10× to 50× difference, and large 16-bit scans can balloon into hundreds of megabytes or even gigabytes.

Why? JPG honestly trades detail for lightness — and wins by a wide margin. TIFF trades nothing, so there's little left to squeeze: LZW and ZIP shrink it only moderately, since they're forbidden to discard pixels. For print and archiving that weight is normal, even desirable. But storing such files by the thousands, uploading them to the cloud, or emailing them is painful — and that's exactly where JPG has no rival.

Color, 16-bit and CMYK: JPG's wall

Beyond the loss, JPG has two hard limits that TIFF removes.

Color depth. JPG stores 8 bits per channel — 256 shades of each color. TIFF can store 16 bits — that's 65,536 shades, 256 times more. On a finished shot the difference is usually invisible, but during editing the headroom is decisive: when you lift shadows or stretch a smooth sky, an 8-bit JPG runs out of "steps" and you get visible banding. A 16-bit TIFF survives the same edit without a trace.

Color model. Screens show color in RGB (red-green-blue), while print shops print in CMYK (cyan-magenta-yellow-black). JPG only does RGB. TIFF stores the image directly in CMYK — exactly the way a printing press will see it. That's why layouts go to print as TIFF: what you hand over is what gets printed, with no color surprises.

When JPG is the right call

It's easy to read all this and conclude "TIFF is always better." That's a trap. In most everyday tasks choosing TIFF just wastes space and patience. Here's where JPG is objectively the right pick:

• Photos for the web and social media. Browsers don't open TIFF at all, and a site needs speed. A quality JPG loads instantly, and on screen you can't see the difference from the original.
• Shooting in big bursts. Sports, reportage, events — thousands of frames. Shooting it all in RAW/TIFF means filling the card and the drive; JPG is the sensible quality-vs-volume compromise.
• A finished image that won't be edited. If the frame is final and no further edits are coming, generation loss is a non-issue — while the 20× space saving is very real.
• Sending and sharing. Email it, drop it in a messenger, upload it to a form — JPG sails through everywhere, while a heavy TIFF hits size limits.
• An everyday family photo library. Thousands of personal snapshots in TIFF means terabytes and friction; in JPG it's a compact, convenient collection.

The cheat-sheet: what to pick

Boiled down to practice, it's a simple fork by task:

• Commercial print, poster, cover → TIFF (CMYK, high DPI, lossless).
• Archiving, digitization, restoration → TIFF (a reference for decades).
• Serious retouching and color grading → 16-bit TIFF (headroom for edits).
• Website, blog, online store → JPG (speed and compatibility).
• Social media, messengers, email → JPG (lightness).
• A final photo with no edits planned → high-quality JPG.

Notice that in almost any "professional" scenario the optimum is not one format but a pairing. You shoot and edit in TIFF, and send it out into the world as JPG. That way you get both the untouched original and the convenient copy.

How to convert both ways

In practice you usually need one thing: turn a heavy TIFF into a light JPG so the file can be shown, sent or posted. It takes seconds.

One important caveat about the reverse direction: you can't turn a JPG into a lossless TIFF. Converting JPG to TIFF gives you a lossless file, but the quality inside it stays exactly what the JPG had — the discarded data won't come back. A TIFF made from a JPG only makes sense as a technical step (say, to feed a program that accepts TIFF only), not to "improve" the picture.

Not JPG you're after? Assemble a document from the pages with TIFF to PDF, keep transparency via TIFF to PNG — and the full list of conversions is always on the all formats page. And if you're just getting to know the format, start with what TIFF is.