<h2 id="introduction">Introduction</h2>Everything written below is based purely on my personal experience and observations. I can’t guarantee everything is correct, so take it as reference material only. Discussion and corrections are always welcome.As an open-source model focused on photorealistic image generation, Z-Image-Base (ZIB) 官方页面 is easily one of the current SOTA models. Its image quality is extremely strong, and its prompt adherence and fine-detail control are honestly on another level. For example, you can modify the style of a single button purely through prompts without noticeably affecting the rest of the image.However, ZIB is much weaker when handling spatial relationships between multiple subjects, especially multiple characters. Basic two-person poses are usually manageable, but uncommon poses often fail badly, with frequent misalignment and anatomical issues. For threesome or more complex interaction scenes, no matter how detailed the prompt is, while it can occasionally generate good results, the overall experience feels more like rolling a gacha. Most outputs end up with broken anatomy or spatial errors.Because of this, I started experimenting with ControlNet + mlutiple processors to guide composition more reliably.I used the following combination:<ul><li><a target="_new" rel="ugc" href="https://huggingface.co/alibaba-pai/Z-Image-Fun-Controlnet-Union-2.1?utm_source=chatgpt.com">Z-Image-Fun-Controlnet-Union-2.1</a></li><li><a target="_new" rel="ugc" href="https://huggingface.co/alibaba-pai/Z-Image-Fun-Lora-Distill?utm_source=chatgpt.com">Z-Image-Fun-Lora-Distill (8 Steps LoRA)</a></li></ul>After testing ZIB + 8 Steps LoRA + ControlNet together, I found that ZIB’s ControlNet can solve certain structural problems, but the resulting image quality still often feels lacking:<ul><li>overall sharpness is weaker</li><li>lighting tends to look flat and gray</li><li>prompts related to lighting respond poorly</li><li>ControlNet strength at <code>1.0</code> often produces terrible-looking results</li></ul>Under the 8 Steps LoRA setup, adjusting CFG (usually between <code>1</code> and <code>2</code>) can sometimes help, but the workflow still feels heavily constrained by the base image. Some reference images even produce extremely strange lighting behavior.Overall, the experience feels very different from SDXL workflows, where high-quality results often work almost out-of-the-box with minimal tweaking. I’ve also seen similar complaints on Reddit about ZIB’s ControlNet implementation feeling relatively weak.Another important issue is that in ZIB, generation resolution directly affects focal length and depth-of-field behavior. Different resolutions can produce dramatically different compositions and camera feel. Solving this became one of the key goals of my workflow.<hr /><h1 id="workflow">Workflow</h1>After a lot of experimentation, I ended up building a relatively simple ControlNet workflow that gave me much more satisfying results.The core idea is straightforward:<ol><li>Use any checkpoint you like together with the 8 Steps LoRA (This is extremely important. For ZIB, the 8 Steps LoRA is almost mandatory in my opinion. It significantly improves image quality and detail rendering. Of course, if your checkpoint already has something similar baked in, you don’t need to add it separately.)</li><li>Use ControlNet together with a suitable resolution — usually a relatively low resolution — and perform a short initial sampling pass (around 2 steps) This stage establishes a solid base latent with correct character positioning and spatial relationships.</li><li>Upscale the latent to the target resolution, then remove ControlNet and continue sampling using only the checkpoint + 8 Steps LoRA This preserves the structural consistency from ControlNet while dramatically improving image quality, lighting, and detail in the second pass. More importantly, you can freely adjust the second-pass resolution without heavily affecting focal length or depth-of-field behavior.</li><li>The “small-resolution first pass + large-resolution second pass” approach also works well outside of ControlNet workflows It helps reduce the coupling between focal length behavior and image sharpness/resolution.</li></ol><hr /><h1 id="recommended-models">Recommended Models</h1>Personally, I use a 1:1 merge of:<ul><li>Big Love</li><li>Pornmaster</li></ul>I feel Big Love performs very well in anatomy and clothing structure, while Pornmaster produces character aesthetics that fit my taste better. The merged result feels surprisingly balanced in actual use.<hr /><h1 id="recommended-sampler">Recommended Sampler</h1>Under ZIB + 8 Steps workflows, I strongly recommend samplers that inject noise at every step. These samplers consistently produce better anatomy and micro-detail quality than more deterministic alternatives.My personal recommendation is:<ul><li>Euler A</li></ul><hr /><h1 id="key-parameters">Key Parameters</h1>In this workflow, there are basically only three major parameters you need to tune.<hr /><h2 id="1.-controlnet-resolution-(first-pass-resolution)">1. ControlNet Resolution (First-Pass Resolution)</h2>The first sampling pass establishes the base composition latent, so this resolution matters a lot.I usually default to:<ul><li>short edge = <code>768</code></li></ul>This feels like a very balanced starting point.In ZIB, lower resolutions effectively produce a “longer focal length / shallower depth-of-field” look:<ul><li>subjects become larger</li><li>background elements become fewer and more compressed</li><li>the model focuses more attention on the main subjects</li><li>prompt responsiveness for character details improves noticeably</li></ul>This parameter can be adjusted depending on your goal:<h3 id="situations-where-lowering-or-increasing-this-resolution-helps">Situations where lowering or increasing this resolution helps</h3><ol><li>You already know the kind of depth-of-field or focal feel you want Adjust this value to match the desired camera look.</li><li>Your subject differs heavily from the reference image For example:<ul><li>different body type</li><li>different pose</li><li>weak prompt responsiveness</li></ul>Lowering the first-pass resolution enlarges the subject and reduces the influence of the original image, making the output follow your prompt more strongly.</li><li>The reference image contains distracting or unwanted elements Lowering the resolution can help suppress them. Though in many cases, adjusting ControlNet strength is even more effective.</li><li>Extremely low resolutions (for example <code>128</code>) are usually too destructive The initial latent becomes too small, causing heavy detail loss and significantly reducing adherence to the reference image.</li></ol><hr /><h2 id="2.-controlnet-strength">2. ControlNet Strength</h2>This controls how strongly ControlNet influences the generation.I usually use:<ul><li><code>1.0</code></li></ul>Without the second sampling pass, <code>1.0</code> often produces awful-looking results. But in the dual-sampling workflow, <code>1.0</code> works surprisingly well:<ul><li>strong structural adherence</li><li>while still allowing the second pass to restore image quality and details</li></ul><hr /><h2 id="3.-final-resolution-(second-pass-resolution)">3. Final Resolution (Second-Pass Resolution)</h2>This is your final upscale sampling resolution.I usually use:<ul><li>long edge = <code>1536</code></li></ul>This tends to produce clean and detailed images while keeping rendering mistakes relatively manageable.Since the base latent structure has already been established during the first pass, the second-pass resolution has much less influence on focal length and depth-of-field behavior. This gives you much more freedom to scale image quality independently.Higher resolutions produce:<ul><li>more sharpness</li><li>more texture detail</li><li>richer micro-details</li></ul>But in very complex scenes, excessively large resolutions can also introduce:<ul><li>incorrect clothing details</li><li>broken background objects</li><li>random hallucinated elements</li></ul>In most cases, I avoid going beyond:<ul><li><code>1920</code></li></ul>The second-pass resolution generally has relatively little impact on prompt adherence.<hr /><h1 id="personal-experience-and-tuning-tips">Personal Experience &amp; Tuning Tips</h1>My default starting setup is usually:<ul><li>first-pass resolution: <code>768</code></li><li>ControlNet strength: <code>1.0</code></li><li>second-pass resolution: <code>1536</code></li></ul>Then I adjust from there based on the results.<h3 id="if-the-generated-subject-differs-too-much-from-what-i-want">If the generated subject differs too much from what I want</h3>I primarily reduce the first-pass resolution to weaken the influence of the original image.If that still isn’t enough — or if the resolution becomes so low that important details disappear — I also reduce ControlNet strength.Typical lower limits for me are roughly:<ul><li>first-pass resolution ≥ <code>384</code></li><li>strength ≥ <code>0.8</code></li></ul>Though in special cases, I’ve gone as low as:<ul><li>resolution = <code>256</code></li><li>strength = <code>0.5</code></li></ul><hr /><h3 id="if-the-reference-image-contains-many-characters-or-very-small-subjects">If the reference image contains many characters or very small subjects</h3><code>1536</code> may not provide enough detail density.In those cases, I increase the second-pass resolution moderately to improve detail rendering.Usually I stay below:<ul><li><code>1920</code></li></ul><hr /><h3 id="sampling-step-distribution">Sampling Step Distribution</h3>I usually use:<ul><li>first pass = <code>2</code> steps</li></ul>You can adjust this depending on your needs.For example:<ul><li>if adherence to the reference image is insufficient, you can slightly increase first-pass steps</li></ul>Personally, I generally keep:<ul><li>first pass ≤ <code>3</code> steps</li><li>second pass ≥ <code>6</code> steps</li></ul><hr /><h3 id="when-nothing-seems-to-work">When nothing seems to work</h3>If repeated parameter tuning still fails to produce the result I want, I often take the best partially successful output and use it as the new reference image.Then I repeat the process iteratively.Surprisingly often, this works much better than endlessly fighting the original reference image.<hr /><h1 id="end">End</h1>Hopefully this workflow can help people struggling with ZIB ControlNet setups.And finally, good luck to everyone — hope you all generate the images you actually want.

Files with SHA256: 8f502057f9e9deaf30518d10226fd53ffd6d3fd062d36c1f97ae6ac3525a42c6