-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New Pipeline: FluxFillControlNetInpaintPipeline for FLUX Fill-Based Inpainting with ControlNet #12649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
hi @pratim4dasude can you post a couple of images so we can see the quality of using this pipeline? |
|
thanks @pratim4dasude, looking at the results, it doesn't seem to be on par or better than the current ones we have (qwen-image-edit-plus, kontext). I'm guessing some people will have some specific use case scenarios where they would like this pipeline, are you interested in moving it to a community pipeline in the meantime to measure if people will use it? Just so you know, qwen-image-edit can work with multiple images and condition images too (depth, pose, etc) |
|
Thanks @asomoza for checking it out! Yeah, that makes sense — the results aren’t yet matching qwen-image-edit-plus or kontext, and I get why. This pipeline was more of an experiment around Flux-Fill + separate condition inputs (depth / canny / pose), so it might be useful only for some niche workflows. I’m open to moving it to a community pipeline so others can try it out. Can you help me with the process, or should I just create a new PR under diffusers/examples/community/? Happy to follow whatever you suggest. |
…int.py deleting from main flux pipeline
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Flux fill controlnet pipeline so now it been in the community work and also updated the readme.md
asomoza
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks a lot!
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
|
@bot /style |
|
Style bot fixed some files and pushed the changes. |











What does this PR do
This PR adds a new pipeline — FluxFillControlNetInpaintPipeline — located in pipeline_flux_fill_controlnet_inpaint.py.
This pipeline extends FLUX.1-Fill-dev with full ControlNet support for depth, canny, union, and other conditioning models. It enables fill-style inpainting + ControlNet conditioning in a single unified workflow.
We chose FLUX.1-Fill-dev instead of the main FLUX.1-dev model because the regular model does not handle inpainting or masked edits well, especially when combined with styling from Flux Redux.
This variant is specifically designed for mask-based inpainting and produces far more stable and coherent results in these workflows.
How I identified the gap
Existing FLUX pipelines were split:
There was no single pipeline combining all three.
How to Use the New Pipeline
Below is the updated example with the correct pipeline name and file import:
Who can review
Anyone in the community is free to review the PR once the tests have passed.
I'm new to contributing here, so please feel free to point out mistakes or roast the code if needed - it will help me improve.
@yiyixuxu and @asomoza