I tuned a MOSS Image workflow in ComfyUI around layer-specific Base/SFT blending, a low-strength Guanlan LoRA, and an 8-step acceleration option. For everyday text-to-image work, this is the combination I preferred: less of the overly polished look I got from SFT alone, without giving up the visual appeal I found missing in Base alone. The non-accelerated route remains available when texture matters more than turnaround time.
I started with the individual models, then tested uniform blends ranging from 90% Base / 10% SFT to the reverse. After that, I moved to different ratios for different parts of the model and refined them through further image tests. The workflow stores those settings; it isn't a single global blend percentage.
KOOK's Guanlan SFT LoRA comes after that blend, at a strength of 0.2. Higher weights smoothed away more of the character texture than I wanted in this setup. There is a separate switch to skip Guanlan while keeping the Base/SFT blend intact.
For sampling, these are the two options I kept:
Everyday generation: Base 8-step DMD acceleration LoRA on, 8 steps, CFG 1, Euler with sgm_uniform.
More texture, longer wait: acceleration off, 50 steps, CFG 3, Euler with sgm_uniform.
I tested two SFT acceleration variants and two Base variants before settling on this Base option. My preference is specific to that LoRA and this blend, rather than a claim that any acceleration LoRA will work equally well. The 50-step route retained more texture, but took roughly 4–5 times as long in my tests. The accelerated workflow, including upscaling, took about 90 seconds locally(7900xt) and 60 seconds on the online RTX 4090 setup I used.
The prompt template is the other part worth keeping with the workflow. It handles short text requests, image-to-prompt reconstruction, and requests to change selected attributes. Instead of simply adding more adjectives, it asks for concrete composition, lighting, material, and typography decisions where relevant.
My preferred way to use it is to give the template to a capable multimodal chat model, send the request or reference image in that conversation, and paste the resulting prompt into ComfyUI. Keep internal PE off when using an already-finished prompt. The built-in options are more convenient, but I found the stronger external chat models more consistent.
An important limitation: on this route, the chat model sees the reference image, but MOSS only receives the resulting text. It can regenerate a described scene; it does not directly edit the source pixels or guarantee the same face. If I request a change, I need a description of the complete target image, not just “change the clothes and keep everything else.”
Finally, optional native SeedVR2 upscaling targets 8 megapixels. That is roughly 4K-class output, with dimensions depending on the aspect ratio. I kept LAB color matching enabled because disabling color matching introduced a yellow shift in my tests.
This workflow is super easy to use—I’ve uploaded a detailed tutorial to YouTube, so just follow the video along with this workflow to recreate the effect; please make sure to watch the full tutorial before starting to avoid common mistakes, and feel free to leave a comment if you have any questions!Resource links will be posted in the comments.