TIFF wins on image quality in one specific sense: it stores uncompressed or losslessly compressed pixel data, so what you save is exactly what you reopen, while JPG throws away image data every time you save. That difference matters most in editing workflows and archival storage, not in how an image looks on screen. The trade-off is blunt: TIFF files run roughly 5 to 20 times larger than a high-quality JPG of the same photo, and that size gap shapes everything about how you use each format. If you are asking this question, you are likely deciding what to export from a camera, scanner, or editor β€” and the answer depends on whether the file needs to survive repeated editing or just be viewed and shared.

Photo: The main difference between TIFF and JPG is how each format handles pixel data. TIFF stores image data losslessly, while JPG uses lossy compression that permanently discards some detail.

What TIFF Actually Stores Compared to JPG

TIFF is a container format, and that container can hold uncompressed RGB data, losslessly compressed data using LZW or ZIP compression, or even layered and multi-page content. The Adobe TIFF specification, first published in 1986 and still the reference document for the format, defines it as a tag-based structure that can carry almost any image data type. When a scanner or camera saves a TIFF, every pixel value the sensor or sensor pipeline produced is written to disk without averaging, quantizing, or discarding. That is the core of its quality advantage.

JPG works the opposite way. The JPEG standard, maintained by the Joint Photographic Experts Group under ISO/IEC 10918-1, divides an image into 8Γ—8 pixel blocks, converts them to a frequency representation, and quantizes the high-frequency coefficients β€” the fine detail β€” based on a quality setting. At quality 90 or above, most viewers cannot see the difference on a single save. The loss becomes visible in gradients and fine textures, and it compounds with each re-save.

So the quality comparison splits into two questions. On first save at high quality, a JPG looks nearly identical to a TIFF to the human eye. After ten edits and re-saves, they diverge. A TIFF opened and saved a hundred times retains identical pixel values; a JPG saved a hundred times at quality 90 has been quantized a hundred times, and the artifacts accumulate. That is why print shops, publishers, and archivists ask for TIFF delivery.

The scanned-document world makes the gap concrete. The U.S. National Archives and Records Administration's digitization guidance recommends uncompressed TIFF as the preservation master format for scanned textual records, with JPG acceptable only for access copies. That recommendation exists because a preservation master is expected to survive decades of migration and re-processing, and lossy compression forecloses that. If your file is a working copy bound for a social post, the calculation is entirely different.

The Size Gap in Real Numbers

The trade-off everyone hits first is file size, and the numbers are steep. A 24-megapixel camera photo β€” 6000 Γ— 4000 pixels β€” holds 24 million pixels; at 8 bits per channel across three channels (RGB), that is 72 megabytes of raw pixel data before any file overhead. An uncompressed TIFF of that image lands near 70 MB. A high-quality JPG of the same photo typically lands between 8 and 15 MB. That is roughly a 5:1 to 9:1 ratio, and it gets worse with higher-resolution sensors.

Image Pixel dimensions Uncompressed TIFF (approx.) JPG at quality 90–95 (approx.) Ratio
12 MP photo 4000 Γ— 3000 35 MB 5–7 MB ~5–7:1
24 MP photo 6000 Γ— 4000 70 MB 8–15 MB ~5–9:1
45 MP photo 8192 Γ— 5464 134 MB 15–25 MB ~5–9:1
A4 scan at 300 ppi, color 2480 Γ— 3508 25 MB 2–4 MB ~6–12:1
A4 scan at 600 ppi, color 4960 Γ— 7016 100 MB 8–15 MB ~7–12:1

The scan figures follow from the arithmetic: an A4 page at 300 ppi is about 8.7 megapixels, so 8.7 million pixels Γ— 3 bytes per pixel comes to roughly 26 MB uncompressed. JPG compresses photographic and scanned content far more aggressively than it compresses flat graphics, which is why scanned text often compresses to a tenth of its TIFF size while a detailed landscape photo compresses less.

