
Check whether Generator Image Assets is enabled before treating Photoshop’s asset folder as a frozen delivery. A filename extension in a layer or group name can request an automatically maintained image. Subsequent edits and saves can therefore change a file that somebody already reviewed.
Adobe’s Generator instructions describe these automatic updates. An approved delivery needs its own identified snapshot; the working output directory is a production mechanism, not an approval record.
Identify the live output relationship
Inspect the current desktop menu File > Automate > Generator Plugins > Image Assets, then look for layer names such as cover.png. For a saved local document, generated assets appear beside the document in a subfolder. An unsaved document can instead put assets on the Desktop. Record the actual document and destination before diagnosing a missing file.
A layer can request several assets through comma-separated or plus-separated specifications. Count the requested names rather than assuming one layer always means one output. A colon or asterisk in a layer name can prevent generation. These are naming rules, not evidence that a particular image has been approved.
The Layers to Files visibility guide covers a separate export command. Its Visible Layers Only choice does not establish the behavior of Generator’s continuously updated folder.
Rehearse the handoff on a disposable copy
Consider a hypothetical campaign with a cover.png layer and a separately approved cover. Preserve the original PSD and existing delivered files before this proposed check:
- Use a duplicate document in a separate working location. Confirm where its generated assets are actually written.
- Give the candidate layer a recognizable temporary mark, save, and inspect that layer’s requested output.
- Compare the changed working output with the retained approved file. Check both pixels and filenames rather than relying on a familiar thumbnail.
- Remove the temporary mark in the working copy, save again, and recheck the output before selecting a final candidate.
The expected relationship is that a generator-enabled change updates its corresponding asset. This exercise has not been performed for this guide. Do not run it in a folder watched by a publishing process or shared as the approved delivery.
Freeze the approved set deliberately
Copy the chosen, checked outputs into a separately named release folder and include a small manifest linking each delivered name to its source document revision. Record approval outside the live asset folder. If automatic production is no longer needed, deliberately disable Image Assets and verify the current interface state.
Keep the editable master separate from flat deliverables. If a one-time saved copy is the required handoff instead, the Save a Copy workflow addresses preserving the open master while creating that copy.
Stop when the destination is uncertain
If the expected asset does not update, investigate the enabled state, exact layer name and actual destination first. Do not delete the old asset folder to force a result. If cloud-document storage or a different Photoshop release changes the location, consult that release’s help and use a controlled local copy or a deliberate one-time export.
Accept the delivery only when its membership and appearance match the approved manifest and further work in the PSD cannot silently replace the recipient’s snapshot.
Related tasks
- Why Are Hidden Draft Layers Included in My Photoshop Asset Export?
- Save a Photoshop Delivery Copy Without Switching the Master
- What Is the Difference Between an Editable Artwork Master and a Flat PNG?
Sources and scope
- Generate image assets from layers: File > Automate > Generator Plugins > Image Assets enables name-triggered assets. Extensions in layer/group names request output. Saving creates files alongside saved PSD, or Desktop if unsaved. Generator-enabled changes update outputs automatically. Colon/asterisk prevent generation; comma/plus allow multiple specifications.
Based on Adobe desktop help reviewed October 31, 2026. Menu names depend on the installed release. The example and acceptance procedure are proposed, not results of hands-on 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.