Initializing... drag & drop files here
Supports: DCR
DCR is the Kodak Digital Camera RAW format — the sensor file written by Kodak's professional DCS-series DSLRs and digital backs in the early 2000s, before white balance, exposure, or tone is applied. AVIF (AV1 Image File Format) is a modern, highly compressed delivery image built on the AV1 codec. Converting DCR to AVIF turns a 20-year-old professional Kodak RAW into a small, web-ready picture that current browsers can open directly — useful because Kodak left the DSLR business in 2005 and the software that reads DCR is steadily thinning. The two tables below explain what each format actually is, then a short walkthrough covers the conversion and what it does to the RAW.
| 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 |
| Structure | TIFF-based, losslessly compressed sensor data |
| 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 viewer or decoder |
| Status | Orphaned — Kodak exited professional DSLRs in May 2005 |
| Decoders today | Adobe Camera Raw / Lightroom, RawTherapee, dcraw |
| Note | Unrelated to the Adobe/Macromedia Director (Shockwave) .dcr |
| Property | Value |
|---|---|
| Full name | AV1 Image File Format |
| Type | Compressed delivery image (rendered, finished picture) |
| Released | February 19, 2019 (AOMedia, spec v1.0.0) |
| Codec / container | AV1 still image inside the HEIF / ISO-BMFF container |
| Compression | Lossy or lossless; ~30-50% smaller than JPEG at similar quality |
| Bit depth | Supports 8, 10, and 12-bit, plus HDR and wide gamut |
| Editing latitude | None — the render is baked in |
| Native browser support | Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+ (~93% of users, per caniuse) |
| Metadata | HEIF container can carry Exif and XMP |
| Best for | Fast-loading web and app delivery at small file sizes |
.DCR file 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.One thing here is easy to miss: the DCR is rendered before it ever becomes an AVIF, and that step is one-way. A DCR stores high-bit sensor data with wide editing latitude — you can recover highlights, shift white balance, and push exposure long after the shot. To write an AVIF, that sensor data is demosaiced into ordinary 8-bit pixels and the current white balance and exposure are baked in; the latitude does not survive into the AVIF, exactly as it would not into a JPEG. The visible result can look excellent, often indistinguishable at normal viewing sizes, but you are now holding a finished picture, not a RAW. Because these files came from a camera line Kodak discontinued in 2005 and may be the only copy you have, the right move is to render a copy to AVIF for the web and keep the original .DCR as your editable master. If you want control over the look, adjust white balance and exposure in a RAW editor that reads DCR first, then convert the result.
No, and the shared extension trips people up. This converter handles the Kodak Digital Camera RAW image — a TIFF-based RAW written by Kodak DCS Pro DSLRs and digital backs. It is unrelated to the Adobe/Macromedia Director (Shockwave) .dcr, which is a compiled web-multimedia file, not a photo. If your file is an old web animation rather than a camera RAW, this tool is not the right one.
DCR is not uncompressed — a common myth. It is a TIFF-based RAW that stores the sensor data with lossless compression at high bit depth (12-14 bit is typical for the Kodak DCS Pro line), so no image information is discarded in the file itself. AVIF is different on both counts: it holds a rendered, demosaiced picture, and for web delivery it is normally encoded with lossy compression to reach its small size. So you move from a losslessly stored RAW to a compact, finished image — a deliberate trade of editing latitude and file size for reach.
Yes. 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. To make an AVIF the converter renders that data into ordinary pixels with the current settings baked in, so once it is an AVIF you are editing a finished image, not the RAW. Keep your original .DCR if you may still want to edit it, particularly since it came from a camera Kodak no longer makes — for many of these archives the DCR is irreplaceable.
Two reasons. First, reach and size: AVIF is supported by Chrome 85+, Firefox 93+, Safari 16.4+, and Edge 121+ — roughly 93% of users can view it natively, per caniuse — and at similar quality AVIF files are typically about 30-50% smaller than JPEG. Second, longevity: DCR decoders are thinning, while AVIF is a current, actively maintained AOMedia format. Rendering your Kodak archives into AVIF now, while RAW decoders for DCR still exist, gives you a small, broadly viewable copy and removes the dependence on increasingly rare DCR software. If you also want maximum compatibility, keep a DCR to JPG copy alongside it.
The AVIF format itself supports 10- and 12-bit color and HDR, which is one of its advantages over JPEG. This converter targets a standard, broadly compatible AVIF suitable for web delivery rather than an HDR-graded master, so treat the output as a standard-dynamic-range copy. If you specifically need a wide-gamut, high-bit-depth file for editing or print, render the DCR to a lossless format instead — DCR to TIFF preserves high bit depth without lossy compression.
DCR is the RAW format of the Kodak DCS Pro line — DSLR bodies such as the DCS 720x, DCS 760, and the full-frame DCS Pro 14n and SLR/n, plus digital backs like the DCS Pro Back series. Kodak discontinued these professional DSLRs in May 2005 to focus on compact cameras and medium-format backs, which is why DCR is effectively an orphaned format. It matters because Kodak's own software is gone, so the sensible move is to render these files into a current format now, while RAW decoders for DCR still exist, rather than risk being unable to open them later.
It depends on the file's job. Convert to AVIF when you want the smallest web- or app-ready picture and your audience is on current browsers. If you need universal compatibility — email, older devices, any image viewer — DCR to JPG opens essentially everywhere. If you are building a print or lossless-editing master, DCR to TIFF gives you a high-bit-depth, losslessly compressed file. Whichever you pick, keep the original .DCR as your archival master; the rendered output never carries the RAW's full latitude.
Your file is uploaded over an encrypted connection, rendered and encoded into AVIF on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, 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, not your device. In our testing, a full-resolution DCR converted to AVIF at the "Very High" preset produced a file a fraction of the original's size while staying visually sharp at normal viewing sizes. For irreplaceable originals, archive the .DCR alongside the AVIF you publish.