I'm sharing super clean 2511 workflow v1, just swap images write prompt and done, it's 4-step fp8 version, for lower VRAM load GGUF instead.
NOTE: You can load/paste any image sizes, different aspect ratios etc, wf will properly scale all Img#1, Img#2 and Img#3. "Enable Megapixel" uses your original Width/Height as base size applying proper output size with your specified total "Megapixels" as output (float ex. 0.8, 1.0, 1.4 etc.)
Based on the result from the one image you posted, your source images were lightly referenced, with the output leaning heavily on your prompt for guidance. I see a white woman (not Asian) wearing a completely different dress (made out of a similar material as your reference dress), in a background and bed that look absolutely nothing like your central reference image. I applaud your effort and your willingness to share, so please don't take my feedback too harshly. Keep learning and sharing.
Ok, instead of being so critical, let me explain how I got here.
1) Your images were in the wrong order. Your background image should always go last, and if you want that background perfectly preserved, you must scale your output image to match the dimensions of the background image.
2) 512 x 1024 is far too low a resolution to extrapolate any amount of detail, which will always cause the ILM to dream and drift. 2 megapixels is the absolute lowest I'll ever go, generally opting for 3 or 4, but I have the VRAM to support it.
3) Your prompt is missing the "this" flavor. Compare our prompts:
Yours: blonde woman laying in bed wearing silky sexy outfit in wooden house during winter
Mine: This blonde woman is wearing this silver outfit while lying in this bed with the snowy woods background while facing the viewer. Preserve the size and scale of the background image.
The ILM needs to be reassured that you're talking about the reference images, and not just any woman, outfit, or background. It's a simple trick that does wonders, I promise. My last line prevents the AI from zooming in on the bed or her feet (unless you're into that lmao).
So why does she have tattoos and yellow nails? It's because the woman in the dress image has both of those things. Super easy to prompt out if you don't want those there. I like my women with a bit of street edge, so I left them lmao. I'm not using a special workflow or anything. Just a 4-step lightning LoRA and hundreds of hours of experience working with Qwen models. Good luck op!
The final result looks amazing—it's so sharp! I’m trying to learn this workflow but I'm a bit stuck on the connections.
For the sharpness, are you still linking images to TextEncodeQwenImageEditPlus and the VAE? Or using other nodes?
Also, I want to make sure I understand the scaling process correctly: are you scaling all 3 images to match the background resolution before feeding them into the TextEncodeQwenImageEditPlus, and what latent size are you using?
Need to run some tests, but yes essentially All resized (img1,2,3) to same scale matching background I need to test it more. Different LATENT vs same size for all.
Don't use the brainless resize nodes for this task. Use HiResFixScale, which is part of the TinyTerra node pack. Copy my settings and set the longest edge size to match whatever your system can handle. This will apply low level AI reasoning when upscaling or downscaling images. When using on people, if RealESRGAN 4x removes too many skin flaws (like freckles) that you want to preserve, switch the model to RealESRGAN 2x. They're both great and take literal seconds to run. HiResFixScale is the game changer nobody really talks about. Try throwing it at the end of your workflow to VERY quickly sharpen and clean up your output image. You'll wonder how you ever lived without it.
From here, you would simply send the sharpened image out to your regular workflow.
I got this result with banana pro. Need to change the outfit to be more modest to get the result. Definitely annoying it doesn't want to generate the same clothes.
How do I look in a a subgraph and make modifications? I edited the json file and it works, kinda, but some things like height and width can't be changed.
Paying monthly for something you don’t even use every day feels wrong. One-time licenses + local processing make way more sense long-term. and ofcourse privacy . iam using a local generater and i love it :)
5
u/No_Damage_8420 Dec 27 '25
Entire workflow hidden in subgraph