ComfyUI’s Save Image node writes each input image as a PNG in the output directory. Its filename combines your filename_prefix, an optional %batch_num% batch-position marker, and a five-digit counter. The node can also embed workflow information in each PNG, but only when metadata saving is enabled. Saving an image does not by itself prove that workflow metadata is present.
Understand the filename parts
Set filename_prefix to the stable part of the name, such as CampaignA. Add %batch_num% where you want an image’s position in the current batch to appear. The node replaces that marker with the image’s batch position. It also adds a five-digit counter; the documented example is ComfyUI_00001_.png. The documentation does not specify every separator or counter-reset detail for all configurations, so inspect the actual names in your output rather than inferring unlisted behavior.
For example, a hypothetical prefix CampaignA_%batch_num% expresses that the batch position belongs after the campaign label. The position marker and counter have different jobs: one identifies an image’s place in the batch, while the counter is part of the saved filename sequence. A counter is not a substitute for checking that the expected number of batch images was written.
The prefix also supports formatting information such as dates or values from nodes. Use such formatting only when the relevant value exists in the workflow, and verify the resulting filenames. The Save Image node documentation describes the input and the filename components.
Set up and verify a batch
Use this sequence for a batch you need to hand off or review:
- Decide how many images the current batch should contain, and record that expected count.
- In the Save Image node, set
filename_prefixto a short, recognizable label. Add%batch_num%at the position where the batch image’s index will be useful to readers. - Run the workflow, then inspect the saved PNG filenames in the ComfyUI output directory. Check that the names include the intended label and that the batch-position values are distinguishable where expected.
- Count the actual PNGs produced for this run and compare that number with the expected count. Do not use the largest counter alone as proof that all expected images are present.
- If the workflow must be recoverable from the PNGs, open a representative output in a metadata-aware viewer or inspect its text metadata. Confirm the prompt and other expected workflow information are actually present.
The node returns the input images unchanged after saving them, so downstream nodes can continue to receive those images. This pass-through is separate from what is written into PNG metadata. The documentation describes the output image as unchanged; it does not say that the saved file necessarily contains enough information to reconstruct every editing detail.
Reconcile names, counts, and metadata
The following is a hypothetical acceptance check, not a report of a software test. Suppose a batch is expected to contain three images and the prefix is CampaignA_%batch_num%.
| Check | Hypothetical observation | Decision |
|---|---|---|
| Expected batch size | 3 images | Use as the run’s target count |
| Saved files | 3 PNGs with the CampaignA label | Count matches; inspect the names and image contents |
| Batch position | Position marker appears in the intended filename location | Names distinguish batch positions as planned |
| Counter | Each filename includes a five-digit counter | Confirmed as part of the naming format, not as proof of completeness |
| Metadata | Prompt and expected workflow information are visible in PNG text metadata | Metadata check passes for the inspected files |
If only two PNGs appear, or a file is missing its expected name component, first compare the actual files with the run’s expected count and inspect the node’s prefix. If filenames exist but the metadata check fails, check whether metadata saving was disabled at startup. Re-run only after you have identified and corrected the cause; changing a filename does not add missing metadata to an already saved PNG.
Know what metadata saving means
Save Image receives hidden prompt and extra_pnginfo inputs that ComfyUI populates with the workflow prompt and extra PNG information. When metadata is enabled, that information is embedded as text metadata in each saved PNG. When metadata saving is disabled, do not expect those workflow details to be embedded. The PNG can still exist as an image file, so file presence and workflow traceability are separate acceptance checks.
Before relying on PNGs to retain workflow information, check whether metadata saving was disabled for the ComfyUI instance. The Save Image documentation says the hidden prompt and extra_pnginfo information is embedded as text metadata when metadata is enabled; it does not guarantee that every viewer displays metadata, that every PNG contains identical information, or that embedded metadata alone restores all external inputs and context. Keep the workflow or other required project records separately when full recovery matters.
Common questions
Does `%batch_num%` replace the five-digit counter? No. The documented filename construction describes the optional batch-position marker and a five-digit counter as separate components.
Can I tell that metadata exists just by seeing a PNG? No. A saved image may have no embedded workflow information when metadata saving is disabled. Inspect its text metadata.
Does Save Image change the image it passes to the next node? The documentation says the node returns the original input images unchanged. That pass-through does not establish that the PNG contains recoverable workflow metadata.
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 film workspace. The external software controls discussed above belong to their respective products.