
In darktable, copying an edit does not freeze its parameter values at that instant. The current manual states that a later paste uses the source image’s current state, including changes made after copying. If an approved treatment changes while you continue working on its source, the pasted result can therefore differ from the state someone approved.
Separate selecting modules from freezing values
The official copy and paste instructions describe this temporal behavior. Selective copy chooses which modules travel. It does not turn their copied values into an immutable approval snapshot. Also check the source selection: when several images are selected, the first selected image supplies the history.
Use one source and one destination for diagnosis. Record the source identity, selected modules and approved reference before touching a larger set. The shared-settings allowlist helps decide scope; the issue here is when those selected values are read, not simply which adjustments should travel.
Rehearse a visible change on disposable versions
Suppose a hypothetical product series has an approved neutral treatment. A photographer copies that treatment, then experiments with a warmer source before pasting onto the remaining views. A warmer destination is consistent with the documented live-source behavior, rather than proof that the application ignored Copy.
For a proposed rehearsal, use retained source files and disposable editing versions:
- Select only the intended source, identify one easily observed adjustment, and note its current value.
- Use selective copy for that adjustment. Keep the destination out of the selection at this stage.
- Change the selected source adjustment by a recognizable amount, noting the new value separately.
- Select the disposable destination and paste. Inspect the destination parameter as well as its appearance.
- Compare the observed value with the later source state. Do not infer the relationship from a thumbnail alone.
This rehearsal has not been executed for this guide. Keep it away from approved outputs and do not use an important destination as the experiment. A successful diagnostic only establishes this transfer relationship in the installed version; it does not approve the warmer treatment.
Establish a stable source for the real transfer
Return to the specifically retained source revision that represents the approved treatment. Stop editing that source while transferring it. Select its intended module subset, paste onto one representative destination, and compare both parameters and the agreed visual reference. Only expand the operation after that small check passes.
Use the approved-version handoff guide to identify which reference belongs to which revision. A rendered reference records appearance, while an application edit state records adjustable processing. Neither a familiar filename nor the earlier Copy gesture proves they still correspond.
Stop when the source revision cannot be established
If nobody can identify the approved source state, recover an explicit saved checkpoint or agree a new approval. Do not repeatedly paste and compensate the destinations until the set happens to look similar. The saved-document and undo distinction explains why a historical command list is not a dependable recovery file.
Accept the transfer when the recorded source state, selected modules and representative destination agree, and when excluded image-specific adjustments remain appropriate. Keep the source stable until the transfer is finished. This addresses a changing input relationship without claiming that all photographs should receive identical corrections.
Related tasks
- Which Photo Edits Should I Copy to a Whole Set, and Which Should Stay Individual?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Why Can I Edit My Saved Layers but Not Undo Yesterday’s Steps?
Sources and scope
- darktable user manual: copy: Paste reads the current source state, including changes after copying; multiple selection uses the first-selected source.
Based on the current online darktable manual reviewed October 31, 2026. Check the installed release. Examples and acceptance checks are proposed, not hands-on test results.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.