<h1 id="flux-kontext-try-on-workflow-!">Flux-Kontext Try-On Workflow !</h1><pre><code>version 2.0
* compartimentalized workflow
* supports flux-nunchaku
* manually offloads Flux and Phi models from VRAM to cpu</code></pre><p></p><p>Here is my clothing transfer workflow. All you need are two images:</p><ul><li><p>an <strong>image of the subject</strong> you want to dress on</p></li><li><p>an <strong>image with the clothes</strong> you want to transfer</p></li></ul><p>There's no need for prompting as it should work out of the box. To be honest It took me a LOT of trial and error to figure it out. It's a bit complex, but it does the job and it works most of the time.</p><h3 id="word-extraction-from-images">Word extraction from images</h3><p>I use both <strong>Florence2 </strong>to extract captions about the image and <strong>Phi </strong>to sort out the mess. FluxK wants a very specific prompt and that's how we do it, in a lazy way so it's pretty much automatic :)</p><h3 id="subject-outlining">Subject outlining</h3><p>Using <strong>ClipSeg </strong>and stroking mask contours, it helps Flux Kontext... or maybe not ! but still I make a circle around my subject to be clear to FluxK who I want in the final image</p><h3 id="2-step-method">2-step Method</h3><p>It follows a two steps process</p><ol><li><p>Dress up in a swimsuit: I haven't found a better way to remove sleeves and leggings and prevent them from showing on the end product otherwise.</p></li><li><p>Transfer clothing from any image to your subject</p></li></ol><h2 id="consistency">Consistency</h2><p>It's at the same time quite impressive and sometimes disappointing. Sometimes it's perfect sometimes it botches the job and sometimes certain images will refuse to work for some reasons:</p><ul><li><p>difference of scale and angle between images</p></li><li><p>you didn't provide an image with a great size and resolution (I left some info on the topic)</p></li><li><p>fluxk doesn't understand the clothing</p></li><li><p>the clip-l doesn't understand the name of some items</p></li><li><p>the most likely reason: <strong>it's for your own good </strong>(check the section below)</p></li></ul><h2 id="sfw">SFW</h2><p>Flux Kontext will do everything in its power to keep it SFW, and the great part is that it's unlikely to produce offending results, even if input images aren't SFW to start with (check the examples for that). Some type of clothing will not work. Private parts (Crotch, nipples and the lower-exterior part of the cups) must be covered, however input images will be treated regardless. It tends to extend the fabric over these areas to still allow you to process the image.</p><h1 id="feedback-is-welcome!">Feedback is welcome!</h1><pre><code>(in Progress v3.0 - update 2025-09-25)
[x] improving the offload/recall nodes to detect/ignore unsupported models
[x] improving prompts for better fidelity and better transfer overall: Simpler is better Flux can get confused with too much info
[x] removing red outline step: replaced by a red box
[x] replacing Phi by another model: Gemma3:4b
[x] added an optimisation step on the target to prevent replacing face and body of the subject.
[~] developing caching nodes for a consistent workflow. Will be quite handy in many workflows.
[~] removing experimental fluff (compartimentalisation)
[~] cleaning up new workspace

Abandoned:
[.] using a fashion fine tune of Florence2: The only one avaialble is worse!</code></pre><p></p><p></p><p></p>

Files with SHA256: 2706e0d716a7791754442eb9e925371b0a587bcd3755f36a966b1d68a360d8df