TIFF's LZW and ZIP compression options narrow the gap without losing a single pixel, but only modestly. The TIFF 6.0 specification describes LZW as a lossless scheme, and lossless compression on photographic content typically achieves 1.5:1 to 3:1 depending on the image β€” detailed foliage compresses poorly, smooth skies compress well. That still leaves TIFF files several times larger than JPGs. Storage math follows directly: a 500-image shoot at 24 MP is about 35 GB as uncompressed TIFF and about 5 GB as JPG. A 4 TB external drive holds roughly 114 such TIFF shoots or 800 JPG shoots.

Where JPG Loses Quality and Where It Doesn't

JPG's lossy compression is not uniformly destructive. It exploits human vision, which is more sensitive to brightness than to color and less sensitive to fine high-frequency detail. At quality 95, the quantization applied is gentle, and a single save of a well-exposed photo is visually indistinguishable from the original in side-by-side viewing at normal magnification. The format also stores color at reduced resolution through chroma subsampling, typically 4:2:0, which halves color detail horizontally and vertically while keeping full luminance detail.

The damage shows up in specific conditions. Sharp high-contrast edges β€” text on a page, architectural lines against sky β€” develop ringing or "mosquito" artifacts around them. Smooth gradients like sunsets or studio backdrops develop banding. Repeated saves amplify both, because each pass re-quantizes data that was already quantized. A JPG opened, retouched, and saved ten times at quality 90 shows visibly softer detail and blockier shadows than the original, even though each individual save seemed fine.

There is also a metadata and bit-depth gap that affects quality indirectly. Standard JPG is 8 bits per channel, so it cannot hold the 10-, 12-, or 14-bit data a modern camera sensor captures; those extra bits are where highlight and shadow recovery live in editing. TIFF can carry 16-bit-per-channel data, which is why raw converters and scanners offer TIFF output at 16 bits. If you plan to push exposure or lift shadows aggressively, an 8-bit JPG has already thrown away the headroom you need.

For images destined only for screens β€” web pages, social media, email β€” none of this matters, because the viewing pipeline and platform recompression dominate. Facebook and Instagram recompress uploads regardless of what you send, so a TIFF upload gains nothing on those platforms and may not even be accepted. Screen output is the JPG use case, and TIFF delivers no visible benefit there.

The Real Cost: Workflow and Storage Burden

The TIFF trade-off is not just disk space. It is throughput. A 70 MB TIFF takes longer to write to a card, longer to copy to a drive, longer to open in an editor, and longer to upload. On a typical USB 3.0 external drive writing at around 100 MB/s, copying a 500-image TIFF shoot of 35 GB takes roughly six minutes of pure transfer time; the same shoot as JPG takes under a minute. Over a year of heavy shooting, those minutes compound into hours.

Editing performance degrades too. Photoshop, Lightroom, and Capture One all handle large TIFFs, but a 16-bit 45 MP TIFF can be 250 MB or more, and brush strokes, layers, and history states multiply memory use. Machines with 16 GB of RAM will feel the difference when working with stacks of layered TIFFs. JPGs open instantly and scrub smoothly, which is why culling and proofing happen on JPGs or rendered previews even in TIFF-based pipelines.

Backup and cloud costs scale with the same ratio. Cloud backup services charge by storage volume; a photographer storing TIFF masters needs five to nine times the plan size of one storing JPGs. Archival institutions accept that cost because preservation masters are their product. A casual user backing up family photos usually should not β€” the family photos will be viewed, not re-edited and re-migrated for a century.

The workflow rule that resolves this: choose the format by what happens to the file next, not by which format sounds more professional. Files that will be edited repeatedly, printed at large sizes, or archived as masters go to TIFF. Files that are finished outputs go to JPG at the highest quality the destination accepts.

When TIFF Is the Right Choice

