ShootFlow · camera raw support · as of 2026-11-18

Which camera RAW files can ShootFlow develop without Adobe DNG Converter?

Fourteen formats, read directly: DNG, Canon CRW, CR2 and CR3, Sony ARW, Nikon NEF (and Coolpix NRW), Olympus ORF, Panasonic RW2, Samsung SRW, Pentax PEF, Fujifilm RAF, including X-Trans and Fujifilm's compressed modes, Minolta and Konica Minolta MRW, Phase One IIQ from the P+ and IQ medium-format backs, and Hasselblad 3FR with the .fff files Phocus writes. Leica's RWL is a Lumix RW2 under another name and is read too.

Each reader was checked on real camera files from public sample collections against LibRaw 0.22, the open-source decoder behind most raw software. For every format, every sensor value read was equal to LibRaw's, and so were the as-shot white balance and colour filter layout. Source: the project's evaluation records, one per format.

See every camera checked Develop a file What ShootFlow does

Jump to a format

What was checked, format by format

"Sensor values equal" means every value decoded from the file matched LibRaw 0.22 (read through rawpy). The real files came from the public metadata-extractor-images collection and raw.pixls.us (CC0).

FormatCameras checked on real filesResultStill refused
CR353 real files of 23 cameras: EOS R, RP, M50 and M50 Mark II, M6 Mark II, M200, 250D, 90D, 850D, R100, R5 and R5 Mark II, R6, R6 Mark II and R6 Mark III, R7, R8, R10, R50 and R50 V, R3, 1D X Mark III and PowerShot V1 (full quality and C-RAW, full frame and crop)Every sensor value equal on every file (up to 47.9 M each; 986.8 M on the 39 checked 2026-11-18), and the white balance on all of them. The 2018-2023 bodies store two tiles side by side, read since 2026-11-18. On the R6 Mark III and PowerShot V1, LibRaw 0.22.2 reads a wrong black level; ShootFlow uses the 512 the camera states and its masked pixels showNone known. Tiles stacked one above another: no body seen writes them (C-RAW tiles so stacked disagree with LibRaw at the seam rows).
CR2Canon 350D, 600D, 70D, 7D, 5D Mark II0 sensor values different on all five; 5D Mark II render a median 0.61 of an 8-bit step from LibRaw'ssRAW and mRAW
CRW20 real files from 15 Canon bodies of 2000-2004: EOS D30, D60, 10D, 300D (Digital Rebel); PowerShot G2, G3, G5, G6, Pro1, S30, S40, S45, S50, S60, S70Every sensor value equal on all 20 (114.0 M), and the white balance wherever the file records oneThe four-colour (cyan, magenta, yellow, green) PowerShot G1, Pro70 and Pro90 IS
ARWSony DSLR-A500, NEX-5N, NEX-7, A5000, A7 III, A7 IV (lossless)133.9 M sensor values equalARW 1.0 (DSLR-A100), SR2 and SRF
NEF18 real NEFs from 16 Nikon bodies, D70 to D810, D3400 to D5600, D5, 1 J5, Z 6IIEvery decoded sensor value equal on 18 of 18High-efficiency NEF (Z bodies)
NRW (Nikon Coolpix)13 real Coolpix files: P6000, P7000, P7100, P7700, P7800, P330, P340, P950, P1000, B700, A1000, E8800 (NEF) and Coolpix AEvery sensor value, black level, white balance and CFA equal on 13 of 13 (since 2026-11-18)None seen
RAFFujifilm X-E1, X-E2, FinePix S5500; lossless compressed X-T2, X-H1, X-T3, X-S10, GFX 50S; lossy compressed X-S10, X-E4Every sensor value equal on all ten files, X-Trans includedSuperCCD
RW225 Panasonic Lumix bodies: 4 older (GF1, GF3, GF7, LX7), 12 from 2017 on (GH5, G9, S1R, S5 ...) and every current one (GH6, GH7, G9 II, S5 II, S5 IIX, S1 II, S1 II E, S1R II, S9); and Leica's RWL from the Lumix-built D-LUX (Typ 109) and V-LUX (Typ 114)1,308 M sensor values equal across three generations of the format. The S1R II’s 177 MP mode, which LibRaw 0.22 cannot open, is checked by its tile seams insteadThe older 16-bit RawFormat 2 and 3
ORF18 Olympus and OM System bodies, C-5050 Zoom to OM-1219.6 M sensor values equalE-1/E-300-era layouts and high-res composites
SRWSamsung Galaxy NX, NX1, NX20, NX300090.5 M sensor values equalNone seen yet
PEFPentax K-1 Mark II (the only real PEF at hand)36.6 M sensor values equalUncompressed PEF and Pixel Shift
MRW9 Minolta and Konica Minolta bodies of 2001-2005: DiMAGE 7, 7i, 7Hi, A1, A2, A200; Dynax 7D, Maxxum 7D and Alpha-7 DigitalEvery sensor value equal on all nine (54.1 M), and the white balance and CFAThe DiMAGE Z2's headerless .MRW
DCR (Kodak)Kodak DCS Pro SLR/n (the only public DCR at hand)Every sensor value equal (13.6 M), and the white level, white balance and CFAKodak DC-series compressions (262, 32867) and KDC
IIQ (Phase One)24 real files of 16 backs and cameras: H 25, P25, P20+, P25+, P30, P45+, P65+, IQ140, IQ150, IQ180, IQ3 100MP, IQ4 150MP, iXM-100 (IIQ L); IQ180, iXU180, IQ3 100MP, iXM-100, iXM-RS150F (IIQ S); IQ4 150MP, IQ3 100MP, IQ3 100MP Trichromatic (16-bit IIQ L)Every sensor value equal on all twenty-four (1,769 M, up to 154 M a file), and the white balance and CFA. Develops with the colour matrix the file carries, no .dcp neededThe uncompressed formats. Phase One's per-sensor calibration (flat fields, defect maps, sensor-half curves) is applied since 2026-11-19 and matches LibRaw to within 3 codes outside dead columns on ten backs
3FR10 Hasselblad bodies and backs: H3D, H4D-60, X1D, X1D II 50C, X2D 100C, CFV II 50C, CFV 100C, CFV-50c, CFV, Ixpress CF132Every sensor value equal on all ten (561.5 M), and the white balance and CFA. Develops with the file's own colour matrix, no profile needed (since 2026-11-18)Multi-shot frames
FFF (Phocus)11 files from 9 Hasselblad bodies and backs: CFV-50, CFV-50c, H4D-40, H4D-50, H5D-40, H5D-50c, H6D-100c, X1D II 50C, X2D 100CEvery sensor value equal on all eleven (713.7 M), and the stored white balance and CFA. Two frames shot as both 3FR and .FFF develop to the same colour within 0.0001 (since 2026-11-18)H4D-40 and H6D-100c files with no matrix need a .dcp; Imacon scanner .FFF files
DNGConverted Nikon and Canon files; camera DNGs from a Leica T, Pentax Q-S1, LG Nexus 5X, Google Pixel 3 XL, DJI Phantom 4Within one 8-bit step of LibRaw's render; camera DNGs a median 0.02 to 0.11 of a stepLossy, deflate and floating-point DNG; four-colour sensors

