TIFF vs DNG vs CR2 — comparing professional camera formats
Compare TIFF, Adobe DNG, and vendor RAW formats (CR2 / NEF / ARW) for professional photo workflows, print submission, and long-term archival, across reversibility, vendor lock-in, editor support, and archive readiness.
Four axes for camera-workflow formats
Picking a format for professional camera work is not a quality ranking. Reversibility (the “RAW-ness”) decides how far you can push white balance, exposure, and tone curve later without breaking the image. Vendor lock-in drives long-term risk — what happens when you switch camera bodies, or when the manufacturer ends support for its converter? Editor compatibility is the everyday reality of which application opens the file: Lightroom, Capture One, RawTherapee, or the manufacturer’s own software (Canon DPP, Nikon NX Studio). Archival longevity is the question of whether you can still open the file in 10 or 20 years, which is paramount for commissioned work and historical records.
TIFF, DNG, and CR2 all share TIFF (Tagged Image File Format) as a structural base, but they target different jobs and differ in whether the payload is already developed pixels or raw sensor data. Confusing them breaks the workflow. We use Canon’s CR2 as the case study; Nikon NEF, Sony ARW, and Fujifilm RAF occupy the same “manufacturer-specific RAW” slot and have the same trade-offs.
Side-by-side comparison
| Property | TIFF | DNG | CR2 |
|---|---|---|---|
| Structural base | TIFF (original) | TIFF extended for RAW | TIFF-derived |
| Payload | Developed pixels | Raw sensor data + metadata | Raw sensor data + maker tags |
| Origin / year | Aldus, 1986 | Adobe, 2004 | Canon, 2004 |
| Vendor lock-in | None | None (Adobe open spec) | Yes (Canon) |
| Primary editors | Photoshop, most DTP tools | Lightroom, Camera Raw, RawTherapee | Canon DPP, Lightroom (model-dependent) |
| Compression | Uncompressed / LZW / Deflate / JPEG | Lossless (recommended) | Canon lossless |
| Typical size (24 MP) | 70-150 MB (16-bit uncompressed) | 25-35 MB | 25-35 MB |
| Primary use | Print delivery, archival, DTP | Long-term archival, editor handoff | In-the-moment development |
| Metadata richness | EXIF / IPTC / XMP | EXIF + Adobe-specific + embedded original RAW | EXIF + Canon Maker Notes |
TIFF is a general-purpose image container from 1986, supporting 16-bit depth, alpha channels, multi-page documents, and a wide range of colour profiles (sRGB, Adobe RGB, ProPhoto RGB, CMYK). The payload is already-developed pixels, so big tonal adjustments after the fact are out of scope. DNG (Digital Negative) is Adobe’s 2004 attempt at a vendor-neutral RAW standard, built on top of TIFF and carrying sensor data, white-balance hints, lens-correction data, and colour profiles. CR2 is Canon’s TIFF-derived proprietary RAW, also from 2004, with Canon Maker Notes for vendor-specific tags and a strong dependency on Canon DPP. Newer Canon bodies have moved to CR3 (structurally incompatible with CR2), making CR2 itself a slowly fading format.
Recommendations by use case
Immediate development after a shoot: stay in manufacturer RAW (CR2 / NEF / ARW / RAF). Vendor-specific white-balance, lens correction, and film simulations (Fujifilm Film Simulation, Nikon Picture Control) are best honoured by the vendor’s own software or by third parties with a licensing agreement (Capture One’s Fujifilm support, for example).
Long-term archival (still openable in 10 years): DNG. Adobe’s spec is publicly documented, with multiple independent implementations (Lightroom, Camera Raw, RawTherapee, darktable). When converting CR2 → DNG with Adobe DNG Converter, enable “Embed Original Raw File” — this packs the original CR2 inside the DNG so the operation is fully reversible, at the cost of roughly doubling the file size.
Print delivery and finished-image distribution: TIFF. 16-bit depth, Adobe RGB, embedded ICC profiles. Print shops that require CMYK conversion accept TIFF as a matter of course. Choose LZW or Deflate compression — picking JPEG inside TIFF makes it lossy and can introduce banding in print.
Editor-to-editor handoff (Lightroom → Capture One, etc.): TIFF (16-bit, lossless) is the safe default. DNG is ideal if the receiving editor supports it well, but third-party support varies in quality.
Web and social posting: convert to JPG / PNG / WebP first. Uploading RAW or TIFF directly is wasted bandwidth — every platform re-encodes to JPG anyway.
Working with RAW and TIFF in the browser
For quick previews of manufacturer RAW files, raw-convert converts CR2 / NEF / ARW / DNG / RAF to JPG or PNG entirely in the browser. It is thumbnail-based rather than a full development engine, so fine tonal control is out of scope — but it is enough for “send the client one preview before delivery” jobs. For TIFF specifically, tiff-convert converts to JPG / PNG / WebP and handles multi-page TIFFs (medical imaging, fax origin, DTP spreads). For routine cross-format work, combine with image-convert.
Four traps to watch for. (1) RAW files going dark. Canon DPP support ends, or a new DPP refuses to open old CR2 files — both have happened. For important shoots, convert to DNG at capture time and keep two copies. (2) DNG conversion can drop vendor-specific metadata. Adobe DNG Converter only preserves the publicly documented parts of the maker tags; undocumented fields (some AF point details, for example) may be lost. The “Embed Original Raw” option keeps the source file inside the DNG as insurance. (3) JPEG inside TIFF is lossy. “TIFF” alone does not guarantee lossless — the compression scheme inside does. Pick LZW or Deflate. (4) EXIF, GPS, and serial numbers ride along in every format. Before posting to social media or sending to a client, strip them with image-exif-strip. The implementation is published on GitHub, and the DevTools Network tab confirms that capture data never leaves your machine.