
Saving linked artwork in Photoshop or Illustrator and seeing it in an Adobe Express layout are separate steps. Adobe's linked-asset workflow includes returning to Express and choosing Update after the source changes. Check the source identity and the updated proof before treating a layout as current.
Key Takeaways
- Confirm that the layout uses a linked asset rather than a converted or detached copy.
- Save the intended source, then apply the linked-asset update in Express.
- A previously downloaded proof does not change when the working design changes.
Establish which copy owns the change
Imagine a proposed packaging proof in which the designer changes a small blue seal to green. The Express poster still shows blue. Before editing again, identify the selected asset and the source opened by its linked-asset action. A similarly named desktop copy is not sufficient evidence that you changed the file used by this layout.
Record the source filename, the layout name, and one unmistakable visual change. This gives the team a practical way to trace the revision without relying on modification dates alone. For complicated source documents, also consider the nested Smart Object refresh boundary.
Follow the source-to-layout sequence
In Adobe's documented linked-image procedure, select the linked asset and open it in Photoshop or Illustrator. Make and save the change in that application. Return to Express and apply Update when the linked-assets-changed notification appears.
Inspect the exact changed area after the update. Do not use repeated exports as a substitute for confirming that the on-canvas rendition is correct. If the expected linked action is absent, first determine whether the original import was converted into Express content or whether you selected a different object.
Diagnose a missing refresh without destroying the layout
If no update appears, reopen the source through the selected asset and verify that the saved change is present there. Check the account and file identity rather than immediately replacing every instance. Preserve a working copy before trying a different import route.
Other layout tools also need clear dependency ownership: updating linked InDesign content can overwrite local changes, while a design-project package addresses missing dependencies during delivery. Those procedures should not be assumed to be Express menu commands.
Approve a newly exported proof
For the hypothetical seal change, first inspect the green seal on the Express canvas. Then download a new candidate proof under a new revision name. Open that file independently and confirm the seal, crop, and nearby text. Ask the reviewer to compare this named candidate with the prior blue-seal proof.
If the source contains green but the candidate still contains blue, the chain remains unresolved. Keep both artifacts and the source identity in the correction note; do not mark the change complete because one editor window looks right. If necessary, produce a separate flattened delivery rendition from the approved source while preserving the editable source for later work. This procedure is a proposed revision check, not a claim that a particular sync failure was reproduced.
Related tasks
- Why Did a Nested Linked Smart Object Stay Out of Date?
- Why Does Updating Linked InDesign Content Undo My Local Changes?
- Why Are Images Missing When Someone Else Opens My InDesign or Photoshop Project?
Sources and scope
- Adobe: Edit linked Photoshop and Illustrator assets: Select linked asset, Open in source application, modify and save; return to Express and select Update when notified.
Documentation-based guidance. The example, diagnostic path and acceptance checks are proposed; no installed-application compatibility test is claimed.
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.