Develop a file

A DNG carries its own colour matrices, and so do a Phase One IIQ and a Hasselblad 3FR (and most Phocus .fff files). The other formats need the camera's .dcp profile. Adobe's free DNG Converter installs one per body, and RawTherapee and dcamprof write them too. Pass a folder and ShootFlow picks the right profile for each camera.

git clone https://github.com/Duncan-Haywood/oss-monorepo
cd oss-monorepo/ventures/photo-editing

# ~/profiles holds the .dcp profiles; the right one is picked per camera
PYTHONPATH=src python3 -m shootflow.cli develop DSCF0001.RAF \
  --dcp ~/profiles --out masters

The output is a neutral 16-bit TIFF master with as-shot white balance and sRGB, meant as the starting point for your LUT or grade. It runs on Python's standard library alone. Install numpy and the optional C decoders build on first use, and most files then read in under two seconds.

What it is not

Questions

Can I open Canon CR3 files without Adobe DNG Converter?

Yes. ShootFlow reads full-quality CR3 and the smaller C-RAW setting directly, from the 2018 EOS M50 and EOS R through the 90D, M6 Mark II and R100 to the R5 Mark II and R6 Mark III. On 53 real files of 23 Canon cameras every sensor value matched LibRaw 0.22. You still need the camera's .dcp profile for colour.

