
Append in darktable’s history paste does not mean that every copied adjustment becomes a new independent instance. The manual describes matching by module instance name: a matching destination instance is replaced and placed at the top of the history. If there is no match, a new instance is created. Multiple occurrences also have a last-occurrence rule.
Identify the operation before changing names
Read the current copy and paste manual for the installed workflow. The documented append merge is different from export-time style application, where additional processing can be applied temporarily while rendering. Do not transfer the meaning of Append between those controls without checking their documentation.
List the relevant module instances in source and destination, including their names and intended roles. A destination called “background” and a source called “background” can carry different creative intentions despite a matching name. The batch-setting scope guide helps separate shared treatment from individual corrections, but it does not specify darktable’s instance merge behavior.
Build an instance-level comparison
Consider a hypothetical portrait with one broad exposure correction and a separately named local adjustment. Another portrait supplies a creative exposure treatment. The question is whether the intended destination correction should be replaced or whether a separate adjustment is required.
On disposable editing versions, make a short record:
| Item | Record before paste | Check after paste |
|---|---|---|
| Source | Selected module and instance name | Intended instance was transferred |
| Destination | Existing instance names and purpose | Which instance changed or was added |
| Overall image | Reference appearance and local boundaries | No unintended correction was lost |
Use selective copy and selective paste to limit this rehearsal. Inspect the resulting module list and values, not just the combined appearance. If several history entries represent the same module, the manual says append processes only the last occurrence. A longer source history is therefore not a promise of more destination instances.
Choose merge or replacement deliberately
If replacing the same named adjustment is intended, retain its earlier state and verify the new parameters. If the task requires a separate creative adjustment, use the application’s documented multiple-instance workflow and verify the resulting instance relationship on the small test. Do not rename every source module merely to avoid understanding what will merge.
Overwrite is a different and more consequential choice: it removes the destination history before inserting the copied stack. It should not be used as a casual workaround for an unexpected append merge. The editable-master handoff guide provides a useful distinction between preserving an editable source and delivering a rendering, though its layer examples do not define darktable’s controls.
Verify both the visible result and editing roles
The acceptance test is that each required destination role still exists and that the intended transferred treatment is the one affecting the image. Compare a local area and the whole image. A plausible overall brightness can conceal replacement of an image-specific adjustment.
Keep the approved reference identified throughout the exercise. If the source contains complex repeated instances or masks and the mapping is uncertain, stop at one disposable destination and consult the version-matched manual. These are proposed checks, not reported application tests, and they do not promise that transferring a local correction preserves its meaning on another photograph.
Related tasks
- Which Photo Edits Should I Copy to a Whole Set, and Which Should Stay Individual?
- What Is the Difference Between an Editable Artwork Master and a Flat PNG?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- darktable user manual: copy: Append matches instance names, replaces matches and processes last occurrences. Overwrite deletes destination history.
- darktable user manual: export: Export-time styles are temporary; append adds separate processing instances for export.
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.