Disclaimer: This article was generated by Google Gemini based on information found on Discord channels and the model’s general ability to search for information on the internet. The information presented here may be incorrect or biased.

A simple version generated from this article can be found here: https://rentry.org/zimage-base-tldr

Comprehensive Technical Report on Z-Image Base LoRA Training Paradigms within the AI-Toolkit

The emergence of the Z-Image Base model, a 6-billion parameter Diffusion Transformer (DiT) architecture developed by the Tongyi-MAI group, has necessitated a paradigm shift in the strategies employed by the AI-Toolkit community for low-rank adaptation.[1] Prior to this foundation model's release, practitioners were primarily constrained to the Z-Image Turbo variant, which achieved high-speed generation through Decoupled Distribution Matching Distillation (Decoupled-DMD).[4] While Turbo offered sub-second generation times and high aesthetic appeal, the distillation process introduced a "compressed" latent space that frequently resisted complex identity preservation and exhibited significant aesthetic biases toward specific demographics.[6] The release of the undistilled Base model—capable of traditional multi-step denoising with explicit Classifier-Free Guidance (CFG)—promised a more flexible and high-fidelity training target, yet early empirical results suggest that the transition from Turbo-based training to Base foundation training is fraught with technical instability, unforeseen failure modes, and a non-linear relationship between hyperparameters and convergence.[7]

Theoretical Divergence and Structural Architecture

The primary distinction between Z-Image Base and Turbo lies in the mechanism of their weight distributions and how they respond to low-rank weight updates. Z-Image Turbo is an 8-step model where the guidance is internalized, effectively removing the need for traditional CFG during inference but making the model highly sensitive to "Turbo drift"—a state where LoRA updates undo the distillation effects, requiring the model to return to high step counts for coherent output.[10] The AI-Toolkit community initially addressed this by using "training adapters" or "De-Turbo" checkpoints, which temporarily expanded the model to a pseudo-undistilled state for training purposes.[11]
With the official release of Z-Image Base, the community has moved toward direct training on the foundation model. This foundation shares the 6B parameter S3 DiT architecture but operates without the constraints of few-step distillation.[1] Consequently, the model exhibits a higher degree of prompt adherence and structural variety, particularly in complex scene compositions that the distilled version might over-simplify.[5] However, this complexity results in a training environment where likeness is significantly more difficult to "lock in" than in the distilled variant.[6] Community findings indicate that while Turbo-trained LoRAs typically reach peak fidelity at approximately 100 steps per image, Base-trained models often require 300 steps or more to achieve perceptible resemblance.[6]

Parameter Metric Z-Image Turbo (Distilled) Z-Image Base (Foundation)
Model Nature Knowledge Distilled [4] Foundation Backbone [3]
Inference Path 8-step pathway [4] 20-50+ steps [3]
Guidance Logic Baked-in / CFG 1 [10] Traditional CFG 4-7 [1]
Latent Space Compressed / High Reward [4] Broad / Unfiltered [3]
Convergence Speed Rapid (~1k-2k steps) [7] Slower (~3k-8k+ steps) [6]

The second-order implication of this structural difference is the "delta mapping" problem. Community researchers have observed that a LoRA trained on Z-Image Base does not map its learned weights linearly to the Turbo model.[6] Because the internal representations differ significantly, a standard 1.0 strength application of a Base LoRA on a Turbo model often yields no visible result.[6] To force identity transfer, users must often scale the LoRA strength to 2.0 or 2.5, which frequently causes "model collapse" in the Turbo weights, introducing high-frequency noise and anatomical distortions.[6]

Hyperparameter Optimization and Learning Rate Paradoxes

The most contentious area of community discourse involves the identification of an optimal learning rate (LR) for Z-Image Base training. The empirical data suggests that Z-Image Base does not adhere to the 1 × 10^(-4) standard that was effective for SDXL or initial Z-Image Turbo adapters.[2] Instead, the community has split into two competing schools of thought: the "Aggressive High-LR" method and the "Precision Low-LR" method.

The Aggressive High-LR Strategy

A subset of advanced practitioners discovered that increasing the learning rate to 1 x 10^(-3) — a value traditionally considered catastrophic for LoRA training—yielded "perfect" likeness in a fraction of the time previously required.[7] This approach is predicated on the hypothesis that the 6B parameter transformer weights in the undistilled model are sufficiently robust to absorb larger weight shifts without losing the global structural priors of the foundation.[7] Users employing this strategy reported reaching near-flawless character likeness at approximately 2,500 steps, compared to failing to achieve likeness at 10,000 steps with lower rates.[7] The critical caveat to this strategy is that it requires a highly consistent dataset; any "noise" in the dataset images (e.g., inconsistent lighting or poor captions) is amplified by the aggressive LR, leading to rapid overbaking.[7]

