Petty Paint Image Save
Save to an absolute path — the app's layer folder, not ComfyUI's output dir
- images
Core ComfyUI's Save Image writes into ComfyUI/output and gives you the file back. This node writes anywhere you tell it - and if you're using the petty-paint pack as intended, "anywhere" is the Petty Paint layer directory, which is exactly why the default filepath is the very un-Linux D:\apainter\layers. It's the "hand the finished image back to the app" node, and it doubles as a generic save-to-absolute-path for anyone who wants outputs on a specific disk without touching output.
It's part of the ComfyUI-side integration for Petty Paint, Andrew Porter's web canvas that reimagines your doodles through Stable Diffusion. The app polls its layer folder for new images, and this is how a ComfyUI graph drops them there.
How it works
Feed it an IMAGE batch, pick a format and quality, and it saves every image with a fresh random filename - petty_paint_<10 random chars>.<ext> - into filepath. The overridefilepath input is the interesting one: if you set it, the node ignores filepath entirely and saves into <overridefilepath>/images. That's how the app's per-project storage gets the "images" subfolder it expects. File formats run png, jpg, jpeg, gif, tiff, webp, bmp; quality (1–100, default 100) only really bites for jpg/tiff.
The inputs that matter
images- the IMAGE batch to save.filepath- target folder. Change that Windows default; on Linux it'll happily try to write toD:\apainter\layersand fail.overridefilepath- if set, wins overfilepathand appendsimages.extensionandquality- format and compression.- No outputs - this is a terminal output node.
Installing it
Same pack, same story - Manager search "petty-paint-comfyui-node", or:
cd ComfyUI/custom_nodes
git clone https://github.com/mephisto83/petty-paint-comfyui-node
Restart ComfyUI. Declared dependency is Flask==2.1.2; no model files needed.
Common issues
The big one is silent failure. The save is wrapped in a try/except that just prints - if the target directory doesn't exist, or the path is unwritable, you get no error in the UI and no image on disk. Nothing is created for you. So check the folder exists before you run, and if "nothing saved," look at your terminal log. Also note the random filename means every run writes a new file - if you're iterating, your layer folder fills up fast, and Petty Paint may pick up stale images. Want to save to one exact, predictable path instead? That's what PettyPaintImageStore in the same pack is for.
Inputs (5)
| Name | Type | Default | Description |
|---|---|---|---|
| images | IMAGE | — | |
| filepath | STRING | D:\apainter\layers | — |
| overridefilepath | STRING | — | |
| extension | COMBO | 7 options: png, jpg, jpeg, gif, tiff, webp, +1 | |
| quality | INT | 1001–100 | — |
Outputs (0)
No outputs