Why Three Cameras Produce Three Different Files
Every camera manufacturer has a proprietary RAW format. Canon writes CR2 (older bodies) and CR3 (2018+). Nikon writes NEF. Sony writes ARW. Fuji writes RAF. Pentax writes PEF. Olympus writes ORF. None of them are interchangeable.
This isn't a case of "all RAW is the same data with different file extensions." Each format encodes the sensor's color filter array, white balance presets, lens profile hints, and metadata in a structure unique to that manufacturer. Adobe has to write a separate decoder for each one.
The practical result: when you upgrade your camera, you might find Lightroom Classic refuses to open your new files until you update Camera Raw. Our RAW conversion guide has the full table of which versions support which sensors. This post focuses on the workflow problem, not the format anatomy.
What's Actually In a RAW File
Open a CR3 from a Canon R5 in a hex editor. You'll find:
- A small embedded JPG preview (about 800x600, used for thumbnails)
- A second larger JPG preview (about 2400x1600, used in the camera's playback)
- The actual sensor data (a Bayer-pattern grid of single-channel pixel values)
- Metadata (lens model, ISO, shutter, GPS, lens profile)
- Color matrix and white balance hints
When you import to Lightroom, the catalog shows the embedded JPG preview instantly. The actual demosaic happens lazily when you open the file in Develop. This is why import is fast but "1:1 previews" take ages to generate.
| Camera body | Format | Year | Lightroom needs |
|---|---|---|---|
| Canon 5D Mark III | CR2 | 2012 | Camera Raw 7+ |
| Canon R5 | CR3 | 2020 | Camera Raw 12.4+ |
| Canon R5 Mark II | CR3 | 2024 | Camera Raw 16.0+ |
| Nikon D850 | NEF | 2017 | Camera Raw 10+ |
| Nikon Z9 | NEF | 2021 | Camera Raw 14.0+ |
| Sony A7 IV | ARW | 2021 | Camera Raw 14.1+ |
| Sony A7R V | ARW | 2022 | Camera Raw 15.1+ |
The "Lightroom needs" column is what trips photographers up. A 2024 camera with a 2022 Lightroom install will import the file, show the JPG preview, then fail when you try to develop it.
DNG: The Universal Backup Plan
Adobe's DNG (Digital Negative) is the open RAW format. It's a wrapper that can hold the demosaiced sensor data from any camera, plus the metadata, plus an optional embedded JPG preview.
The case for converting RAW to DNG on import:
- Future compatibility: 20 years from now, DNG will still open. Proprietary RAW formats may not.
- Smaller files: DNG often saves 10-15% on file size with lossless compression
- Consistent metadata: All your edits and ratings live in the file itself, not in sidecar XMP files
- Camera Raw version independence: A DNG converted today opens in any future Lightroom
The case against:
- One-way conversion (you can't recover the original CR3 binary)
- Slower import (the conversion runs at import time)
- Some advanced features (Canon Dual Pixel RAW, Sony Pixel Shift) don't survive
Pro Tip: If you keep both your originals and DNGs, treat the DNG as your working copy and the CR3/NEF/ARW as cold storage. Adobe's free DNG Converter lets you batch-convert without touching the originals.
Lightroom Import Settings That Matter
The Import dialog has 6 settings that affect downstream performance. Most photographers ignore them.
- Build Previews. "Standard" is wrong for most workflows. Pick "1:1" for small libraries, "Embedded & Sidecar" for fast import with deferred 1:1 generation.
- Build Smart Previews. Adds 5% file size, lets you edit when the originals are offline. Worth it if you work from a laptop.
- Don't Import Suspected Duplicates. On. Always.
- Make a Second Copy To. Use a separate drive for redundancy.
- Apply Develop Settings. A starting preset (e.g., your default white balance + camera profile) saves a lot of clicks downstream.
- Apply Metadata. Adds copyright, contact info, keywords on import.
For weddings or events where you'll cull a lot, "Embedded & Sidecar" preview is fastest. For fine-art work where you'll edit everything, "1:1" is worth the import wait.
When Lightroom Renders RAW Wrong
Common symptoms that aren't a corrupt file:
Symptom: Colors look flat or wrong on import, then snap to "correct" after a second.
Cause: Lightroom is showing the camera's embedded JPG preview, then replacing it with Adobe's demosaic. The two interpretations differ.
Fix: Apply a Camera Profile (Camera Standard, Camera Vivid, etc.) to match the camera's interpretation.
Symptom: Highlights clip to pink or purple.
Cause: White balance interaction with highlight recovery on a saturated channel.
Fix: Reduce white balance temperature, then bring highlights down before applying the camera profile.
Symptom: Shadows show banding or posterization.
Cause: 8-bit working space when the file is 14-bit.
Fix: Set Lightroom Classic > Preferences > External Editing to ProPhoto RGB / 16-bit. The default is sRGB / 8-bit, which discards information.
Symptom: Lens correction does nothing.
Cause: Lens profile not auto-detected (often happens with adapted lenses or third-party glass).
Fix: Manually select the profile or apply Adobe's Generic profile.
Converting RAW Outside Lightroom
If Lightroom doesn't support your camera yet, or if you need a quick JPG without opening the catalog:
- Our ARW to JPG converter handles Sony files
- Our CR3 converter handles modern Canon files
- Our DNG to JPG converter handles already-converted DNGs
- Our image converter hub lists all 49 supported image formats
For batch processing, the batch processing guide covers folder-of-RAWs workflows.
RAW + DNG Hybrid Workflow
The setup that survived two laptop migrations and a Lightroom version jump:
- Import RAW files (CR3 in our case) to a "Camera Originals" folder. Read-only after import.
- Lightroom auto-converts to DNG on import, writes DNG to a separate working folder.
- Edit DNGs in Lightroom Classic.
- Export final JPGs to a "Delivered" folder.
- Catalog backs up to a NAS nightly.
- Camera Originals back up to cloud cold storage (Backblaze B2 or equivalent).
This costs about 2.3x the storage of a pure RAW workflow, but the catalog stays portable and the originals stay untouched.
File Size Math
For a 45-megapixel RAW from a Canon R5:
| Format | Typical size | Notes |
|---|---|---|
| CR3 (camera default) | 50-65 MB | Canon's lossy compression |
| CR3 (lossless) | 80-95 MB | Some bodies offer this |
| DNG (lossless) | 55-70 MB | Adobe's lossless compression |
| DNG (lossy) | 18-25 MB | Optional, visually identical |
| 16-bit TIFF | 270 MB | Demosaiced master |
| JPG (q=90) | 12-18 MB | Final delivery |
| AVIF (q=63) | 4-7 MB | Web delivery |
A wedding shoot of 1500 RAWs is 75 GB on the camera, ~85 GB after DNG conversion, ~25 GB delivered as JPG, and ~9 GB if you also publish AVIF. Storage adds up.
XMP Sidecars and What Breaks Them
When Lightroom edits a CR3, it doesn't modify the file. It writes the edits to either:
- The Lightroom catalog (default, faster, brittle if the catalog corrupts)
- An XMP sidecar file next to the original (slower, portable across machines)
Turn on "Automatically write changes into XMP" in Catalog Settings if you ever move files between machines. It's the difference between "rebuild from XMP" and "lose all edits" when something goes wrong.
DNG files don't need sidecars. The XMP data lives inside the DNG.
Frequently Asked Questions
Why does my CR3 file open as a tiny preview in macOS Preview?
macOS Preview shows the embedded JPG, not the actual RAW data. It can't demosaic. To see the real image, open in Photos, Lightroom, Capture One, or convert with our CR3 to JPG converter.
Should I shoot CR3 lossless or compressed?
For most editing workflows, the compressed CR3 is fine. Lossless matters when you push exposure several stops or pull aggressive shadow recovery. The file size penalty (about 30%) is real, the visual benefit at sane edit ranges is small.
Can I convert old CR2 files to CR3?
No, and you wouldn't want to. CR3 is a newer container with different encoding. The two formats are not interconvertible. If you need future compatibility, convert to DNG instead. Our DNG converter handles the path.
Why does Lightroom say "the file appears to be unsupported or damaged"?
Either your Camera Raw version doesn't recognize this camera (check the table above), or the file is genuinely damaged. Try our RAW converter hub as a quick test. If we can decode it, the file is fine and you need a Camera Raw update.
Is there a free alternative to Lightroom for RAW editing?
Darktable (open source) and RawTherapee (open source) both demosaic any RAW format with broad camera support. Capture One has a free "Express" edition for some Sony and Fuji bodies. None match Lightroom's catalog UX, but they all handle RAW well.
What's the difference between "Edit a Copy with Lightroom Adjustments" and "Edit Original"?
"Edit a Copy with Lightroom Adjustments" sends a TIFF or PSD to Photoshop with all your Lightroom edits baked in. "Edit Original" sends the raw bytes with no edits applied. For round-trip work, always use "Edit a Copy with Lightroom Adjustments."
Related Reading
Bottom Line
CR3, NEF, and ARW each need a Camera Raw decoder for your specific camera body. Update Lightroom whenever you buy a new body. Convert to DNG for archival. Keep originals as cold storage. If Lightroom can't open something, our RAW image converter covers the formats it doesn't yet support.



