-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Add QwenImage Inpainting and Img2Img pipeline #12117
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
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! The PR looks super clean :) Just have some nits about # Copied from
convention we follow. Other than that, looks good to me
Could you also update the qwenimage.md in docs/
folder to reflect these pipelines:
@a-r-r-o-w I’ve finished updating qwenimage.md
to reflect the pipelines and fixed the # Copied from
convention. Please take a look at the changes.
HuggingFaceDocBuilderDev
commented
Aug 12, 2025
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.
@Trgtuan10 You just have to change from diffusers.pipelines.qwenimage.pipeline_qwenimage
in the copied from statement on the pipeline methods to from diffusers.pipelines.qwenimage.pipeline_qwenimage.QwenImagePipeline
Thanks @DN6
@Trgtuan10 Pushed up minor changes to your branch for style and copy checks to pass. FYI you don't need to merge into main on your fork before opening the PR. It's better to open from your working branch.
Uh oh!
There was an error while loading. Please reload this page.
What does this PR do?
This PR introduces support for the QwenImage model in both Inpainting and Img2Img tasks, expanding the model’s creative capabilities and integration within the Diffusers library.
1. Image to Image
Example code
Results at different strengths
0.7
0.8
0.9
1.0
2. Inpainting
Example code
Results at different strengths
Mask
0.7
0.8
0.9
1.0
Before submitting
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?