Four situations reliably justify TIFF. First, editing masters: if an image will pass through multiple editing sessions across years, TIFF preserves every pixel between sessions, while every JPG save is a fresh lossy pass. Second, print production: commercial printers and publishers commonly request TIFF for large-format output because it avoids compression artifacts that become visible at poster scale and supports 16-bit data for smooth gradients. Third, scanning and digitization: archival standards, including NARA's guidance for textual records, name TIFF as the preservation master for good reason β€” scans are typically edited, cropped, and re-processed after capture, and a lossless master survives that. Fourth, medical and technical imaging: modalities like microscopy and satellite imagery often output TIFF because measurement depends on exact pixel values, and lossy compression would corrupt the data.

Photographers shooting raw have a nuance here. A camera raw file is not a TIFF in the usual sense β€” it is proprietary sensor data β€” but many raw converters can export 16-bit TIFF as an intermediate for further editing in another application. That intermediate TIFF is a working master, not an archive format, because it is far larger than the raw file and carries no camera metadata advantages. Export TIFF intermediates when moving between editors, then delete them once the final output exists.

Scanned text deserves a specific note. For documents that will be OCR'd or stored for decades, a 300 ppi color TIFF is the standard preservation master, with a compressed JPG or PDF derivative serving as the access copy. The master's job is to be re-derivable into any future format; the derivative's job is to be read today. Mixing those jobs β€” archiving the JPG and distributing the TIFF β€” inverts the whole logic and is a common filing mistake in small offices.

When JPG Wins and TIFF Is a Waste

JPG wins whenever the file is finished. Web images, email attachments, social posts, client proofs, phone wallpapers, presentation slides β€” every one of these is a delivery surface, and the size penalty of TIFF buys nothing there. A 70 MB TIFF uploaded to a website slows page loads and may be rejected by the CMS; the same image as a 3 MB JPG at quality 85 loads fast and looks identical to viewers. Every major browser displays JPG natively and displays TIFF poorly or not at all, which alone settles the web question.

Storage-constrained devices make the same case. A phone's camera roll, a tablet's photo library, and a laptop's working drive all fill up faster with TIFF, and most consumer apps do not even accept it. The format's strengths β€” lossless data, 16-bit depth, layered and multi-page capability β€” are invisible to a photo viewer that downsamples to screen resolution anyway. If nobody will ever re-edit or print the file, the extra data is dead weight.

There is also a compatibility trap in the other direction. TIFF is a container, and different applications write different flavors: some produce uncompressed RGB TIFFs that open everywhere, others produce LZW-compressed, CMYK, or layered TIFFs that some viewers refuse. A TIFF sent to a print shop should be checked against the shop's stated requirements β€” color space, bit depth, compression, and whether layers are flattened β€” before sending. JPG has fewer variables: baseline JPG at high quality opens essentially everywhere.

Compression Options Inside TIFF

TIFF's flexibility means "a TIFF" is not one thing, and the compression choice inside the container changes both quality and size. Uncompressed TIFF stores every byte and is the safest archival choice but the largest. LZW compression, defined in the TIFF 6.0 specification, is lossless and typically shrinks photographic TIFFs by a third to two-thirds depending on content. ZIP/Deflate compression, also lossless, often beats LZW on photographic data. Both reopen to identical pixels β€” the compression is a storage trick, not a quality setting.

The trap is that some TIFF writers offer JPEG compression inside the TIFF container. A JPEG-compressed TIFF is a lossy file wearing a TIFF extension, and it inherits every JPG artifact while keeping TIFF's size overhead. If the goal is a lossless master, confirm the compression setting is None, LZW, or ZIP β€” not JPEG. This distinction trips up people who assume the extension guarantees losslessness.

TIFF compression Lossless? Typical size vs. uncompressed Best for
None Yes 100% Archival masters, maximum compatibility
LZW Yes 40–70% General lossless storage
ZIP/Deflate Yes 35–65% Photographic lossless storage
JPEG-in-TIFF No 10–20% Rarely advisable; inherits JPG artifacts

