Saving a ComfyUI workflow saves the editable graph, not a copy of its generated image. Use Ctrl + S (or Cmd + S on Mac) to save the workflow. Then check four things separately: did the run complete; is an output file listed under Assets > Generated or present in the configured local output location; has that file been downloaded to this computer; and does the downloaded file open? The Assets entry may be available without the full asset system: on self-hosted ComfyUI without --enable-assets, it lists local history and output-folder files. The full asset system requires --enable-assets and a working database connection. Comfy Cloud enables the Assets panel by default.
Find the generated file
Use this sequence after the run has finished:
- First confirm that the run completed. If the Assets entry is available, open it from the left sidebar and select Generated; this tab lists files saved by workflow runs, while imported reference files appear under Imported. Comfy Cloud enables the panel by default. On self-hosted ComfyUI, the entry can open without the full asset system and list local history and output-folder files; the full asset system requires
--enable-assetsand a working database connection. - Look for the run only if it completed and saved an output. If one run produced several files, its card may show an output-count badge; click the badge to inspect the grouped files.
- On Cloud, use the available search, filters, or sorting to narrow the list. Search filters by filename, so it helps only if you know part of the name.
- If no file is listed, check the run history and the output location configured for that installation. This distinguishes an output present locally but absent from the list from an output not found; absence alone does not establish why no file is available.
- If the file is visible but not on this computer, select it and use the card’s download control or right-click Download. A single file downloads on its own. On Cloud, downloading a multi-output run or multiple selected assets prepares a ZIP; on self-hosted ComfyUI, grouped outputs are expanded into individual files. Open the downloaded file to confirm it is usable.
The Assets panel is a media library for generated and imported files, not the workflow-saving panel. Its behavior and self-hosted availability are described in the official Assets documentation. In APP mode, Ctrl + S or Cmd + S saves the workflow for future use; the documentation describes Assets as a separate panel. See the APP mode guide.
Delivery checklist
The following is a hypothetical checklist, not a report of a tested run. Suppose one completed run has two output files, but the recipient needs one image and an editable graph. Verify the actual deliverables rather than treating a panel listing as proof of delivery:
| Check | Acceptance evidence |
|---|---|
| Workflow saved | The workflow file exists and opens as an editable graph |
| Intended output identified | The completed run’s output is visible in Generated or at the configured local output location; inspect grouped files if present |
| Media delivered | The intended media file has been downloaded, and the downloaded file opens |
| Recipient needs both | Include both the workflow file and the verified media file |
If the output is not found, check run completion and the configured output location; do not infer a cause from absence alone.
If the image is missing
First confirm that the run completed and that you are looking under Generated, not Imported. Search by filename if you know it; clear active filters or change sorting if a result might be hidden. If several files were created, open the grouped run rather than assuming its card represents just one image.
On self-hosted ComfyUI, the Assets panel may use local history and output folders when the asset system is not enabled. The full asset-library system requires starting the server with --enable-assets and a working database connection; without that setup, do not assume the library-backed behavior is available. Check the installation’s output location and run history instead. The documentation does not establish that every workflow saves an image: check that the workflow has an output-producing path and that the run actually completed with a saved file.
If the file is listed but missing from your computer, download it from its asset card. If it is .exr or .hdr, ComfyUI opens it in the HDR Viewer rather than the standard image lightbox; the viewer also offers Download image. A preview or viewer display is still not a substitute for confirming that the download finished.
Common questions
Does saving the workflow preserve the generated image inside it?
The workflow-save instructions cover saving the workflow; the Assets documentation separately covers generated media and downloads. Keep the media file as its own deliverable.
Where are generated files on a self-hosted setup?
The Assets documentation says that, without the enabled asset system, the panel lists files from local history and output folders. It does not prescribe one universal filesystem path for every installation, so check the output location for your setup rather than assuming a fixed directory.
Should I send the workflow, the image, or both?
Send the image when the recipient needs the result. Send the workflow when they need the editable graph or to run it again. Send both when they need the result and the means to inspect or reuse the graph. An APP-mode share link is a separate option and is documented as supported only on Comfy Cloud.
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.