A project file can contain a reference to an image rather than the image itself. It may also retain a cached preview that makes the layout look complete on your computer. Before handing over an editable project, collect its external dependencies and reopen the package away from the original source folders.
Distinguish a dependency from a preview
Inspect the application's link or layer information. Identify which images are embedded, which are linked and which links are missing or modified. A linked file on your desktop, external drive or personal cloud folder is not automatically available to the recipient.
Do not replace a missing high-resolution source with the small preview just because that preview looks acceptable at normal zoom. Find the intended source and confirm its revision. Otherwise the project may open without a warning while silently delivering a poorer image.
Repair first, package second
In external InDesign, use the preflight and link checks before packaging. Adobe's packaging guide describes collecting the document and linked graphics, alongside relevant font resources and a report. Packaging an already broken link does not recover a file you no longer possess.
In external Photoshop, inspect linked Smart Objects separately from ordinary embedded layers. Adobe's linked-object packaging guidance describes gathering linked resources and relinking missing files. Use the application's dependency workflow rather than manually assuming that every nearby JPG belongs to the project.
Worked example: an invented exhibition program
This fictional project has an InDesign program, an approved AI portrait and a Photoshop composition that links to a background texture. The designer originally stores the portrait in Downloads and the texture on an external drive. Sending only the INDD and PSD leaves two separate dependencies behind.
The designer first verifies that both links point to approved sources, then packages each applicable project. They include a final PDF as a visual reference and a note stating which file the recipient should edit. The PDF helps compare appearance but does not substitute for the editable source or its linked resources.
Test without accidental access to the originals
Copy the delivery package to a separate test location and open the packaged project. Ensure the test is not quietly resolving links through the original folders. A colleague's clean workstation is useful when available; otherwise inspect resolved paths and dependency status carefully. Do not delete the original files merely to create the test.
Check for missing-link warnings, unexpected substitutions and changed image resolution. Compare the opened layout with the supplied reference PDF. A package passes only when the intended project can locate the intended resources, not simply when an archive can be downloaded.
Include the limits of the handoff
Document the application version, editing entry point and any resources the recipient must obtain separately. Font inclusion depends on the font's permissions and application support; a package command does not grant a distribution license. Identify such dependencies clearly rather than quietly replacing typography.
Create artwork through Image Prompt, save the approved image locally and place it into the external design project. The final delivery should contain the tested dependency package and a viewing reference, with a clear account of what is editable and what remains an external requirement.