
Current Affinity embeds content dragged from a web browser or an application other than the operating system's file manager, regardless of Prefer Linked. A placement policy cannot create a stable external file reference where the drag source does not provide that workflow.
Key Takeaways
- Browser drag-and-drop is a documented exception to Prefer Linked.
- Confirm the resource type in the actual document.
- Obtain an authorized stable source before planning linked updates.
Identify how the image arrived
The Affinity embedding/linking guide explicitly documents this browser and non-file-manager exception. Check the placement route as well as the document policy before assuming a resource setting was ignored.
For a hypothetical design board, dragging a preview from a licensed image service may place a visible embedded image. That does not establish that it is the approved full-resolution source or that its license permits the intended publication.
Obtain the correct source first
Use the authorized asset delivery route and save the approved source in the project's intended resource folder. Record its revision and license or permission information according to the project's normal process. Do not scrape or bypass a service's access controls to create a linked file.
The missing-original guide illustrates why a visible preview is not proof that the production original is available. Resolve that source question before optimizing document size.
Convert the resource deliberately
The same Affinity guide documents Document > Resource Manager and Make Linked or Embed. When making an embedded resource linked, the application can use an existing original location or ask where to save an external file. Verify the actual file and path after conversion.
Affinity's placement guide provides the related placement workflow. Confirm that the new source contains the intended image, rather than assuming that converting the resource type upgrades a low-quality preview.
Linked resources can update when their external source changes. Agree which revision is authoritative before enabling or relying on that behavior; the linked-content update guide provides useful context.
Verify portability and future updates
Keep the linked assets in a stable project structure and include required files in an editable handoff. The resource-package guide explains the dependency risk when only the main layout is transferred.
A suitable acceptance check is: the resource type is intentional, the approved source exists at the recorded path, the image remains available after reopening and the exported proof matches the approved revision. Also confirm that the recipient is authorized to receive any included asset.
This explanation follows documented placement behavior and a hypothetical preview. It does not claim that every browser-dropped image is unsuitable, or that linking alone improves resolution, rights or color accuracy.
For later updates, test the agreed revision procedure on one noncritical resource first. Document whether the team expects a manual update or an automatic refresh before applying it throughout the book.
Related tasks
- Why Are Images Missing When Someone Else Opens My InDesign or Photoshop Project?
- Why Does Updating Linked InDesign Content Undo My Local Changes?
- Why Can I See a Photo in Lightroom Classic but Not Export It?
Sources and scope
- Embedding vs linking: Browser/app drag-and-drop differs from file-manager placement policy.
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.