Operation
Selects how source metadata is applied.
Choose merge, replace or clear according to whether existing keys must survive.
← Fusion node reference
Utility / DataIntermediate
CopyMetadata
Metadata merge and replacement
Copies metadata between images with merge, replace or clear behavior while leaving the image pixels conceptually separate from the metadata operation.
CopyMetadata
DaVinci Resolve · Fusion
CopyMetadata is useful when an image-processing branch needs to preserve, replace or combine metadata carried by another source.
Overview
What CopyMetadata does
CopyMetadata is useful when an image-processing branch needs to preserve, replace or combine metadata carried by another source.
Mental model
The pixels are the picture; metadata is the attached note card. CopyMetadata changes the note card without needing to rebuild the picture itself.
Common uses
Preserve source metadata after image processing
Merge metadata from another branch
Replace conflicting metadata
Clear metadata before delivery or testing
Flow anatomy
Inputs & outputs
The port structure shows how this node fits into a Fusion graph.
Input
Primary image whose metadata will be modified.
Metadata Source
Image supplying metadata to copy or merge.
CopyMetadata
Fusion node
Output
Primary image with metadata updated according to the selected operation.
Inspector
Important parameters
Start with these controls before reaching for more complicated workarounds.
Merge (Replace Duplicates)
Merges metadata and lets incoming duplicate keys overwrite existing values.
Useful when the metadata source should take precedence.
Merge (Preserve Duplicates)
Merges while keeping existing values for duplicate keys.
Use when the primary image's metadata should win conflicts.
Replace
Replaces the current metadata set with the source set.
Appropriate when a clean metadata handoff is required.
Clear
Removes metadata.
Useful for debugging or when downstream delivery requires a minimal metadata payload.
Practical setup
A reliable workflow
- 1
Decide which branch should own the image pixels and which should own the metadata.
- 2
Connect both sources.
- 3
Choose merge, replace or clear behavior.
- 4
Inspect important metadata keys after the operation.
- 5
Keep metadata handling near the stage where it is actually needed.
Typical node chain
Image + Metadata Source→
CopyMetadata→
Image + Updated Metadata
Examples
Where this node fits in real work
Restore source metadata
Copy original metadata onto a heavily processed image branch.
Processed Image + Original SourceCopyMetadataMediaOut
Sanitize a branch
Clear metadata before a technical export test.
ImageCopyMetadata ClearMediaOut
Troubleshooting
Common mistakes
Using Replace when only one key needed updating
Ignoring duplicate-key precedence
Assuming metadata changes alter the image pixels
Production notes
Practical tips
Document which metadata keys matter to the pipeline.
Use explicit merge semantics so later operators know which source wins conflicts.
Related nodes