
A linked Affinity document, PDF, SVG, PSD or EPS is not edited directly as an embedded document inside the parent layout. Edit the authorized source, then update the linked resource through Resource Manager. Embedded editing is a different workflow with different consequences.
Key Takeaways
- Confirm whether the placed object is linked or embedded.
- Update linked documents from their source file.
- Do not embed solely to make an edit button appear without reviewing the tradeoff.
Identify the placed document's role
Affinity's placing-content guide documents a layer-type indicator for embedded versus linked documents. It says external changes to the listed linked-document formats are reported as Modified in Resource Manager and can be updated there.
This distinction concerns placed documents. Do not generalize it into a claim that all linked photographs are uneditable by every Affinity feature. The application's current help describes separate image-editing workflows.
Make the correction at the source
For a hypothetical supplied event advertisement, ask the authorized designer to correct the date in the source file and save an approved revision. Select the placed object in the layout; the placing guide states that its Resource Manager entry is selected too, helping identify the resource. Open Document > Resource Manager, the route in the embedding/linking help. Confirm source filename and location before updating. Modified means external content changed but has not yet been brought into the layout; it does not mean the revision is approved. Update the selected resource through the manager, then compare the refreshed date in the layout with the actual approved source. Reopen that source independently if revision identity is uncertain. If automatic updates are enabled, it may already show the new file, so verify content rather than expecting a status transition.
The linked-content update guide provides context for the risks of confusing source updates with local overrides. Its commands belong to another application, so use Resource Manager for the current Affinity workflow.
If automatic updating is enabled, verify when external changes become visible. A live update is useful only when the team agrees which source revision is authoritative.
Consider embedding only with a reason
Affinity's embedding-versus-linking help explains portability and external dependencies. Embedded content travels inside the document, while linked content depends on its source location.
Embedding and interpreting a supplied PDF or other supported embedded document can change the native-data and passthrough workflow. Preserve the original before making that decision. Do not tell a collaborator that the embedded edit automatically changed the external source.
Inspect the handoff as a whole
Package required resources for an editable delivery using a clear folder structure; see the linked-image package guide. Verify that the linked source exists, not merely that a cached preview is visible. The missing-original guide illustrates that broader distinction.
A suitable acceptance rule is: the approved date appears, the correct source revision is linked, Resource Manager reflects the intended state and the exported proof matches. Review the actual export after updating, especially when supplied branding or page geometry is critical.
This is a documented source-management workflow with a hypothetical advertisement. It does not claim a resource was updated or that direct embedded editing is always the wrong production choice.
If the source owner cannot provide a correction immediately, keep the issue open in the review record. An interpreted local workaround should not silently replace an agreed native-source handoff.
Related tasks
- Why Does Updating Linked InDesign Content Undo My Local Changes?
- Why Are Images Missing When Someone Else Opens My InDesign or Photoshop Project?
- Why Can I See a Photo in Lightroom Classic but Not Export It?
Sources and scope
- Placing content: Source editing and Resource Manager updates for linked resources.
- Embedding vs linking: Resource Manager menu and external updates.
- Creating packages: Meaning of Modified status.
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.