Nodes/Anymatix/Anymatix Image Save
ComfyUI Node

Anymatix Image Save

The save node with a format for everything — PNG through OpenEXR, counters, and JSON sidecars

By Anymatix·Created about a year ago·Updated 2 days ago· 0
Anymatix Image Save
  • images
  • save_json
    output_path[time(%Y-%m-%d)]
    filename_prefixComfyUI
    filename_delimiter_
    filename_number_padding4
    filename_number_start
    extension
    overwrite_mode
    show_previews
    bit_depth8
    quality100
    lossless_webp

    Every workflow ends somewhere, and in Anymatix-land it ends here. Anymatix Image Save is the node the app reads its results from - it writes your generated images to disk in the format you actually want, with filename numbering, optional JSON metadata sidecars, and subfolder organization. If you've used WAS Node Suite's image saver, the shape of this will feel familiar: it's a beefed-up Save Image with real format coverage and deliberate overwrite behavior.

    The headline feature is the extension dropdown, which is unusually generous: png, jpg, jpeg, gif, tiff, webp, bmp, exr, and avif. Most stock save nodes stop at png/jpg; if your pipeline feeds a video tool that wants sequential PNGs, or a color pipeline that wants 16-bit OpenEXR, or you just want smaller webp files for a gallery, this node has it. The extension list is a genuine differentiator - 9 formats is more than most of the ecosystem bothers with.

    The inputs that matter

    The full list looks intimidating, but only a handful matter day-to-day:

    • images - the IMAGE tensor to write.
    • extension - png/jpg/webp/exr/avif/etc. Your format choice.
    • filename_prefix and filename_number_padding - the base name and how many digits the counter gets. output_path accepts a subfolder (default [time(%Y-%m-%d)], a date-stamped folder), and overwrite_mode controls the numbering: false auto-increments past existing files, true overwrites, and prefix_as_filename skips numbering entirely.
    • save_json - writes a JSON sidecar alongside the image (the Anymatix app reads these to reconstruct what was made).
    • quality (1-100) and lossless_webp apply to the lossy formats; bit_depth (8 or 16) is there when you need it - it's optional precisely because not every format has anything to say about it.

    Outputs: none - it's an output node; it writes files and reports the paths in its UI.

    Install

    The standard pack routine:

    cd ComfyUI/custom_nodes
    git clone https://github.com/Anymatix/anymatix-comfy-nodes
    

    then restart, or install via ComfyUI Manager (search "anymatix-comfy-nodes"). Pillow and numpy handle the writing; the pack pulls them automatically.

    Issues to expect

    The counter logic is where people get confused first. With overwrite off, the node scans existing files matching your prefix pattern and starts numbering past the highest one - that's the safe default, and it means you'll never silently clobber yesterday's batch. Set overwrite on and you will, so think before you do. Two more: bit_depth 16 is pointless for jpg (it's a png/exr/tiff thing), and if you're looking for files and can't find them, remember the default subfolder is date-stamped under ComfyUI's output directory.

    CategoryAnymatix

    Inputs (13)

    NameTypeDefaultDescription
    imagesIMAGE
    output_pathSTRING[time(%Y-%m-%d)]
    filename_prefixSTRINGComfyUI
    filename_delimiterSTRING_
    filename_number_paddingINT41–9
    filename_number_startCOMBO2 options: false, true
    extensionCOMBO9 options: png, jpg, jpeg, gif, tiff, webp, +3
    overwrite_modeCOMBO3 options: false, true, prefix_as_filename
    show_previewsCOMBO2 options: true, false
    save_jsontrue
    bit_depthoptINT88–16
    qualityoptINT1001–100
    lossless_webpoptCOMBO2 options: false, true

    Outputs (0)

    No outputs