TIFF files are commonly used for storing images that must survive editing, repeated saving, and professional printing without visible quality loss, which is why photographers and graphic designers reach for them when the final output matters more than file size. A TIFF, short for Tagged Image File Format, holds image data with lossless or no compression, optional layers and alpha channels, and high bit depth, so a single file can carry a full-resolution master rather than a delivery copy. The trade-off is size, and the boundary is simple: TIFF suits archival, print, and production work; JPEG suits sending pictures to people.
What a TIFF File Actually Stores That a JPEG Cannot
A TIFF is a container built to hold image data, and its specifications allow several ways to package that data: uncompressed, LZW-compressed, or ZIP-compressed. A single 8-bit RGB TIFF from a 24-megapixel camera occupies roughly 69 megabytes uncompressed, and the same image saved with LZW compression typically drops to around 40 to 50 megabytes depending on subject matter, since smooth skies compress far better than foliage. Those figures follow directly from the pixel count and bit depth: 24 million pixels Γ 3 channels Γ 1 byte per channel.
The format's real distinction is what it can carry beyond pixels. TIFF supports 16-bit and 32-bit per channel data, embedded ICC color profiles, alpha transparency, multiple pages, and layers when saved from applications like Adobe Photoshop. A photographer editing a 16-bit TIFF can push shadows two or three stops before banding appears in a gradient sky, whereas an 8-bit JPEG already holds only 256 tones per channel and starts showing steps after a similar adjustment.
JPEG, by contrast, discards information during compression and again every time the file is saved. Reopening and resaving a JPEG at quality 90 repeatedly degrades fine detail measurably, which is why retouchers treat it as a delivery format rather than a working format. TIFF's lossless compression preserves every original value, so the hundredth save looks like the first.
One commonly confused term is RAW. A RAW file from a camera is proprietary sensor data, not a TIFF, though many cameras and converters can output TIFF as an intermediate format. A common misuse is treating a TIFF as a web image: browsers historically did not display TIFF at all, and some still do not, so sending one to a client expecting a preview often produces a broken or missing image.
Why Photographers Choose TIFF for Masters, Not Memory Cards
Photographers generally do not shoot TIFF in-camera, despite the option existing on many DSLRs and mirrorless bodies, because the buffer fills fast and cards fill faster. A 45-megapixel camera writing uncompressed TIFF produces roughly 130-megabyte files per frame, and a 128-gigabyte card that holds thousands of RAW files might hold under a thousand TIFFs. RAW also preserves the sensor's full dynamic range and white balance latitude, which a converted TIFF has already partially baked in.
The TIFF preference appears after conversion. When a RAW converter exports a 16-bit TIFF, the photographer gains a working file that opens in any editor, carries the color profile, and survives round trips through Photoshop, Capture One, or Affinity Photo without re-demosaicing. Scanning workflows lean on TIFF for the same reason: a drum or flatbed scan of a negative saved as TIFF keeps every captured tone, while a JPEG scan throws away shadow detail that cannot be recovered later.
Archival practice reinforces the choice. Museums and image archives commonly specify TIFF for preservation masters, and the Library of Congress lists TIFF among its recommended formats for still images, citing its wide support and lossless options. A family archive of 5,000 scanned photographs saved as TIFF at 20 megabytes each consumes 100 gigabytes, which a two-terabyte external drive holds comfortably; the same archive at JPEG quality 85 might take 15 gigabytes but loses the ability to re-edit.
There is a failure case worth knowing. A photographer who exports a 16-bit TIFF, then saves over it from an 8-bit editing session, can silently lose bit depth without any warning dialog in some applications, and the loss only shows when a later adjustment bands. Checking the file's bit depth in the image information panel before archiving catches this.
Why Graphic Designers Rely on TIFF for Print Production
Print production rewards formats that do not surprise the press operator, and TIFF delivers predictable color and resolution. A designer placing a TIFF into Adobe InDesign or Illustrator keeps the embedded ICC profile, so a CMYK TIFF prepared for coated stock prints as expected, while a JPEG's chroma subsampling can soften small type and fine lines. At 300 pixels per inch, an A4 page needs roughly 2480 Γ 3508 pixels, about 26 megapixels, which as an uncompressed CMYK TIFF runs near 104 megabytes.
TIFF also carries transparency and layers in workflows where a flattened handoff is not acceptable. A packaging designer sending a dieline artwork file to a printer may supply a layered TIFF so the prepress team can toggle a spot varnish layer or adjust a die line without reopening the source application. JPEG cannot store layers at all, and PNG, while lossless, has weaker support for CMYK and spot color workflows in some RIP software.
File size becomes a production cost, not just a storage annoyance. Sending a 104-megabyte TIFF through a print house's file transfer portal at a typical 100 megabits per second upload takes about eight seconds of pure transfer time but often minutes with portal overhead; a designer who batches twenty such files learns to schedule uploads rather than fire them off mid-conversation. Compression choice matters here too: LZW TIFF typically halves the size with no quality loss, and press RIPs accept it without complaint.
The edge scenario is the client who asks for "the original file" and cannot open a TIFF on a phone. Designers routinely keep two deliverables: the TIFF master for print and a JPEG or PDF for approval, and the mix-up happens when the approval copy gets sent to press or the master gets sent to a client's email.
Uncompressed, LZW, ZIP, and JPEG-in-TIFF: Choosing the Right Flavor
TIFF is not one compression setting but a family, and the choice changes file size, compatibility, and risk. The table below compares the common options as they behave in Photoshop and in print RIPs.
| TIFF variant | Typical size vs. uncompressed | Quality impact | Best use | Watch out for |
|---|---|---|---|---|
| Uncompressed | 100% | None | Maximum-compatibility archival masters | Large files; slow transfers |
| LZW | 50β60% | None (lossless) | Print handoffs, general archive | Slightly slower decode on old RIPs |
| ZIP (Deflate) | 40β55% | None (lossless) | Photoshop default for layered files | Some legacy software lacks support |
| JPEG-in-TIFF | 10β25% | Lossy | Rare; quick proofs only | Defeats the point of TIFF |
| PackBits | 60β80% | None | Simple graphics, line art | Poor on photographs |
A designer picking between LZW and ZIP for a 104-megabyte CMYK piece sees a difference of perhaps 10 megabytes, which rarely justifies changing defaults; Photoshop's ZIP default is a fine choice for layered work. The JPEG-in-TIFF option exists but undermines the format's purpose, and few production shops accept it. For scanned line art, PackBits can outperform LZW because flat black-and-white regions compress extremely well, a detail that matters when digitizing 500 pages of ink drawings.
One version-specific wrinkle: BigTIFF, introduced to handle files over 4 gigabytes, is not readable by every older application. A 32-bit-per-channel scan of a large-format transparency can exceed that limit, and a designer who receives one should confirm the receiving software's BigTIFF support before promising delivery.
TIFF vs. PSD vs. PNG vs. JPEG: A Side-by-Side Comparison
Designers choosing a working format weigh four candidates, and the right answer depends on what happens next.
| Feature | TIFF | PSD | PNG | JPEG |
|---|---|---|---|---|
| Compression | Lossless (LZW/ZIP) or none | Proprietary, lossless | Lossless | Lossy |
| Layers | Yes, when saved from Photoshop | Yes, native | No | No |
| Bit depth | Up to 32-bit/channel | Up to 32-bit/channel | 8 or 16-bit | 8-bit |
| CMYK support | Yes | Yes | Limited | Yes (as CMYK JPEG) |
| Web browser display | Historically no | No | Yes | Yes |
| Typical 24MP RGB size | 40β70 MB | 30β60 MB | 15β40 MB | 3β8 MB |
| Print RIP acceptance | Broad | Broad | Mixed | Broad |
The verdict splits by role. Use PSD while the file still needs layer editing inside Adobe's ecosystem, because PSD remains the native Photoshop format and preserves adjustment layers, smart objects, and text. Use TIFF for the archived master or the handoff to a printer, because it opens in more software and carries the profile reliably. Use PNG for web graphics with transparency, and JPEG for photographs delivered to people who will view them on screens. Anyone who does not use Adobe applications should skip PSD entirely, since its support elsewhere is inconsistent.
The Real Costs: Storage, Bandwidth, and Time With Numbers
The cost of TIFF is mostly arithmetic, and it is worth running before committing an archive or a deadline. A wedding photographer delivering 600 final images at 45 megabytes per TIFF master needs about 27 gigabytes for that one wedding; fifty weddings a year reaches 1.35 terabytes, and a mirrored backup doubles it. Cloud storage at commonly quoted consumer rates of roughly $6 per terabyte per month for the first tier would cost about $16 monthly for that archive before any egress fees, a figure worth confirming on the provider's current pricing page.
Time costs show up in transfers and saves. Saving a layered 500-megabyte TIFF to a spinning external drive can take several seconds and to a network share much longer, while the same document as a flattened JPEG saves almost instantly. Batch-converting 1,000 RAW files to 16-bit TIFF on a mid-range desktop typically runs 20 to 40 minutes depending on processor and disk, and the resulting folder might occupy 60 gigabytes, which changes how a photographer plans cards and drives on a shoot.
There is a subtler cost: compatibility debt. A studio that archives everything as layered TIFFs from one application version may find that a future version reinterprets an adjustment or drops a layer effect, and the file opens slightly differently years later. Flattening a copy alongside the layered master costs storage but protects against that.
For a small design shop, the working rule that keeps costs sane is two-tier storage: fast local drives for active TIFFs, cheaper archival drives or cloud cold storage for finished ones, with JPEG proxies for browsing. A 4-terabyte external drive at current commodity prices holds roughly 60,000 average 45-megabyte TIFFs, which is enough for years of moderate output and costs less than a single lens.
Bit Depth, Color Profiles, and Other Settings That Decide Quality
Most quality failures in TIFF workflows trace back to settings chosen at export, not to the format itself. Sixteen-bit-per-channel export preserves the tonal headroom that makes TIFF worth using; exporting 8-bit and then editing defeats much of the purpose, though 8-bit remains fine for images that will not be adjusted again. Assigning the correct ICC profile, such as Adobe RGB or ProPhoto RGB for photography and a CMYK profile matched to the press condition for print, prevents the washed-out or oversaturated results that come from mismatched profiles.
Resolution and resampling deserve the same attention. A TIFF exported at 72 pixels per inch is a web-resolution file wearing an archival extension, and designers who receive one for print must either resample upward, which softens detail, or request the original. Setting the export to 300 pixels per inch at final print dimensions avoids the conversation.
Alpha channels and spot colors are where TIFF shows flexibility that JPEG lacks. A product cutout saved as TIFF with an alpha channel drops cleanly into layout software, and a TIFF carrying a spot channel can be separated at the RIP. Checking that these channels survive export is a quick visual step in the channels panel.
One common misconception is that TIFF files are inherently print-ready. They are not: a TIFF in sRGB at 150 pixels per inch will print, but softly, and a TIFF with no embedded profile invites the printer to guess. The format preserves what you put in it, including mistakes.
Common Mistakes, Compatibility Traps, and How to Recover
The most frequent TIFF mistake is sending one where a JPEG was expected. Email clients, phone galleries, and many web upload forms reject or fail to preview TIFF, and the recipient's silence is often confusion rather than rudeness. Converting to JPEG or PDF before sending, while keeping the TIFF as the master, prevents the loop.
A second trap is opening a TIFF in software that silently converts it. Some basic viewers load a 16-bit TIFF as 8-bit and save it back that way, and the file loses headroom with no warning. Verifying bit depth after any round trip through unfamiliar software catches this before it becomes permanent.
Recovery scenarios are worth rehearsing. If a layered TIFF opens flattened, the layers may have been saved with a compression option the receiving application does not support; reopening in the original application and resaving with ZIP usually restores them. If a TIFF will not open at all, checking whether it is BigTIFF or uses an unusual compression scheme narrows the cause quickly, and a format-conversion utility can often rescue the pixels even when metadata is damaged.
Backup discipline matters more with TIFF than with JPEG simply because the files are large and the temptation to skip a copy is higher. A three-copy rule, with one copy off-site, protects an archive that represents months of work; a single failed drive holding 1.35 terabytes of wedding masters is not a hypothetical loss.
FAQ
Do TIFF files work on the web or in browsers?
Most browsers still do not render TIFF natively, and Safari's long-standing support has been inconsistent across versions, so a TIFF linked from a web page usually fails to display for visitors. Convert to JPEG, PNG, or WebP for anything that loads in a browser, and keep the TIFF as the source. Some content management systems generate a preview automatically, but relying on that produces broken images when the plugin is missing.
Is TIFF better than RAW for photography?
TIFF is not better than RAW, and the two serve different stages: RAW holds the sensor's full data and must be converted, while TIFF holds a converted, editable image that opens anywhere. A 16-bit TIFF retains most of the tonal latitude a photographer needs after conversion, but a RAW file still offers more white-balance and highlight-recovery room. Many photographers keep the RAW as the negative and the TIFF as the printable master.
Why is my TIFF file so much larger than the JPEG version?
The size gap comes from compression method and bit depth: a 24-megapixel uncompressed 8-bit RGB TIFF is about 69 megabytes, while a high-quality JPEG of the same image is typically 3 to 8 megabytes. If the TIFF is 16-bit, double the uncompressed figure to roughly 138 megabytes. LZW or ZIP compression on the TIFF usually cuts it by 40 to 60 percent, still far above JPEG.
Can I convert a JPEG to TIFF and get the quality back?
No. Converting a JPEG to TIFF changes the container, not the data: the compression artifacts and lost detail stay exactly where they were, and the TIFF is simply a larger file holding the same degraded image. Conversion is useful for workflow uniformity or for avoiding further JPEG degradation during editing, never for recovering quality.
What bit depth should I use when saving a TIFF?
Use 16-bit per channel when the image will receive further tonal editing, such as shadow lifting or curve adjustments, and 8-bit when it is finished and file size matters. Print workflows often accept either, but 16-bit preserves smooth gradients through adjustments. Check the receiving software's support if the file is headed to an older RIP.
Does LZW compression damage a TIFF?
LZW is lossless, so the pixels are identical to an uncompressed save and no quality is lost. The only downsides are slightly slower decoding in very old software and marginally larger files than ZIP on some images. For archival and print handoffs, LZW is a safe default that meaningfully reduces size.
How long will a TIFF archive last?
TIFF's longevity comes from its open, widely documented specification and broad software support, and archives such as the Library of Congress recommend it for preservation masters, but no format guarantees forever. Long-term safety depends on verified copies, periodic checksums, and migration to new media every few years. Store at least three copies, one off-site, and test that they open on current software.
Why do printers sometimes ask for TIFF instead of PDF?
Printers request TIFF when they want the image data without PDF's transparency-flattening or font-embedding variables, particularly for large-format and packaging work. A TIFF at final resolution with an embedded CMYK profile gives the prepress team predictable, editable pixels. PDF remains the standard for page layouts with text; TIFF handles single images and handoffs where the RIP wants raw raster data.