Open RAW files in GIMP with darktable: two reliable routes

Choose automatic RAW import or an explicit TIFF handover, with checks for missing importers, profiles and reusable development history.

Matte coastal photographs show a lighthouse and green headland with an orange back card and a blank SD card on cream.

To open a RAW file in GIMP 3, install darktable, restart GIMP and choose File → Open; a working RAW importer opens the photograph in darktable before returning a developed image to GIMP. For an edit you need to revisit, I'd develop the RAW in a normal darktable session, export a 16-bit TIFF and open that TIFF in GIMP. That route keeps a named handover file and avoids relying on the automatic import session to preserve your RAW adjustments.

GIMP handles the layers, masks and retouching after RAW development. Its RAW workflow uses a processor such as darktable or RawTherapee; opening the camera file doesn't turn GIMP into a RAW developer or transfer darktable's editable controls into a layer.

Choose the route before developing the photograph

The automatic importer is convenient when you want to get a supported RAW into GIMP quickly. The separate-file route gives you more control over the saved development, destination, dimensions and colour profile. Both end with rendered pixels in GIMP.

Your priorityRoute I'd chooseWhat to retain
Open one RAW and continue in GIMPGIMP's darktable importer, once discovery worksOriginal RAW and a new XCF project
Revisit exposure or colour development laterNormal darktable session → TIFF → GIMPRAW, its XMP sidecar, TIFF and XCF
Finish the edit while the bridge is failingExport TIFF from darktable independentlyA named TIFF that GIMP can open without the RAW importer

Before using the automatic route: darktable's GIMP integration returns a temporary EXR when you close its darkroom window. Existing edits from darktable's database can be included, but adjustments made during that GIMP invocation are not saved back to the database. Choose the normal-session route if you need those adjustments to remain reusable.

Check the exact camera and RAW mode

Copy the photograph from the card to a working folder and keep a backup before editing. Then open that copy in darktable on its own. If darktable can't develop it independently, changing GIMP's importer preference won't solve the decoding problem.

Check both the camera model and the recording mode against the darktable camera-support list and unsupported formats. An extension such as NEF, ARW or DNG doesn't establish support for every variant. The list explicitly excludes examples including Nikon high-efficiency NEF, Apple ProRAW DNG and some downsized Sony lossless RAW modes. A DNG extension isn't a universal workaround.

The support table also separates basic camera support, white-balance presets and noise profiles. A missing preset or noise profile is a different condition from an unreadable RAW. Record the exact filename, camera mode, GIMP version, darktable version and package source before investigating a failure; “both are installed” leaves several different faults unresolved.

Use the official darktable installation routes for your platform. If GIMP itself needs updating, follow the GIMP update instructions and confirm the version in the application you launch. An older troubleshooting post about GIMP 2.10 and darktable 4.x doesn't establish compatibility for your current pair.

Open RAW through GIMP's darktable importer

  1. Open darktable independently once. Confirm it can develop your RAW, then close it. Restart GIMP after installing darktable so its plug-in discovery can run again.
  2. Open GIMP's preferences. On Windows and Linux, use Edit → Preferences. On macOS, use Settings or Preferences in the GIMP application menu. Select Image Import & Export.
  3. Inspect Raw Image Importer. Look for the registered file-darktable plug-in. Select it if another registered RAW importer is currently chosen. If only a placeholder appears, work through the discovery checks below or use the TIFF route.
  4. Choose File → Open and select the camera RAW. With the bridge working, darktable opens the image in darkroom mode. This special invocation keeps you in darkroom; it isn't the normal library-management session.
  5. Develop the image, then close the darktable window. The bridge exports its temporary result and GIMP opens the rendered image. You don't need to find an “Edit in GIMP” command for this route.
  6. Save a new XCF in GIMP. Choose File → Save As, give the project a useful name and keep the original RAW separately. Check the imported colour and precision before building a large layer stack.

