Inpaint workflow V2
GUIDE FOR V2 WORKFLOW IS LOCATED HERE
06/12/2025
-Added ability to control mask opacity.
-Changed sampler to prevent problems with generation.
-Adjusted guide.
04/12/2025
-Added ability to do colormatch. Changing colormatch setting to 1 will try to match the color of the image.This is good if using VAE that changes color between encode/decode cycle or using different lora/model.
Older:
-Added differential diffusion
-Cleaned the workflow
-Created guide which can be found HERE
-This should work with 1.5 too, did not test.
Inpaint workflow XL V1.1
Due to request updated to work with XL. It is somewhat barebones compared to 1.5. Does not have segmentation or controlnet models currently.
I have a bit outdated comfyui, let me know if it is throwing some errors.
Description
-Added colormatch.
Using 1 on color match will try to match the color to the original image.
-Added note for all the settings
FAQ
Comments (11)
In my recent runs, the inpaint workflow renders the masked area as a solid green overlay instead of properly blending the inpainted result.
You have helped me a lot in my eternal search for the ideal. Thank you, Great man
I don't know why I didn't leave a comment earlier.
(～￣▽￣)～ glad you like it
It would be great to be able to resize the latency space. Working with the square limits our possibilities. I have not yet figured out how to bring the inpaint from Forge closer to Comfy.
When i started building the inpaint workflow over 2 years ago, my idea was to replicate how inpainting worked in A1111. It has come long way since then and i personally still use slightly edited version of the workflow every time i inpaint. I don´t exactly know how it differs from current forge as i have not used it in year or so.
Main reason why i created it to cut square was to have better results for the inpainting. For XL for example you are going to get good results mostly on specific resolutions (1024x1024) as example. If it uses the cut resolution on generation, it could cause distortion and consistency issues with higher denoise and the results will not be as good as the generation is done on the lower resolution image (unless the cut area size is larger than the 1024x1024 or which ever resolution you are generating with).
If you want to inpaint large area on image, at that point inpainting with the full image might be better choise. Getting detail on images was always the focus for this workflow.
Thank you for the comments (～￣▽￣)～
@PotatCat 💜
I don't know if it's just me, but ComfyUI can never find the "Images to RGB" node not matter how many times I reinstall the Impact Pack
You could try remaking the node
Also isn´t that node from WAS node suite
e: yeah it is from this pack: https://github.com/ltdrdata/was-node-suite-comfyui should be able to find with comfyui manager