A 3D LUT can be a creative look or a camera Log conversion; the file extension alone does not tell you which. Decide from the LUT’s intended input and output color spaces. For a creative grading LUT, darktable’s documented default is after filmic rgb, applied to a neutral image. For a camera Log conversion, the manual describes a different placement: between demosaic and input color profile, with the input profile aligned to the LUT’s output. That Log workflow is explicitly marked as not yet tested in the manual, so treat it as a documented use case, not a verified result.
Identify the LUT and choose its position
Use these steps when you have a .cube, .3dl, HaldCLUT .png, or .gmz file and its role is unclear:
- Check the LUT maker’s documentation for the expected input and produced output. Look for a camera Log encoding such as F-Log or S-Log3, and whether the output is linear raw data or another space darktable can interpret. A label like “cinematic” is not enough to establish a technical conversion.
- If the file is meant to grade an already-developed, neutral image, treat it as a creative LUT. Keep the documented default placement after filmic rgb. Avoid applying another specific look before it if you want to judge the LUT against a neutral starting image.
- If the file is explicitly a camera Log conversion, use the manual’s placement guidance instead: put LUT 3D between demosaic and input color profile, then set the input color profile to match the LUT output. Do not leave it in the normal creative-look position and assume the two arrangements are interchangeable.
- For the ordinary grading use, set application color space to the space the LUT was built for. darktable says Cube files are usually associated with Rec. 709 and most other LUTs with sRGB; those are clues, not a substitute for the LUT’s actual specification. In the described Log arrangement, this control is no longer available.
- Compare the image before and after the LUT under the intended placement. Check whether the source is being interpreted as the LUT expects and whether the output is consistent with the next color-management stage. Judge the image, not just the module position or LUT filename.
The LUT 3D module reference documents the module’s input/output roles, default use, and Log placement. It also explains that application color space selects the color space for which the LUT was built; it does not identify whether the LUT is a camera conversion or a creative look.
LUT identity and workflow worksheet
The entries below are hypothetical examples for recording a decision, not guaranteed darktable results. Replace the example specifications with information from your actual LUT. The final column is an author-recommended acceptance check, not a documented automatic test.
| Hypothetical LUT and evidence | Intended input → output | Placement and application color space | Review observation and decision |
|---|---|---|---|
| “Studio mood.cube”; maker says Rec. 709 input and Rec. 709 output; no camera Log encoding named | Rec. 709 image → Rec. 709 graded image | After filmic rgb; choose Rec. 709 only if confirmed as the LUT’s built-for space | Compare against the neutral baseline. If the effect is unexpectedly extreme, recheck input assumptions and LUT documentation before changing placement. |
| “Camera X S-Log3 conversion”; hypothetical maker notes say S-Log3 input and linear output | S-Log3 camera data → linear output | Between demosaic and input color profile; match that profile to the stated output; application color space unavailable in this arrangement | Confirm the selected source and output-profile description match the LUT notes. The manual marks this workflow untested, so an inconclusive render is not proof of a working conversion. |
For either row, note the source file, the LUT’s stated input/output, the relevant module positions, and a visible before/after observation. A useful comparison asks whether the result is plausible for the declared transform and whether a mismatch appears before or after the LUT. It does not claim that the transform recovers image information absent from the source.
Limits and next steps when it fails
A LUT file can be valid yet incompatible with the image or workflow. darktable warns that incompatible grading LUTs may not produce their advertised look. The module also clips values outside [0,1]; reducing the input range may be necessary, but that is a separate issue from identifying the LUT’s purpose. Do not assume an extreme result proves the LUT is a Log converter, or that changing application color space repairs a camera Log pipeline.
If the result is wrong, return to the LUT’s documented input/output contract. If that information is missing, ask the supplier for it or treat the file’s purpose as unknown; do not infer it from its filename or extension. For a suspected Log conversion, verify the documented encoding and output profile, then record the result as inconclusive if you cannot establish that the input and profile match. The official manual itself warns that this use case has not yet been tested. For a creative LUT, confirm the intended application color space and neutral starting point before investigating other causes.
darktable does not store uncompressed LUT data in the database or XMP sidecar; the LUT file remains at its configured path. When sharing an edit, make sure the recipient also has the same LUT file available. See the module reference’s file storage and LUT handling notes for that limitation.
Common questions
Does `.cube` mean the LUT is a creative look? No. The extension identifies a supported file format, not the intended color-space transform. Check the maker’s input/output description.
Is application color space the same as LUT input and output? No. It is a selectable setting for the color space a LUT was built for in the ordinary module use. The camera Log arrangement described in the manual disables that choice and instead requires attention to the LUT output and input profile.
Has the camera Log placement been verified here? No. This guide has not run darktable tests. The manual describes the placement but explicitly says the use case has not yet been tested. Treat worksheet outcomes as hypothetical acceptance checks, not measured results.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.