Initializing... drag & drop files here
Supports: DCR
DCR is the Kodak Digital Camera RAW format — the unprocessed sensor file written by Kodak's professional DCS-series DSLRs and digital backs, before white balance, exposure, or tone is applied. TIFF is the long-standing professional raster format used for print, layout, and archival preservation masters. This conversion is a natural pairing for historical pro archives: DCR is itself built on the TIFF specification, so you are rendering one TIFF-lineage format into a flat, broadly readable TIFF that a print RIP or any imaging tool can open. The two tables below explain exactly what each format is, then a short walkthrough covers the conversion and the one setting that decides whether your TIFF is lossless.
| Property | Value |
|---|---|
| Full name | Kodak Digital Camera RAW |
| Type | Camera RAW still image (unprocessed sensor data) |
| Released | Early 2000s (Kodak DCS Pro era) |
| Cameras | DCS 720x, DCS 760, DCS Pro 14n, SLR/n, DCS Pro Back series |
| Structure | TIFF-based; sensor data compressed with lossless JPEG (like Canon CR2, Adobe DNG) |
| Bit depth | 12-14 bit per channel (typical for the DCS Pro line) |
| Editing latitude | Full — white balance, exposure, highlights recoverable |
| Native browser support | None — needs a RAW decoder |
| Status | Orphaned — Kodak exited professional DSLRs in May 2005 |
| Decoders today | Adobe Camera Raw / Lightroom, RawTherapee, dcraw; legacy Kodak DCS Photo Desk |
| Note | Unrelated to the Adobe/Macromedia Director (Shockwave) .dcr |
| Property | Value |
|---|---|
| Full name | Tagged Image File Format |
| Type | Rendered raster image (finished, demosaiced picture) |
| Released | First published by Aldus in 1986; TIFF 6.0 finalized June 3, 1992 |
| Maintained by | Adobe (acquired Aldus in 1994) |
| Compression | Selectable — None, LZW, Deflate, PackBits (all lossless); JPEG (lossy) |
| Bit depth | 8 or 16 bit per channel; the rendered output here is a standard high-fidelity TIFF |
| Editing latitude | None — the render is baked in |
| Native browser support | None in practice — TIFF is not a web format (Safari is the main exception, per MDN) |
| Best for | Print, page layout, and lossless archival preservation masters |
| Extension | .tiff or .tif — the same format; this page lets you pick either |
.dcr onto the page or click "+ Add Files" to browse — files straight off a DCS 720x, DCS 760, DCS Pro 14n, SLR/n, or a DCS Pro Back. You can queue several at once.No — this is the most common myth about DCR. Although DCR uses a TIFF-based container, the sensor data inside is compressed, and the compression is lossless JPEG (the same approach Canon's CR2 and Adobe's DNG use), so no image information is discarded in the file itself. "TIFF-based" describes the file's tagged structure, not that the pixels are stored raw and uncompressed. When you convert to a TIFF here, the output's lossless-versus-lossy status is decided entirely by the "Compression Type" you pick, not by DCR's heritage.
Only if you change the compression. This page defaults the "Compression Type" dropdown to JPEG, which writes a smaller but lossy file — the single most important thing for an archival TIFF is to switch it to LZW, Deflate, or PackBits, all of which are mathematically lossless and discard nothing at the encode step. Separately, the render that turns the DCR's Bayer mosaic into ordinary RGB pixels bakes in a default white balance and exposure, and that interpretation is the part you can no longer freely undo; with a lossless compression chosen, the pixel fidelity of that render is intact.
DCR is built on the TIFF specification — it uses the same tagged file structure — so in a structural sense you are rendering one TIFF-lineage format into another. But shared heritage does not mean the pixels copy across untouched: a DCR holds an undeveloped, high-bit Bayer mosaic, and the converter has to demosaic and develop it into finished RGB pixels before writing the TIFF. Whether that output is lossless rides on your "Compression Type" choice, not on the common TIFF lineage.
A DCR from the Kodak DCS Pro line typically carries 12-14 bit sensor data, and a TIFF can hold 16-bit channels with room to spare. This page, however, does not expose a bit-depth selector — it renders to a standard high-fidelity TIFF rather than letting you hand-pick 8-bit versus 16-bit. For most print and archival uses that rendered TIFF is plenty; if you specifically need a controlled 16-bit export for heavy grading, do that step from a RAW editor that reads DCR (Lightroom, RawTherapee, Capture One) and export the TIFF from there.
No. The 12-14 bit sensor data in a DCR is what lets you recover highlights, lift shadows, and reset white balance long after the shot. Making a TIFF renders that data into ordinary pixels with the current settings baked in, so even a lossless TIFF is a finished image, not a RAW — the latitude does not survive. Keep your original .dcr as the editable master, especially since it came from a camera Kodak discontinued in May 2005 and may be the only copy you have; treat the TIFF as a high-quality print, layout, or preservation copy.
The DCR stores a single, compactly compressed Bayer mosaic — one value per photosite behind a color filter array. A TIFF stores fully rendered RGB pixels, three color planes for every pixel, so even with lossless LZW or Deflate the file is substantially larger than the DCR it came from. That growth is expected and is the cost of holding a flat, finished image. If size matters more than archival fidelity, render a smaller DCR to JPG copy for sharing, or a modern DCR to AVIF copy for the web, and keep the TIFF as the preservation master.
None — .tiff and .tif are two spellings of the same Tagged Image File Format, a holdover from the old eight-dot-three filename limit, and this page produces the identical bytes either way. Use the extension selector to match whatever your software expects. If your workflow specifically wants the three-letter name, the DCR to TIF page outputs the same file with a .tif extension.
In our testing, a full-resolution Kodak DCS-series DCR rendered to a lossless LZW TIFF ran several times the size of the original RAW — normal for a flat RGB image. Your file is uploaded over an encrypted connection, rendered into a TIFF on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, and your photos are never shared or made public. The main practical limit on a big upload is its size and the time it takes to send, since DCR files from Kodak DCS Pro bodies often run tens of megabytes each. For irreplaceable originals, keep the .dcr archived alongside the TIFF you produce.