The RAW importer preference lists known plug-ins; it doesn't install darktable, repair an executable path or make a placeholder into a working importer. The row can show a full plug-in path rather than a friendly application name. Look for file-darktable within that path.

GIMP Raw Image Importer preferences with file-darktable selected above the file-raw-placeholder plug-in.
Find file-darktable in Raw Image Importer; the placeholder can remain listed, and choosing a row does not install or repair the RAW processor. Open the Raw Image Importer list at full size.

Finish the RAW decisions before the handover

I'd settle the photograph's exposure and colour balance before spending time on GIMP retouching. Changing the RAW development afterwards can change the texture and tone beneath every repair.

In darktable, exposure controls overall brightness. Adjust it for the photograph rather than copying an EV value from somebody else's example. For a scene-referred workflow, colour calibration works with the white balance module; don't disable the underlying white balance module simply because colour calibration is available.

Inspect bright edges and important fine detail before leaving darktable. Its highlight reconstruction works on clipped RAW channels, while profiled denoise uses camera sensor noise profiles. These are reasons to examine highlights and noise at this stage, not promises that a clipped sky or every noisy photograph can be recovered.

Stop when the developed base is suitable for the pixel edit you intend to make. A photograph that only needs RAW adjustments can be exported directly from darktable. GIMP earns its place when the job needs a composite, text, local cleanup or an editable arrangement of layers.

Keep the RAW development and export a TIFF

For this route, start darktable normally rather than opening it from GIMP. That distinction determines where the development history is retained.

The import controls distinguish adding existing files from copying them. When existing sidecars matter, that distinction also matters: darktable documents that copy & import does not read or copy an existing XMP, whereas adding an existing image can load its sidecar. Keep the source development files safe before changing your import route.

  1. Import from a stable location. In lighttable's import module, choose add to library for images already in their working folder. It registers the files without copying or moving them. To bring files from a card into a new folder, use the appropriate copying import route instead. Don't format the card until you have checked the copies and backup.
  2. Develop the RAW in darkroom. Make the exposure, colour and detail changes you want to retain. darktable stores development information in its database and, when sidecar writing is enabled, alongside the original as XMP.
  3. Check the sidecar before relying on it. In a normal session, darktable synchronises work to XMP without a separate Save command. Keep the RAW and matching XMP together. If you disabled sidecar creation, restore an appropriate sidecar setting and confirm the file exists before treating it as a backup.
  4. Select the finished image and open export. In darkroom, the current image is exported when no other filmstrip images are selected. Check the selection so you don't accidentally export a different group.
  5. Set the destination and TIFF options below. Use a separate folder or a distinctive name such as fern-developed.tif. Start the export and wait for the completed file before opening it in GIMP.

darktable's XMP sidecar holds metadata and processing history without modifying the RAW. Back up every sidecar associated with an edit you want to retain, including additional versions. An embedded history tag in an exported TIFF is a useful extra, but the export manual warns against relying on embedded history as the backup.

Use deliberate TIFF settings

In the export module, choose target storage: file on disk, file format: TIFF and bit depth: 16 bit. If pixel type is shown, choose unsigned integer for this standard photographic handover. The TIFF controls offer uncompressed or deflate compression; either avoids a lossy JPEG intermediate. I'd keep the first handover simple and use on conflict: create unique filename so a new export can't silently replace an earlier base.

Under the size controls, select pixel dimensions and set both maximum width and maximum height to 0 to retain the image's dimensions after cropping. Zero means no constraint on that dimension. It doesn't undo a crop or restore pixels you excluded during development.

Choose the output profile deliberately. For a straightforward web-bound edit, I'd use sRGB, which darktable recommends for general interchange. A wider-gamut workflow can use another suitable profile if you keep that profile consistent through the handover. Selecting image settings uses the individual image's output-profile setting; it isn't a guarantee of sRGB. These size, collision and profile controls are defined in the darktable export settings, and the output-profile module embeds a supported profile for other applications.

