
An Affinity picture frame has one child marked as its framed content. Dropping another object onto the frame's name can replace that child. To add a watermark as decoration, add it as a regular child in the expanded frame hierarchy instead.
Key Takeaways
- Framed content and ordinary child decorations have different roles.
- The Layers panel's drop highlight matters.
- Inspect the hierarchy before exporting or replacing anything else.
Understand the replacement gesture
The current Affinity picture-frame help distinguishes a row highlight on the frame's name from the line used to add a regular child. Dropping onto the highlighted frame name makes the new object framed content and replaces an existing framed-content child.
If the watermark appears while the photograph disappears, inspect the Layers panel before assuming the photo file was deleted. Preserve the current document and use the normal recovery history where appropriate rather than repeatedly dragging more objects into the same target.
Add the decoration in the intended role
Expand the picture frame's row. Drag the watermark layer just below the frame's row and drop when the insertion line indicates a regular child position. Verify that the original photo retains its framed-content marker.
For a hypothetical client proof, the watermark should overlay the portrait while the portrait remains controlled by the frame's fit behavior. Do not use a replacement-image command to add a second visual layer.
The clipping-mask handoff guide offers general context for inspecting parent-child relationships, but Affinity's documented drop targets are the relevant controls here.
Check scaling and resource behavior
The framed image follows the frame's fitting policy. Regular children have their own ordinary scaling and constraint behavior. Resize cautiously and inspect whether the watermark's size and position still communicate its purpose.
If the watermark or photograph is linked, retain the required resources. Affinity's embedding-versus-linking guide explains why a linked file remains external. The project-package guide reinforces the separate need to preserve those dependencies.
Verify the visible derivative
Export a clearly named proof and open it outside the editor. Confirm that the photo remains visible, the watermark is legible and no unintended clipping hides either object. A flattened export is a different artifact from the layered source; the visible-composite guide illustrates that distinction.
A suitable acceptance record names the photo revision, watermark revision and intended frame relationship. Inspect the actual source hierarchy as well as the rendered image so a later replacement does not accidentally remove the decoration.
This is a documented layer-management workflow with a hypothetical proof. It does not establish ownership rights in the watermark or claim that a particular layer tree was tested.
For repeated proof revisions, retain the layer names and object roles consistently. A future editor should be able to identify the photo and decoration without recreating the original drag gesture.
Related tasks
- Does an Illustrator Clipping Mask Actually Remove the Artwork Outside the Crop?
- GIMP: New from Visible or Merge Visible Layers?
- Why Are Images Missing When Someone Else Opens My InDesign or Photoshop Project?
Sources and scope
- Picture frames: Framed-content child slot versus ordinary child decoration placement.
Guidance follows current Affinity desktop documentation. Worked examples and checks are proposed, not measured software tests.
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.