Supported RAW formats and cameras

The 24 camera RAW formats Raw Photo Editor opens, how files are decoded in your browser, how orientation and the camera crop are handled, and what is not supported.

4 min read Updated Open the editor →

Raw Photo Editor opens camera RAW files with 24 extensions, covering Canon, Nikon, Sony, Fujifilm, Olympus and OM System, Panasonic, Pentax, Leica, phone DNGs and several medium-format makers. Files are decoded by LibRaw, the open-source library behind many RAW converters, compiled to WebAssembly (libraw-wasm 1.6.0, LibRaw 0.22) and run inside your browser. If LibRaw supports your camera and the extension is on the list below, the file should open in the editor.

The drop area lists every extension the editor accepts.

Accepted file types

MakerExtensions
Canon.CR3, .CR2, .CRW
Nikon.NEF, .NRW
Sony.ARW, .SR2, .SRF
Fujifilm.RAF
Olympus, OM System.ORF, .ORI
Panasonic.RW2
Leica.RWL, .DNG
Pentax.PEF, .DNG
Samsung.SRW
Konica Minolta.MRW
Kodak.DCR, .KDC
Epson.ERF
Hasselblad.3FR
Mamiya.MEF
Phase One.IIQ
Leaf.MOS
Phones and DNG converters.DNG

Upper or lower case doesn’t matter. Each extension on the list was checked by decoding a real file before it was added. Some cameras use another maker’s format: the Hasselblad Lunar, for example, writes Sony .ARW files, and the hibiscus photo in this guide is one of them.

The file picker behind Open and Choose file shows only these extensions. A file with any other extension, dropped or picked with the picker’s “All files” option, isn’t opened, and a message says why.

How a file is decoded

Opening a file shows Building preview while LibRaw turns the sensor data into a color image:

  • Demosaicing: AHD for the usual Bayer sensors, and Markesteijn (single pass) for Fujifilm X-Trans sensors.
  • Color: the camera’s own color matrix, converted to sRGB primaries, at 16 bits per channel.
  • White balance: the one the camera recorded. Temp and Tint at 0 mean “as shot”; see white balance.
  • Brightness: no automatic brightening and no hidden tone curve. The photo opens flat, often around a stop darker than the camera’s JPEG, so that you decide where the highlights end. The one automatic adjustment is a DNG file’s BaselineExposure value, an exposure offset written by the camera or phone, which the editor adds to Exposure without moving the slider.

Most files take a few seconds. Fujifilm X-Trans files take longer: 10 to 15 seconds for a 26-megapixel file.

After decoding, the editor keeps two versions of the photo: the full-resolution image, used at 100% and for export, and a working preview of 3072 pixels on the long edge that keeps sliders responsive. Viewing and comparing explains when each one is on screen.

Orientation and the camera crop

Photos taken in portrait orientation open upright, following the orientation the camera recorded.

Many sensors record a thin border of pixels that the camera itself crops away. The editor trims it to the image area the camera declares, so a Canon EOS 750D file opens at 6000 × 4000 pixels, the size the camera states. When a file declares no such area, the editor shows everything LibRaw outputs. This trim is not part of your edit and you can’t undo it; your own framing is done with crop and rotate.

The image size is shown in the info bar above the photo.

DNG files from phones

Phones that save RAW photos as DNG produce files the editor accepts like any other DNG. Phone DNGs often use BaselineExposure to set their intended brightness, and the editor applies it, so they open closer to how the phone meant them to look than other RAW files do.

Very large files

The full-resolution image is held in memory at 16 bits per channel: about 150 MB for a 24-megapixel file, about 600 MB for 100 megapixels, plus the decoder’s working memory while it runs and a copy on the graphics card when you zoom in. Files of 60 to 100 megapixels need a few gigabytes of free memory. On a machine without it, the browser may stop the tab.

The graphics card also limits size. If it can’t hold the full image for a zoomed view, the view falls back to the working preview; if it can’t render the full size for export, the export is made smaller and the editor tells you so. See export.

When a file doesn’t open

If LibRaw can’t read a file, the canvas shows Decode failed with the reason, for example The file may be unsupported or corrupted., and a Try another file button. The usual causes:

  • A camera newer than LibRaw 0.22. A new model, or a new compression mode on an existing one, can appear before LibRaw learns to read it.
  • A damaged copy. A transfer from the card that was interrupted leaves a file that looks right but ends early. Copy it again.
  • A file that isn’t a camera original, such as one exported by another program under a RAW extension.

Converting the file to DNG with a converter such as Adobe DNG Converter is a common workaround for very new cameras.

What isn’t supported

For everything else the editor can’t do yet, see requirements and limitations. To make your first edit, go back to getting started.