Shima File Saver

Stock ComfyUI's Save Image gets the job done, but it buries your output in output/ with a name nobody can find later. Shima.FileSaver is the "do it properly" version: it saves with the same organized naming as the FileNamer - project folder, timestamp, collision ID - and, importantly, it embeds the full workflow JSON and a metadata block right into the file. In this ecosystem that's not a luxury, it's the difference between a PNG and a project file (see the image-io-metadata doc: the graph lives in the PNG's text chunks, and a workflow you can drag back onto the canvas travels with the picture).

The mechanism: it takes your image, builds a name from the same components as FileNamer (base_folder, project_name, base_name, timestamp, collision ID, prefix/suffix, filename_order presets, separator), writes the file to disk, and stuffs the metadata into it using PIL's PNG text chunks. It also has a master saver_enabled switch - flip it off and the node becomes a pure passthrough, which is a great way to test a pipeline without committing files to disk.

Inputs, focusing on what a beginner actually sets:

• images (IMAGE) - the image to save.
• export_as (PNG / JPEG / WebP, default PNG) with export_quality (1–100, default 95, used for JPEG/WebP only). PNG is lossless; JPEG and WebP are not, and WebP/JPEG also can't carry the full ComfyUI workflow graph the way PNG does.
• export_image - a label for what you're saving (Unprocessed, Processed, Lineart, Depth Map, Normal, Palette...). It goes into the filename and metadata, so a multi-pass pipeline produces self-describing files instead of output_0042.
• export_with_metadata and export_with_workflow (both default on) - the metadata block (timestamp, project, prompts, model) and the full workflow JSON. Leave them on; this is the "the file is the project" feature.
• overwrite_mode - collision_id (unique files), increment, overwrite, or skip. collision_id is the safe default; skip is handy for idempotent batch runs.
• user_notes - freeform notes embedded in the file's metadata.
• show_preview - render the image under the node for a quick look.

Optional inputs worth knowing: shima.commonparams (a config bundle from the Shima.Commons controller that overrides project/folder settings), the external_* overrides, and subfolder_path for batch mirroring.

Outputs: the paths back out - full_path, folder_path, filename, collision_id, timestamp - plus an image passthrough, so you can keep a pipeline alive after the save instead of ending it there.

Where people get burned: saving to JPEG or WebP and then trying to drag the file back into ComfyUI to recover the workflow. It isn't there - the graph chunk is a PNG thing, and re-encoding drops it on the floor. Keep your master copy as PNG; export lossy formats only as delivery copies. And if you're getting unexpected duplicates, your collision ID is doing its job - that's the point, not a bug.

Install via ComfyUI Manager (search "Shima") or

cd ComfyUI/custom_nodes
git clone https://github.com/KDB-USJP/shima_wf

then restart. No models to download.