Can it develop old Minolta and Konica Minolta MRW files?

Yes, from 2026-11-18, without converting them to DNG. On nine real MRW files (DiMAGE 7, 7i, 7Hi, A1, A2 and A200, and the Dynax 7D under all three of its names) every sensor value, the CFA and the as-shot white balance matched LibRaw 0.22. A file reads in a tenth of a second or less with numpy. The DiMAGE Z2 writes a file with no MRW header, and it is refused. Colour needs a .dcp profile for the camera.

Can it develop Kodak DCS Pro DCR files?

Yes, from 2026-11-18, without converting them to DNG. ShootFlow decodes Kodak's own compression (65000) and its linearisation table. On the one public DCR found, from a DCS Pro SLR/n, every sensor value, the white level, the CFA and the as-shot white balance matched LibRaw 0.22, and the frame reads in about a tenth of a second. Colour needs a .dcp profile for the camera. That is one file from one body, so other DCS Pro bodies are expected to work but have not been checked.

Can it develop Hasselblad 3FR files without Phocus?

Yes, from 2026-11-18. ShootFlow reads both kinds of 3FR: the uncompressed files of the X1D, X1D II, X2D and CFV backs, and the H-series and older backs' files in Hasselblad's own lossless compression. On ten real files from ten bodies and backs, from an Ixpress CF132 and H3D to a 100 MP X2D, every sensor value, the CFA and the as-shot white balance matched LibRaw 0.22. A 3FR carries its own colour matrix, so it develops without a .dcp profile; a profile can still be passed. A 100 MP file reads in about half a second with the optional C decoder. Multi-shot frames are refused.

Does it read Phocus .fff files?

Yes, from 2026-11-18. Phocus writes the same sensor data as a 3FR, but newer versions multiply the red and blue values by the file's AnalogBalance and leave the white-balance neutral as it was. Read as the DNG specification reads it, that gives a slight colour cast (LibRaw shows it too). A digital gain leaves gaps in the values, so ShootFlow can tell which files carry it, and it scales the neutral by the same gains only in those files. Two frames on raw.pixls.us exist as both a 3FR and an .fff, and with the scaling each .fff develops to its 3FR's colour within 0.0001 in chromaticity. Some .fff files carry no colour matrix. For the CFV-50c and X2D 100C, ShootFlow uses the matrix those bodies write into their own 3FRs. H4D-40 and H6D-100c files without a matrix need the camera's .dcp profile.

Does it read Fujifilm X-Trans RAF files, including compressed ones?

Yes: uncompressed, lossless compressed and lossy compressed RAFs, X-Trans and GFX Bayer. On ten real files from nine bodies every sensor value matched LibRaw. X-Trans files are demosaiced with a directional method written for the 6x6 layout.

Which newer Nikon and Panasonic files does it not read yet?

Nikon's high-efficiency NEF from Z bodies, and Panasonic's old 16-bit RawFormat 2 and 3. Those files are refused with a message to convert to DNG first. Coolpix NRW files (P6000 to P1000, B700, A1000) and the older E-series Coolpix NEFs are read directly since 2026-11-18.

Can I still develop old Canon CRW files from a 10D, 300D or PowerShot G5?