Bit depth multiplies the same way. An 8-bit TIFF matches JPG's per-channel precision; a 16-bit TIFF doubles the file size and holds the extra headroom that raw workflows need. Scanning at 16-bit and saving as 8-bit TIFF throws away half the tonal data before any editing begins, which defeats much of the point of scanning to TIFF in the first place.

Picking a Format by Destination

The decision reduces to a destination table, and it holds across cameras, scanners, and editors. Destination decides format; format does not decide destination.

Destination Format Why
Web page, email, social post JPG (quality 80–90) Small, universally displayed, recompressed by platforms anyway
Client proofing gallery JPG Fast loading; proofs are not masters
Multi-session photo editing TIFF (16-bit) or raw Lossless between sessions, editing headroom preserved
Large-format print TIFF (8- or 16-bit, flatten layers) No compression artifacts at poster scale
Document/photo archive TIFF (uncompressed or LZW) Lossless master survives migration
Raw converter intermediate 16-bit TIFF Lossless handoff between applications
Phone camera roll JPG (or HEIC) Storage and app compatibility

One more cost computation makes the archive case concrete. A 10,000-image family archive at 24 MP is about 700 GB as uncompressed TIFF and about 100 GB as JPG. Cloud backup at a typical $0.10 per GB per month (verify current rates with your provider) costs roughly $70 per month for the TIFF archive versus $10 for the JPG version β€” a $720 annual difference to preserve pixels nobody will re-edit. Institutions pay that for cultural heritage. Households usually should not, and a middle path works: keep the original camera files (which are already lossless) and store JPG derivatives for viewing.

FAQ

Does converting a JPG to TIFF restore the lost quality?

No. Converting a JPG to TIFF produces a lossless container holding already-degraded pixels, so the artifacts are locked in permanently. The conversion adds file size without adding information. Save to TIFF from the original source β€” camera raw, scan, or layered edit β€” never from a JPG.

Is TIFF always better quality than JPG?

Only for files that will be edited, printed large, or archived. For a finished image viewed on a screen, a high-quality JPG is visually identical and far smaller. The format preserves data; it does not improve an image that needs no further processing.

Why do print shops ask for TIFF instead of JPG?

Large-format printing magnifies compression artifacts that are invisible on screen, and TIFF avoids them while supporting 16-bit data for smooth gradients. Shops also want flattened, CMYK or RGB TIFFs at a specified resolution. Confirm the shop's exact requirements β€” color space, bit depth, and compression β€” before sending a file.

How much bigger is a TIFF than a JPG, exactly?

For a 24-megapixel photo, an uncompressed TIFF is about 70 MB against 8–15 MB for a high-quality JPG β€” roughly five to nine times larger. LZW or ZIP compression narrows the gap to about two to four times without losing data. The ratio depends on image content; detailed images compress less.

Can I open a TIFF in a browser or on my phone?

Most browsers do not display TIFF, and many phone photo apps ignore it. TIFF is a working and archival format, not a delivery format. Convert to JPG before sharing, uploading, or texting β€” that is what the recipients' devices expect.

Does saving a JPG at maximum quality make it lossless?

No. JPG is lossy at every quality setting; the highest setting simply quantizes less aggressively. Each additional save re-compresses and accumulates artifacts. The only lossless option in the JPG family's neighborhood is JPEG 2000's lossless mode, which is a different format and not widely supported.

What is a JPEG-compressed TIFF, and should I use it?

It is a TIFF container holding lossy JPEG data β€” it inherits compression artifacts while keeping TIFF's size overhead. It exists for specialized uses like some fax and document workflows. For lossless storage, set compression to None, LZW, or ZIP instead.

Is TIFF going away?

No. The format is maintained through Adobe's specification and is the standard preservation master in archival guidance such as NARA's digitization recommendations. Newer lossless formats like PNG and JPEG XL exist, but TIFF's installed base in scanning, printing, and publishing keeps it in active use.