To save a ComfyUI IMAGE batch as one animated AVIF, connect the batch to Save Image (Advanced), choose AVIF, set save_mode to animated, then choose fps and loop_count. The node documentation says this mode writes the entire batch as a single animated AVIF. By contrast, still images saves each batch image as a separate still file. These modes produce different deliverables; choosing AVIF alone does not make a batch animated. Official Save Image (Advanced) documentation
Decide the output and set its timing
Use this sequence when the desired deliverable is a playable sequence rather than separate pictures:
- Confirm that the input is an
IMAGEbatch. Record its image count and intended order from your workflow; the node documentation does not define how your upstream process arranges frames. - In Save Image (Advanced), select
AVIF. Setsave_modetoanimated. If you need one still file per image instead, keep or choosestill imagesand plan for separate files. - Choose
fpsfor the intended playback pace. For example, if your project calls for 12 frames per second, enter12. This setting controls the animation frame rate; it does not set the number of batch images. - Choose
loop_countto match delivery requirements. The documented value0means loop forever; other values specify the number of times to loop. Do not assume this changes the batch size or number of distinct frames. - Run the workflow and inspect the saved result. If alpha is required, note the documented AVIF limitation: AVIF accepts one-channel grayscale or three-channel RGB, not RGBA.
The settings’ stated meanings and ranges are documented by the node: fps is 0.01–1000.0, and loop_count is 0–1000. Animated AVIF controls and output behavior
Acceptance worksheet
The following is a hypothetical check, not a software test or a guarantee of encoder behavior. Suppose a workflow supplies 24 images in the intended order, with a target of 12 fps and two loops. The nominal duration of one pass would be 24 ÷ 12 = 2 seconds if all 24 images are represented as frames at the selected rate. Confirm actual output properties with a media viewer or inspection tool; the documentation does not specify a frame-count algorithm or guarantee that every viewer reports timing identically.
| Observation | Hypothetical result | Decision |
|---|---|---|
| Saved items | One AVIF result, not 24 separate still files | If separate files appear, check that save_mode is animated and rerun. |
| Frame sequence | Opening, middle, and ending images appear in the intended order | If order is wrong, inspect the upstream batch ordering; do not expect fps to reorder images. |
| Playback pace | Viewer appears consistent with the intended 12 fps | If it seems too fast or slow, compare with a second viewer and review the fps setting. |
| Loop behavior | Playback repeats twice, or follows the chosen loop setting | If behavior differs, check the encoded file in another viewer; the node documentation does not describe viewer-specific loop interpretation. |
| Frame count | Inspection reports 24 frames | Compare with the input count; investigate any mismatch rather than assuming a documented conversion rule. |
Limits and next steps
The documentation defines the save modes and timing controls, but does not promise how every media player displays loop behavior, nor does it describe a rule for transforming batch length into encoded frame count. Treat the worksheet’s checks as your own acceptance criteria. If the file is not animated, first verify the selected format and mode, then inspect the node’s saved-result list and open the output in another animation-capable viewer. If the node errors, check the documented channel restriction: RGBA input is unsupported for AVIF. Resolve the input format through an appropriate upstream workflow or choose another supported output format; do not infer that changing FPS will fix a channel error.
Common questions
Does `fps` change how many images are in my batch?
No such effect is documented. It sets animation frame rate, not batch size.
What does `loop_count: 0` mean?
The node documentation defines it as looping forever. Choose another supported count when the recipient requires a finite repeat count.
Should I choose animated mode if I want separate downloadable images?
No. Choose still images when the intended deliverable is one still file per batch image; choose animated when the intended deliverable is one animation.
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.