sdAppstore_saveImage

sdAppstore_saveImage is the ComfyUI_Appstore pack's version of ComfyUI's core SaveImage - the terminal node that writes a published app's output to disk. Despite the "sd" in the name (a relic from the author's earlier webui life; this is a ComfyUI pack), it's where your app-store workflow ends up when a paying user hits "generate."

Mechanically it's a near-clone of core SaveImage. It's an output node (OUTPUT_NODE = True), takes images (IMAGE) and filename_prefix (STRING, default ComfyUI), prepends Appstore_ to your prefix, expands any time tokens, and writes each frame as a PNG into ComfyUI's output folder using the standard folder_paths.get_save_image_path counter scheme at compress_level 4. It returns {"ui": {"images": ...}} so the frontend - and the pack's appstore panel - knows the run produced results and can show thumbnails. If you've used SaveImage, you already know this node.

The detail that matters

Here's what makes it different, and it's easy to miss: unlike core SaveImage, this node saves with pnginfo=None - no embedded workflow metadata. In the wider ComfyUI culture, "workflow included" is a community norm and you can drag an output PNG back into the app to rebuild the whole graph. This node deliberately breaks that. In a paid-app context that's a feature: you don't want a customer dragging a generated image back into ComfyUI and getting your entire workflow for free. But if you're just testing locally, remember drag-image-back-to-rebuild won't work on these files, and there's no format or quality input to switch it to JPEG - it's always PNG, landing at ComfyUI/output/Appstore_<prefix>_<counter>_.png.

Installing and using it

Same pack as the rest: ComfyUI Manager search for "ComfyUI_Appstore", or

cd ComfyUI/custom_nodes
git clone https://github.com/ronaldzgithub/ComfyUI_Appstore
# restart ComfyUI

No model downloads; the dependencies (aiohttp, requests, numpy, Pillow, piexif, websockets) are light and mostly already in a stock ComfyUI.

Troubleshooting

If the appstore panel isn't showing results, the image is almost certainly still saved - check ComfyUI/output/ first, then the frontend; this node does its disk job and only reports up. If you want workflow metadata in your PNGs for local experiments, just use the core SaveImage node instead - there's no reason to route personal saves through a pack whose job is paywalled publishing.

And the same caveat as the rest of this pack: installing it means a third-party, mainland-China-hosted platform gets a connector into your ComfyUI with permissive CORS routes. If all you wanted was a save node, a plain SaveImage does the saving without the plumbing - this one is only worth the network baggage if you're actually publishing to the appstore.