Add a "save to output" option to the image preview node

[allo-]

Feature Idea

If one decides that an image in the preview of the "preview image" node looks good, it would be nice to have a "save to output" context menu icon that copies it to the output folder. The current "save image" function downloads it to the browser.

Existing Solutions

• Replace the "preview image" with a "save image" node and re-run the workflow. This is not a good solution if the workflow contains items that are randomized after a run or never cached.
• Download the file and manually save it into the output folder. The solution is only usable if ComfyUI runs on the same computer as the browser and the filename is not adjusted for the current numbering in the output folder.

[RandomGitUser321]

The current "save image" function downloads it to the browser.

If you're talking about the save image node, then no it doesn't. It saves to the ComfyUI/output folder. If you're talking about saving from the right click context menu on an image, then it makes sense that it would be browser downloaded just like any other image would, while using a browser. Preview saves to the ComfyUI/temp folder for the session. When you relauch Comfy, it will clear the temp folder and all contents within it on startup.

[allo-]

This issue is about adding a new context menu item to the preview node, which should basically create a copy of the temp file in the output folder. The node already has a "save image" context menu, but it acts as "download to browser".

I edited the issue to make it a bit clearer.

[clover-supply]

Also adding an option to pick between jpg and png would be nice.

[allo-]

Also adding an option to pick between jpg and png would be nice.

I don't think that's easily possible, as the node writes a temp file in the format. The simple option for saving to output would be to copy that file. Given png is lossless one could convert it in that step, but I think that may be out of scope here.

Or do you mean an option which format should be used on the preview node (so copying would also use that format)? May warrant an own issue as well.

[allo-]

It looks like it would be rather simple to implement by reusing parts of the SaveImage.save_images method to filename generation and then possibly using shutil to copy or move the file.

I do not see in the source an example how to extend the context menu or where the "save image" item that downloads the image is added to a menu. Is it a standard item of the image widget?

[clover-supply]

It looks like it would be rather simple to implement by reusing parts of the SaveImage.save_images method to filename generation and then possibly using shutil to copy or move the file.

I do not see in the source an example how to extend the context menu or where the "save image" item that downloads the image is added to a menu. Is it a standard item of the image widget?

Well the best solution would be to merge the save and preview core nodes into a single one with format and quality picker and a switch whether you want to save it or not. Or just be able to save as jpeg when right click saving on preview node, since 95% quality jpeg removes a huge chunk of the png bloat.

[allo-]

I am not sure about merging them.

One solution for merging would then be an "auto save" switch:

• Auto Save on: Save node behavior
• Auto Save off: Click to save. (Stores to temp, copies/moves to output if one clicks)

But I can already see people forgetting to click and regretting it. One would likely need to add very obvious color coding if the node was already saved or not in the UI, and people running a workflow often or having many outputs may still forget to click in some runs and then miss the results.

I'd rather extend the preview node, which is not supposed to save by default. I mostly think of the use-case of "just testing" or adjusting things in a workflow without wanting to save all example images (so using the preview node), but then having a great result one wants to keep even though the workflow itself may not yet be finished.

The trade-off is having many images that are more or less just previews in the output folder or risking that an output image is not saved.

I also think there may be custom nodes that implement such ideas, but the output and preview nodes are used in 99% of the workflows of others one can download. Adding the "keep" function as a core feature would keep the functionality of these workflows by default, but add the quality-of-life feature to keep the result with just two clicks to all of them.