Check the image GIMP receives

Open the exported TIFF with File → Open in GIMP. Confirm the subject, crop, pixel dimensions and colour before retouching. A successful open proves the separate rendered-file route works even if the automatic RAW bridge still fails.

If GIMP asks about the embedded colour profile, Keep preserves it; a deliberate conversion changes the pixels into the chosen working space. GIMP's file-open colour policy can also perform that choice automatically. When the image suddenly looks wrong, inspect the imported profile and display policy first. Don't assign sRGB to a wide-gamut image just to make a warning disappear: assigning a profile changes how existing colour values are interpreted; converting to a profile changes the values to preserve the intended appearance.

In current GIMP 3.2, inspect Image → Encoding for precision. Older tutorials may call this submenu Precision. A 16-bit TIFF gives you a high-bit-depth handover; don't reduce it to 8-bit just to match an old tutorial. GIMP's encoding controls distinguish integer and floating-point precision. Moving a file to higher precision doesn't recreate clipped detail or recover RAW controls from a rendered TIFF.

Save the project as fern-edit.xcf, then begin the layer-mask work or object cleanup. Keep an untouched developed base layer available while you work. GIMP's Save and Export commands serve different files: XCF keeps the project structure, while JPEG or PNG is a separate delivery image. XCF doesn't preserve the Undo history after closing.

Find the failing stage when RAW import doesn't work

SymptomCheckNext action
darktable itself can't open the RAWExact camera model, compressed/special RAW mode and complete local copyResolve decoding or file support first; GIMP's importer isn't the failing stage.
No RAW loader; only a placeholderRunning GIMP copy, registered importer and installed package typeRestart after installation, check executable discovery, or export TIFF independently.
darktable opens, but GIMP receives no imageExact versions and error; whether a manually exported TIFF opensUse TIFF to finish the edit; report the handover failure with its actual environment.
Returned image has the wrong size or cropRAW crop and both export maximum dimensionsCorrect those settings and export a separately named TIFF.
RAW adjustments are missing next timeAutomatic GIMP invocation versus normal session; database and XMPDevelop normally and verify the sidecar; don't assume the automatic session saved a reusable history.

Executable discovery differs by platform. GIMP's RAW loader searches application bundles on macOS and registered application paths on Windows, with PATH as a fallback. On Linux, check the package's integration instructions as well as whether darktable launches from the environment GIMP uses. Finding it in one terminal doesn't prove another packaged application's environment can invoke it.

With Flatpak, applications run in separate sandboxes with restricted host access. A host-installed darktable isn't automatically available to a sandboxed GIMP. I'd use the named TIFF handover while checking the particular packages, rather than granting broad permissions or copying old binaries into GIMP 3.

Historical bug reports are useful when their conditions match. For example, a GIMP 2.10.36/darktable 4.6 failure was tracked towards a 4.6.1 fix. It doesn't justify downgrading a modern pair to those versions. Keep the exact error and distinguish “can't find darktable” from “darktable opened but failed to return an image”. Reinstalling both applications before making that distinction can leave the same problem in place.

Keep the development, project and final image separate

Before archiving the job, confirm that the RAW and its XMP sidecars are backed up, the named TIFF opens, and the XCF reopens with the layers you expect. Then export a separate JPEG or PNG and open that delivery file independently to check its dimensions, appearance and intended metadata.

A TIFF doesn't carry darktable's modules into GIMP as editable RAW controls, and saving an XCF doesn't write your pixel edits back into the camera RAW. If you redevelop the original, make a new TIFF and check how the changed crop, brightness and texture affect existing masks and repairs before replacing the old base. Keep the earlier XCF until the revised edit is complete.

Elena Morris

Elena Morris

Elena Morris is the GIMP image-editing and compositing editor at TheGIMP.net. She writes about selections, masks and layers, restrained retouching, compositing and export.