The Precision Low-LR and PPSF Paradigms

Conversely, many users recommend a more conservative learning rate range of 2 x 10^(-5) to 6 x 10^(-5), paired with a high epoch count.[7] This strategy is often coupled with the use of adaptive optimizers. A significant development in the AI-Toolkit community is the introduction of "Prodigy-Plus-Schedule-Free" (PPSF) via specific pull requests (e.g., PR #601).[7] PPSF automates the learning rate discovery process, essentially allowing the toolkit to identify the optimal LR dynamically based on the gradient flow of the specific dataset.[7] Logs from community experiments using Prodigy show the optimizer frequently settling near 2.6 x 10^(-4) for large, diverse datasets, while smaller character sets tend to hover around 1 x 10^(-4).[7]

Optimizer Method Observed Success Range Community Consensus
AdamW (Standard) 1e-4 to 3e-4 Default but often under-performs for Base identity.[2]
AdamW (Experimental) 1e-3 High risk/reward; effective for "locking in" likeness.[7]
Prodigy (Adaptive) D ≈ 1.0 (coefficient) Reliable for complex or multi-concept sets.[7]
PPSF (Auto) AutomatedDiscovery Most stable; reduces overbaking and "gradient shimmering".[7]

The third-order insight derived from these experiments is that Z-Image Base is highly sensitive to the "starting point" of training. If the initial likeness is not perceptible within the first 1,000 steps, users frequently report that increasing the step count indefinitely leads to "melting" or "identity bleed" rather than improved fidelity, suggesting a threshold where the model's ability to map new vectors to existing concepts becomes saturated.[7]

Architectural Configuration: LoRA vs. LoKr

The AI-Toolkit offers multiple adapter architectures, with the Kronecker Product (LoKr) emerging as a superior alternative to standard LoRA for Z-Image Base.[18] LoKr's primary advantage is its parameter efficiency, allowing it to capture identity with a smaller file footprint and fewer trainable weights, which acts as an implicit regularizer.[7]

The Factor 4 LoKr Meta

The community has identified a "Factor 4" LoKr configuration as the current gold standard for character preservation.[7] In the AI-Toolkit's LoKr implementation, the "factor" parameter is inversely proportional to the complexity of the adapter; a factor of 4 creates a more streamlined representation than a factor of 2.[18] Users report that factor 4 LoKr models reach 90-95% likeness within 1,000 to 1,500 steps, while maintaining the base model's original color depth and texture variety.[7] Furthermore, LoKr appears to be less prone to the "plastic skin" effect often observed in high-rank standard LoRAs.[18]

Linear Rank and Alpha Scaling

When standard LoRA is utilized, community consensus favors a rank/alpha of 32/32 or 64/32 for character training.[2] Ranks lower than 32 (e.g., 8-16) are generally found to be too "weak" for the 6B parameter DiT blocks, failing to capture subtle features like birthmarks, tattoos, or complex skin textures.[5] A critical technical observation is that high-rank LoRAs (rank 128+) exhibit diminishing returns and significantly increase the risk of overfitting, particularly on small datasets of 20-30 images.[5] Some users have experimented with "decoupled alpha," setting rank to 64 and alpha to 32, which theoretically provides more capacity for detail without increasing the overall magnitude of the weight injection.[7]

Specific Layer Targeting

Advanced practitioners have began leveraging network_kwargs to restrict training to specific transformer blocks.[7] Research into the Z-Image transformer architecture identifies that subject identity is heavily concentrated in the to_v (Value) attention projections and the SwiGLU-based Feed-Forward Network (FFN) blocks (w1, w2, w3).[22] By utilizing the only_if_contains parameter in the toolkit config to target layers 17 through 23, users have successfully trained LoRAs that preserve character identity with absolute fidelity while leaving the model's understanding of global lighting, style, and composition completely untouched.[7] This granular control is essential for creating "stackable" LoRAs that do not fight for control over the image's aesthetic tone.[7]

Dataset Engineering and Advanced Captioning Strategies

The shift toward Z-Image Base has underscored the importance of the Qwen 4B text encoder, which functions more as an integrated reasoning engine than a simple CLIP-style tag matcher.[5] This architectural choice by Tongyi-MAI means that training success is now more dependent on linguistic nuance than on raw image count.[5]

Natural Language and integrated Prompting

The community has largely moved away from the comma-separated tagging methods of the SDXL era (e.g., "woman, blonde, sunset").[7] Instead, Z-Image Base responds best to full, descriptive natural language captions.[5] This is because the model utilizes its integrated "Prompt Enhancer" during training to interpret context beyond literal descriptions.[5] Practitioners recommend writing captions as if they were actual prompts (e.g., "A high-fidelity photo of ffFred wearing a blue velvet suit, standing in a brightly lit gallery").[7]
A significant finding regarding captioning is the "detail leakage" effect. If a dataset image contains an element that is not explicitly captioned (e.g., a specific background plant or a visible watermark), the model will associate that element with the target identity or trigger word.[7] Conversely, "over-captioning"—where every pixel is described—can dilute the model's focus on the character's face, leading to weak likeness.[7] The optimal balance found by users involves describing the subject, their action, their clothing, and the environment in 2-3 concise sentences.[7]

The Grey Background Meta

One of the most actionable findings from recent Discord discussions is the effectiveness of using a neutral grey background (rgb(128,128,128) or #808080) for character training images.[7] While white backgrounds were once standard, users reported that white caused a "high-key" lighting bias that made the characters difficult to integrate into dark or cinematic scenes.[7] Grey backgrounds act as a "latent neutral" space, reducing background noise and allowing the model to isolate the subject's geometry and skin tones more effectively.[7]

Trigger Word Nuances

The debate over the "Trigger Word" input field in the AI-Toolkit UI continues.[7] The current consensus suggests that the UI input field is often redundant and potentially harmful if the trigger is already included in the text captions.[7] Redundant triggers can lead to "prompt bleed," where the model sees the word twice (e.g., "ffFred ffFred...") and attempts to render the name as text on a t-shirt or background sign.[7] Experienced users recommend "baking" the trigger word directly into the .txt caption files and leaving the UI trigger field blank.[7] Furthermore, using unique, semi-meaningful tokens (e.g., "ffFred") is preferred over random strings (e.g., "xzy123"), as the Qwen text encoder can more easily map meaningful prefixes to the human vector space.[7]

Advanced AI-Toolkit Features and Optimization

The AI-Toolkit exposes several advanced parameters—Differential Guidance, Differential Output Preservation, and Caching—that significantly alter the training dynamics of Z-Image Base.

Differential Guidance (DG)

Differential Guidance is an experimental training-time guidance term that focuses updates on "what should change" relative to the base model.[2] For Z-Image Turbo, a DG scale of 3 is considered standard for accelerating convergence.[11] However, for Z-Image Base, the results are highly polarizing. While some users report it helps likeness emerge faster, others claim it is the primary cause of "body horror" and monstrous anatomical deformations in Base LoRAs.[7] The third-order insight here is that DG might be over-amplifying the delta in the undistilled weights, leading to unstable gradients. Most successful Base character LoRAs reported recently have either disabled DG or used a very low scale (1.5-2.0).[7]

Differential Output Preservation (DOP)

DOP is a regularization strategy that compares the base model's output with the LoRA-active output at each step, penalizing changes to elements outside the trigger word's scope.[2] This feature is vital for preventing "identity bleed," where a LoRA forces the trained face onto every human figure in a scene.[7] However, practitioners must note that DOP is technically incompatible with "Cache Text Embeddings" because it requires the text encoder to generate two different prompt versions (trigger and preservation class) at every step.[24] Users must choose between the VRAM efficiency of caching and the identity control of DOP.

Caching and Throughput Efficiency

For users on 16GB-24GB hardware, caching latents and text embeddings is essential.[7] Caching latents saves the VAE-encoded versions of the dataset to disk, while caching text embeddings pre-processes all captions through the Qwen 4B encoder.[7] On an RTX 5090, enabling both caching mechanisms can drop iteration times from over 4 seconds per iteration (s/it) to approximately 1.0-1.2 s/it.[7]

Hardware Resolution Batch Caching Status Speed (s/it)
RTX 5090 1024 1 Latents + TE [7] 1.0 - 1.2
RTX 5090 1024 1 None [8] 3.8 - 4.2
RTX 4060 Ti (16GB) 1024 1 Latents + TE [8] 10.0 - 12.0
RTX PRO 6000 1024 1 Latents + TE [7] 1.2 - 1.5

The community also warns of a "Loading Transformer" hang on Linux systems, which is often a result of subprocesses desyncing during the initialization phase of Z-Image Base training.[7] Using the "Low VRAM" mode in the AI-Toolkit can mitigate this by trading speed for memory safety, performing LoRA fusing in smaller chunks rather than loading the entire 6B parameter model at once.[7]

Empirical Failure Modes and Technical Troubleshooting

Training Z-Image Base LoRAs has introduced unique failure patterns that were not prevalent in the SDXL or Flux.1 eras.

The Blurry Face and Detail Degradation

A common complaint is that Base LoRAs produce "blurry faces" or "muddy details," even when the training images were high-definition 1024px captures.[7] This is frequently observed in the 1,500 to 2,500 step range.[7] The community's analysis suggests this is a "resolution memorization" issue; if trained only at 1024, the model learns the pixel-perfect representation of the dataset but fails to generalize the character's features when rendered at different compositions or distances.[7] The consensus solution is to utilize a multi-resolution approach, ticking the 512, 768, and 1024 buckets.[7] This forces the model to learn the identity across multiple densities, significantly improving facial clarity in diverse scenes.[7]

Ethnic Confusion and Demographic Bias

Users have documented significant "ethnic confusion" in Z-Image Base.[7] A notable example includes prompts for Indonesian women resulting in Nigerian facial features and skin tones.[7] This suggests that the Base model's foundation dataset may be less balanced than the RLHF-tuned Turbo variant.[7] Similarly, the model exhibits an "age bias," where prompts for "girl" frequently default to children rather than young adults.[7] Training a LoRA on a specific identity can often fix this, but practitioners must be highly explicit in their captions regarding the target's ethnicity and specific age to override these underlying foundation biases.[7]

Training Artifacts: High-Frequency Noise and "Body Horror"

Unlike the "plastic" smoothing of Turbo, Base training instability often manifests as "high-frequency noise"—a gritty, grainy texture that permeates the image.[7] This is usually a sign of an excessive learning rate or poor weight decay settings.[2] "Body horror"—the generation of extra limbs or melted anatomy—is also reported as a frequent failure mode, particularly when using aggressive Differential Guidance or when training complex poses without sufficient dataset variety.[7]

Cross-Model Interoperability and Inference Scaling

The relationship between Base-trained LoRAs and Turbo-model inference is one of the community's most active research areas.

The Scaling Requirement

Because Z-Image Turbo is a distilled representation of the Base model, the "distance" between the two models' latent spaces is significant.[6] A LoRA trained on Base represents a delta relative to a different set of weights.[6] Consequently, at a strength of 1.0, a Base LoRA applied to a Turbo model typically does nothing.[6] Practitioners have found that a strength of 2.0 to 3.0 is often required to "see" the LoRA's effect on Turbo.[7]

Fidelity Gains on Turbo

Interestingly, despite the scaling requirement, some users argue that Base-trained LoRAs are actually superior when used on Turbo at high strengths.[7] The reasoning is that the Base model's training process is "cleaner"—it doesn't have the aesthetic "guardrails" or distillation artifacts of the Turbo model.[7] When pushed into the Turbo environment at 2.5 strength, these LoRAs often exhibit better finger anatomy and eye detail than a LoRA trained directly on Turbo with an adapter.[7]

Evaluation Metrics and the "Marvel Style" Test

To identify the optimal checkpoint, users have developed several subjective but effective tests:

  • The Marvel Comic Style Test: Prompt the character in a "Marvel Comic Book Style." If the result is a recognizable character in comic art, the model is generalized. If it is a realistic face "stamped" onto a comic background, the LoRA is overfitted.[7]
  • The Off-Prompt Test: Prompt for an unrelated subject (e.g., "a monkey on a bike"). If the monkey has human eyes or the subject's features, the LoRA has "bled" into the base model too deeply.[7]
  • The 5090 Baseline: On an RTX 5090, a character LoRA should hit a 90% likeness "sweet spot" at approximately 1,500-2,000 steps with a 30-image set. If it takes 10,000 steps, the learning rate is likely an order of magnitude too low.[7]

Conclusions and Practical Recommendations

The transition to Z-Image Base training represents a move toward professional-grade fidelity at the cost of increased technical complexity. While the model is more volatile than its distilled sibling, the community has identified several empirically validated paths to success.

Consolidated Best Practices

Variable Recommendation for Character LoRAs Recommendation for Style LoRAs
Dataset Size 20-30 high-res curated images [7] 50-100 diverse images [5]
Background Neutral Grey (rgb(128,128,128)) [7] Original consistent background [17]
Captioning Natural Language / JoyCaption / Qwen3-VL [5] Natural Language / Style-focused [17]
Architecture LoKr (Factor 4) [7] standard LoRA (Rank 8-16) [19]
Optimizer PPSF or Prodigy (D coef ≈ 1) [7] AdamW8bit 16
Learning Rate 1e-4 (Conservative) or 1e-3 (Experimental) [7] 5e-5 to 1e-4 [21]
Step Target 3,000 to 5,000 steps [7] 2,000 to 3,000 steps [23]
Timestep Type Sigmoid (Detail focus) [2] Weighted (Style focus) [2]

Actionable Strategic Findings

The following synthesis identifies the high-confidence actions a practitioner should take when training Z-Image Base models:

  1. Prioritize Dataset Specificity over Volume: The most common cause of failure in Z-Image Base training is the use of a large, noisy dataset. A set of 20 high-quality images with diverse angles but consistent identity is significantly more effective than 100 images with varied lighting and extraneous objects.[7]
  2. Transition to Grey Backgrounds: To minimize background bias and improve lighting flexibility during inference, practitioners should edit their character datasets to use neutral grey backgrounds. This removes the "high-key" bias associated with white backgrounds and prevents environmental leakage.[7]
  3. Employ Multi-Resolution Bucketing: Ticking the 512, 768, and 1024 resolution buckets is mandatory for avoiding "blurry face" syndrome. This forces the model to learn the identity across multiple spatial scales, which is critical for the Base model's non-distilled latent space.[7]
  4. Bake Triggers into Captions: Do not rely on the AI-Toolkit's UI trigger word input. Instead, use a unique name (e.g., "ffFred") and integrate it into every natural language caption. This prevents redundant tokens and "trigger word bleed".[7]
  5. Utilize LoKr for Identity: For single-character likeness, the Factor 4 LoKr configuration consistently outperforms standard LoRA in the Z-Image Base ecosystem, offering faster convergence and better color retention.[7]
  6. Verify via External Sampling: Internal AIT samples for Z-Image Base are frequently reported as "unreliable" or "garbage." Users should save checkpoints every 500 steps and test them in a standalone ComfyUI workflow using the Euler or ClownsharKSampler for an accurate assessment of progress.[7]

The community's understanding of Z-Image Base is rapidly evolving. While early users were "underwhelmed" by the foundation's initial difficulty compared to Turbo, the discovery of specific "metas"—such as Factor 4 LoKr and the 1e-3 learning rate fix—is closing the gap. As community fine-tunes like Chroma and Juggernaut variants emerge, Z-Image Base is expected to become the primary vehicle for high-fidelity personalized content creation, finally fulfilling the promise of a truly undistilled 6B parameter playground.[7]

References

  1. Z Image Turbo vs Base 2026: Which Model to Choose? - PXZ AI, accessed January 30, 2026, https://pxz.ai/blog/z-image-turbo-vs-base
  2. Ostris AI Toolkit LoRA Training for Diffusion Model Fine-Tuning | RunComfy, accessed January 30, 2026, https://www.runcomfy.com/trainer/ai-toolkit/getting-started
  3. Z-Image-De-Turbo Free Image Generate Online, Click to Use! - Skywork ai, accessed January 30, 2026, https://skywork.ai/blog/models/z-image-de-turbo-free-image-generate-online/
  4. Z-Image-Turbo-DeJPEG-Lora Free Image Generate Online, Click to Use! - Skywork.ai, accessed January 30, 2026, https://skywork.ai/blog/models/z-image-turbo-dejpeg-lora-free-image-generate-online/
  5. Z-Image Turbo Complete Guide 2025: Fast AI Image Generation & LoRA Training, accessed January 30, 2026, https://dev.to/czmilo/z-image-turbo-complete-guide-2025-fast-ai-image-generation-lora-training-1013
  6. About LoRAs created with Z-Image Base and their compatibility with Z-Image Turbo. : r/StableDiffusion - Reddit, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1qpdkry/about_loras_created_with_zimage_base_and_their/
  7. ostris_useful_chat.txt (undisclosed copy of Discord discussion since the Z-Image Base release, January 2026).
  8. Z-Image Base Lora Training Discussion : r/StableDiffusion - Reddit, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1qoorck/zimage_base_lora_training_discussion/
  9. Z-Image Base vs Turbo : r/StableDiffusion - Reddit, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1qolfkn/zimage_base_vs_turbo/
  10. FLUX.2 [dev] LoRA Training Guide with Ostris AI Toolkit | RunComfy, accessed January 30, 2026, https://www.runcomfy.com/sitemap34fkp9.xml/trainer/ai-toolkit/flux-2-dev-lora-training
  11. Z-Image LoRA Training (Z-Image Turbo + De-Turbo) with Ostris AI Toolkit - RunComfy, accessed January 30, 2026, https://www.runcomfy.com/sitemap34fkp9.xml/trainer/ai-toolkit/z-image-turbo-lora-training
  12. Train Z Image Turbo LoRA on Windows/Linux - Stable Diffusion Tutorials, accessed January 30, 2026, https://www.stablediffusiontutorials.com/2025/11/z-image-turbo-lora-training.html
  13. I think we're gonna need different settings for training characters on ZIB. : r/StableDiffusion, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1qpbgx4/i_think_were_gonna_need_different_settings_for/
  14. How to Train a Z-Image Turbo LoRA Using the Ostris AI Toolkit | Prompting Pixels, accessed January 30, 2026, https://promptingpixels.com/tutorial/z-image-turbo-lora-training
  15. What Z-Image Lora Training Settings Are You Using? : r/StableDiffusion - Reddit, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1pf9md1/what_zimage_lora_training_settings_are_you_using/
  16. LTX-2 LoRA Training Guide with Ostris AI Toolkit - RunComfy, accessed January 30, 2026, https://www.runcomfy.com/trainer/ai-toolkit/ltx-2-lora-training
  17. Qwen 2512 LoRA Training Guide with Ostris AI Toolkit - RunComfy, accessed January 30, 2026, https://www.runcomfy.com/trainer/ai-toolkit/qwen-image-2512-lora-training
  18. LoKr Outperforms LoRA in Klein Character Training with AI-Toolkit : r/StableDiffusion, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1qgx52y/lokr_outperforms_lora_in_klein_character_training/
  19. The Z-Image Turbo Lora-Training Townhall : r/StableDiffusion - Reddit, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1q3tcae/the_zimage_turbo_loratraining_townhall/
  20. I trained a Z-image lora on AI Toolkit with rank 128 and 4000 steps. When I add my lora to a Z-image workflow, the resulting images are poor. It's not the dataset, as I've used it multiple times. It's a character lora. How can I make my lora look more detailed - Reddit, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1pu26vb/i_trained_a_zimage_lora_on_ai_toolkit_with_rank/
  21. Engineering Notes: Training a LoRA for Z-Image Turbo with the Ostris AI Toolkit, accessed January 30, 2026, https://huggingface.co/blog/content-and-code/training-a-lora-for-z-image-turbo
  22. [LoRA Guide] Z Image Turbo Training with AI-Toolkit and Merging It!, accessed January 30, 2026, https://blog.hinablue.me/lora-guide-z-image-turbo-training-with-ai-toolkit-and-merging-it/
  23. (Re-up) Best Z-Image Training LoRA training settings + workflow (For Ostris AI-Toolkit), accessed January 30, 2026, https://www.reddit.com/r/comfyui/comments/1put7gs/reup_best_zimage_training_lora_training_settings/
  24. FLUX.2 [dev] LoRA Training Guide with Ostris AI Toolkit | RunComfy, accessed January 30, 2026, https://www.runcomfy.com/trainer/ai-toolkit/flux-2-dev-lora-training
  25. Wan 2.2 T2V 14B LoRA Training with AI Toolkit | Text-to-Video - RunComfy, accessed January 30, 2026, https://www.runcomfy.com/sitemap34fkp9.xml/trainer/ai-toolkit/wan-2-2-t2v-14b-lora-training
  26. How to Train a Z-Image-Turbo LoRA with AI Toolkit : r/StableDiffusion - Reddit, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1p9znlc/how_to_train_a_zimageturbo_lora_with_ai_toolkit/
  27. The perfect combination for outstanding images with Z-image : r/StableDiffusion - Reddit, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1p80j9x/the_perfect_combination_for_outstanding_images/
  28. ClownsharkBatwing/RES4LYF - GitHub, accessed January 30, 2026, https://github.com/ClownsharkBatwing/RES4LYF
  29. Z-Image Base VS Z-Image Turbo : r/StableDiffusion - Reddit, accessed January 30, 2026, https://www.reddit.com/r/StableDiffusion/comments/1qojw11/zimage_base_vs_zimage_turbo/
Edit

Pub: 01 Feb 2026 20:01 UTC

Edit: 01 Feb 2026 21:36 UTC

Views: 557