Nodes/Chaosaiart-Nodes/🔶 AutoSyc Save Image
ComfyUI Node

🔶 AutoSyc Save Image

The save node built for Chaosaiart's animation loop

By chaosaiart·Created 2 years ago·Updated about a year ago· 117
🔶 AutoSyc Save Image
  • images
  • restart
    â—„filename_prefixchaosaiartâ–º

    If all you want is to write a PNG to disk, ComfyUI's stock Save Image node already does that and you don't need this one. AutoSync Save Image exists because Chaosaiart-Nodes is built around a different way of animating - frame by frame, one generation at a time, feeding each result back into the next - and this is the node that sits at the end of that loop.

    What it actually does

    Strip away the pack context and it's the same job as the built-in node: take an IMAGE, write it out under output/ with a filename built from your prefix plus a running counter. Nothing exotic in the mechanism. The one thing that marks it as pack-specific is the optional restart input, typed as RESTART - not a standard ComfyUI type, which means it's only meaningful wired to one of Chaosaiart's own cache/counter/switch nodes elsewhere in the graph. The pack's whole pitch is frame-to-frame generation (batch count, not batch size) precisely because it's VRAM-light - each frame is cached and handed to the next generation rather than the whole sequence living in memory at once. A save node with a restart hook fits that loop: save this frame, then let the signal continue the run into the next one. Treat the input as plumbing for their own animation workflows rather than something you'd wire up from scratch on your own.

    If you're doing a plain one-off generation with no loop, just leave restart unconnected - it behaves exactly like a normal Save Image node at that point.

    Inputs and outputs

    • images (required, IMAGE) - what you're saving.
    • filename_prefix (required, STRING, defaults to "chaosaiart") - change it if you don't want every export branded with the pack name.
    • restart (optional, RESTART) - the loop-continuation hook described above.

    There are no data outputs. It's a terminal node (is_output_node) - a sink, not a step you chain further.

    Installing it

    Two paths, both from the README:

    • ComfyUI Manager → Install via Git URL → https://github.com/chaosaiart/Chaosaiart-Nodes.
    • Manual: cd ComfyUI/custom_nodes && git clone https://github.com/chaosaiart/Chaosaiart-Nodes, then restart ComfyUI. On Linux, also run pip install opencv-python and pip install tqdm (activate your venv first if you use one) - these aren't auto-installed by Manager the way a requirements.txt normally would be, they're called out as a manual step for the whole pack. Windows has an Install_windows script in the folder.

    No model downloads - this is a pure logic/utility pack, it works with whatever checkpoint you've already got loaded.

    Where people get burned

    Worth knowing going in: this is a small, mostly one-person project. The author posted it to r/comfyui in March 2024 to a modest response, and community chatter about it effectively stopped after 2024 - there's no active support thread or Discord to fall back on if something behaves oddly. So the practical troubleshooting here is limited to what's actually documented:

    • Default filename branding. filename_prefix defaults to "chaosaiart", not "ComfyUI" - easy to miss if you're scripting output paths and expecting the stock naming.
    • restart only makes sense inside this pack's own animation graphs. Don't try to wire it from an unrelated node type - it's not a generic control-flow signal, it's specific to Chaosaiart's cache/counter system.
    • No output means no debugging via chained nodes. If you need to confirm what actually got written, pair it with chaosaiart_Show_Info upstream of the save, or just check the output folder directly.
    Category🔶Chaosaiart

    Inputs (3)

    NameTypeDefaultDescription
    imagesIMAGE—
    filename_prefixSTRINGchaosaiart—
    restartoptRESTART—

    Outputs (0)

    No outputs