If you found an image in ComfyUI Assets and want to recover the graph that produced it, first check whether it is a generated asset or an imported file with workflow metadata. The options Open as workflow in new tab and Export workflow are available for generated files and for imported files that carry workflow metadata. An image being visible in Assets does not, by itself, mean its workflow can be recovered. The Assets documentation describes these conditions and the export action.
Start with the asset’s origin
Open Assets from the left sidebar, then locate the file in Generated or Imported. These tabs represent different routes into the library: Generated contains files saved by workflow runs; Imported contains uploaded files, such as reference images. The distinction is a useful first check, but it is not enough on its own to decide whether an imported file can restore a graph.
For a generated result, check the card’s context menu for Open as workflow in new tab or Export workflow. For an imported file, check those same options rather than assuming the file is recoverable. The documented condition is that the imported file must carry workflow metadata. ComfyUI-written PNG and WebP images are examples of imported files that may carry it; the file extension alone is not proof that metadata is present.
Follow this recovery sequence
- Find the image in the correct Assets tab. Use the filename search if needed; it filters the current tab.
- Select the asset and open its right-click menu. If it belongs to a grouped run, open the group using its output-count badge and inspect the relevant file there.
- Look for Open as workflow in new tab and Export workflow. Their presence is the practical signal that the asset offers a workflow action in this panel.
- If you want to continue in ComfyUI, choose Open as workflow in new tab. If you need a portable workflow file, choose Export workflow; the exported workflow is saved as JSON.
- For an imported asset with neither action, do not infer that it contains a recoverable graph from its appearance or filename. Check whether you have another copy known to retain workflow metadata, or return to the source that produced or supplied the file.
- After choosing Export workflow, confirm that the JSON file was saved where you can locate it. This confirms the export deliverable was written; the Assets documentation does not specify a separate JSON re-import procedure or claim that saving the file verifies every node. Exporting is a separate action from downloading the image.
The panel also offers Download for the asset itself. Downloading a media file and exporting a workflow are different operations: the former saves the selected asset, while the documented workflow export saves JSON. The asset reuse and download sections describe these separate actions.
Use this diagnostic branch
The following is a hypothetical example, not a tested result. A creator finds portrait.webp under Imported and sees no workflow actions. They find render.png under Generated, whose menu shows both actions, and export a JSON file. The first file’s extension does not establish that it has metadata; the second file’s available menu actions provide a clear route to open or export the workflow.
| Observation | Interpretation | Next action |
|---|---|---|
| Generated image; workflow actions appear | The panel exposes workflow recovery for this asset | Open in a new tab or export JSON |
| Imported PNG or WebP; workflow actions appear | The available actions are the useful signal; metadata is present for this purpose | Open or export, then verify the JSON was saved if exporting |
| Imported file; actions do not appear | The panel does not offer workflow recovery for this file | Look for another copy that carries workflow metadata or return to its source |
| Several outputs are grouped together | You are viewing a run group, not necessarily the individual file menu | Open the group and inspect the target output |
When recovery is unavailable
If the workflow actions are missing, the Assets documentation does not describe a way to reconstruct a graph from an ordinary media file. Use a copy that is known to include workflow metadata, or locate the original workflow elsewhere. Do not treat Insert as node in workflow as a substitute: that action inserts a matching loader node, such as Load Image, with the asset selected; it reuses the media, not the original graph.
Deployment can affect what this panel represents: Comfy Cloud enables Assets by default, while self-hosted ComfyUI needs --enable-assets and a working database connection. Without that flag, the panel can list local history and output files instead of the asset library. Confirm the panel mode before interpreting missing actions or a history entry as evidence about workflow metadata.
Common questions
Does a PNG or WebP always contain a recoverable workflow? No. The documentation names ComfyUI-written PNG and WebP files as examples of imported files that can carry workflow metadata. The extension alone does not establish that this particular file has it. Check whether the workflow actions are available.
Is downloading the image the same as exporting its workflow? No. Download saves the asset file. **Export workflow** saves the workflow as JSON. Choose the action that matches what you need to keep; saving the JSON is the documented export check, not a claim that the file has been re-imported or fully validated.
What does “Insert as node in workflow” recover? It adds a loader node for the asset, when that file type has a supported loader. It does not claim to restore the graph that created the image.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.