Yes, from 2026-11-16, without converting them to DNG. On 20 real CRW files from 15 Canon bodies (EOS D30, D60, 10D, 300D and the PowerShot G2 to G6, Pro1 and S30 to S70) every sensor value matched LibRaw 0.22, and so did the as-shot white balance wherever the file records one. When a PowerShot was set to Auto white balance the file keeps no balance for the shot, so none is applied and the report says so. The four-colour G1, Pro70 and Pro90 IS are refused. A file takes 2 to 5 seconds to read. Colour needs a .dcp profile for the camera, such as the ones Adobe DNG Converter installs for the cameras it supports.

Can it develop Phase One IIQ files without Capture One?

Yes, IIQ L files, from 2026-11-18. On ten real files from the H 25, P25, P20+, P25+, P30, P45+, P65+, IQ140, IQ150 and IQ3 100MP every one of 342.7 M sensor values, the colour pattern and the as-shot white balance matched LibRaw 0.22, and a 100 MP file reads in under a second with the optional C decoder. Unlike the other non-DNG formats, an IIQ carries its own colour matrix, so it develops with no .dcp profile. IIQ S, the smaller setting the iXU and iXM aerial cameras use, reads too, from later the same day: on six real files from the IQ180, iXU180, IQ3 100MP, iXM-100 and iXM-RS150F every one of 546.9 M sensor values matched LibRaw, and a 154 MP frame reads in 1.2 seconds. The 16-bit IIQ L of the IQ4 150MP, the IQ3 100MP and the Trichromatic reads too, from that evening: on all four public files every one of 520 M sensor values matched LibRaw, and a 150 MP file reads in about 1.3 seconds. On the IQ4 the colour matrix in the file and LibRaw's own disagree a good deal on saturated colours (a cyan-blue sky against a lavender one); ShootFlow keeps the file's matrix, and a .dcp overrides it. From 2026-11-19 it also applies the calibration each back writes into its files, as Capture One does: flat fields, defect maps and the curves that even out the sensor's halves and tiles. On ten backs the result matched LibRaw's calibrated render to within 3 of 65,535 levels on every sensor value outside the columns the file marks dead. Those columns are filled in from their neighbours in a different way from LibRaw.

Does it read Leica RWL files?

Yes, from 2026-11-16. Leica's D-LUX, V-LUX and C-LUX are built by Panasonic and write the same file as a Lumix under another name. On a real D-LUX (Typ 109) and V-LUX (Typ 114) file every one of 32.7 M sensor values, the white balance, black level, colour pattern and crop matched LibRaw 0.22. Colour needs Adobe's .dcp for the Leica model.

Will the card copy leave behind raw files it cannot develop?

No, from 2026-11-16. The copy takes every common raw format (Canon CRW, Nikon Coolpix NRW, Sigma X3F, Phase One IIQ, Kodak DCR and others), HEIF and HIF stills, MXF and M2TS video and XMP sidecars, and lists any other file it leaves on the card, so you see it before formatting the card. Formats it cannot develop are still culled from the preview the camera embedded, and stop at the grade with a message to convert to DNG.

Are my photos uploaded anywhere?

No. ShootFlow runs on your own computer and only reads your raw files. It never changes them.

What does it cost?

Nothing. It is open source under the MIT licence.

Privacy and usage

This page has no scripts, cookies or analytics of its own, and records nothing about you.

Disclaimer

Early-stage software. Keep your original raw files and your own backups; do not use it as the only copy of anything. Camera and software names are trademarks of their owners and are used only to say which files are read; ShootFlow is not affiliated with or endorsed by Adobe, Canon, Fujifilm, Hasselblad, Nikon, OM Digital Solutions, Panasonic, Pentax/Ricoh, Phase One, Samsung, Sony or the LibRaw project.

No warranty. This software is provided free and as-is, without warranty of any kind, express or implied. You are responsible for reviewing and verifying its output before relying on it. To the maximum extent permitted by law, the authors accept no liability for any loss or damage arising from its use.