Z-Image + Detail Daemon High-Quality Enhancement Workflow: GGUF Quantized Model Quality Boost

Quantization Saves VRAM, but What About Detail?

Z-Image's GGUF quantized versions (such as z_image_Q8_0 and z_image_turbo-Q8_0.gguf) let 8GB GPUs run a 6B-parameter diffusion model smoothly — but the trade-off is that weights drop from FP16 to 8-bit precision, and the micro-details in generated images — skin texture, fabric fibers, bokeh edges — show visible softening. The most common complaint from quantized-model users in the community: "It's good enough, but something feels missing."

Detail Daemon was built for exactly this problem. Originally created for Stable Diffusion WebUI (by muerrilla), it was ported to ComfyUI by Jonseed (ComfyUI-Detail-Daemon, 957+ GitHub stars, MIT License) with official support for Flux, SDXL, SD1.5, Qwen, and Z-Image. In January 2026, community user gabrielx published the "Z-Image GGUF with Detail Daemon" workflow (CivitAI, 94 Very Positive reviews) combining z_image_Q8_0 + Qwen3-4B text encoder + Detail Daemon into a complete low-VRAM high-detail pipeline — this article walks you through replicating and understanding it.

How Detail Daemon Works: The Art of Sigma Scheduling

Noise Scheduling and Detail Formation

The diffusion denoising process has two phases:

• Early steps: establish the image's large structure (composition, subject silhouette, lighting)
• Late steps: fill in fine details (skin pores, hair strands, fabric texture)

Traditional samplers inject and remove noise in "equal amounts" at every step. Detail Daemon's core idea: keep the injected noise the same while lowering the amount of noise removed at each step — effectively "sneaking" a bit of noise forward for later steps, giving fine details more opportunity to form late in sampling.

In formula terms: the Detail Daemon Sampler node applies an adjustment curve to the sigma schedule. A positive detail_amount lowers the sigma at affected steps, enhancing detail; negative values reduce detail and simplify the image.

The Cost of Overuse

The node documentation explicitly warns: overuse causes oversharpening and HDR-like effects. Detail enhancement is not "more is better" — you need to find the balance between "crisp" and "natural." That is exactly what the parameter tuning section addresses.

The Four Core Nodes

1. Detail Daemon Sampler (Main Node)

The most commonly used node; it directly replaces the sampler in your workflow (compatible by default with custom samplers like SamplerCustomAdvanced).

Key parameters and recommended values (Z-Image):

Parameter	Function	Z-Image Recommended
detail_amount	Core strength; positive = more detail	0.1 ~ 1.0 (Flux/Z-Image can go higher; SDXL needs <0.25)
start	Adjustment start step (0 = first step)	0.1 ~ 0.5
end	Adjustment end step	0.5 ~ 0.9
bias	Shifts mid-range adjustment forward/back	0 (default)
exponent	Curve curvature (0 = none, 1 = smooth)	0 ~ 1
fade	Reduces the entire adjustment curve	0 (default)
smooth	Smooth curve on/off	true
cfg_scale_override	Override CFG (0 = auto-detect)	0 (auto)

Rule of thumb: start with detail_amount 0.3, paired with start=0.2, end=0.8. If you see oversharpening, lower detail_amount first — don't touch start/end; if detail is still insufficient, increase gradually to 0.6 ~ 0.8.

2. Detail Daemon Graph Sigmas (Visualization Node)

This node does not change actual generation — it only graphs the adjusted sigma curve to preview parameter effects. Share the same parameter inputs as the Sampler node (or use primitive inputs for both), run the queue once, and you'll see the curve shape — the most intuitive tuning aid available.

3. Multiply Sigmas (Multiplication Node)

Multiplies all sigmas by a factor (both injected and denoised noise scale together). A factor below 1 adds detail; recommended 0.95 ~ 0.99.

The difference vs. Detail Daemon Sampler: it's a "global scaling" rather than a "curve adjustment" — simpler to use, but may slightly change composition or introduce grainy noise. Set to 1.0 to disable.

4. Lying Sigma Sampler (Simplified Version)

A simplified node with only dishonesty_factor + start_percent + end_percent:

• dishonesty_factor: recommended -0.1 ~ -0.01 (negative = more detail). Note the scale differs from detail_amount: -0.05 ≈ 0.5 detail_amount ≈ 0.95 Multiply Sigmas factor
• start_percent: 0.1 ~ 0.5
• end_percent: 0.5 ~ 0.9

Great for quick experiments: fewer knobs, more intuitive — find your bearings here, then switch to the full node for fine-tuning.

Building the Complete Workflow (Low-VRAM GGUF Setup)

Prerequisites

1. ComfyUI (latest)
2. GGUF custom node (UnetLoaderGGUF, ComfyUI-GGUF)
3. Detail Daemon node: install via ComfyUI Manager (search "Detail Daemon") or manually from GitHub Jonseed/ComfyUI-Detail-Daemon (includes the official example example_workflows/Z-Image txt2img-DetailDaemon.json)
4. RES4LYF custom node (used by the community workflow for resolution/latent handling)

Model Files (Community Workflow Standard Configuration)

Component	File	Location
Diffusion model	z_image_Q8_0.gguf (or z_image_turbo-Q8_0.gguf)	ComfyUI/models/diffusion_models/
Text encoder	Qwen3-4B-UD-Q8_K_XL (GGUF)	ComfyUI/models/clip/
VAE	flux_ae.safetensors (a.k.a. ae.safetensors; Z-Image reuses the FLUX VAE)	ComfyUI/models/vae/

Node Graph (txt2img)

CLIPTextEncode ──► CLIP ──► Detail Daemon Sampler ──► VAEDecode ──► SaveImage
                     │            ▲
UnetLoaderGGUF ──────┘            │
                          (sigma adjustment curve)

[Optional] Detail Daemon Graph Sigmas ── shares params with Sampler

1. UnetLoaderGGUF loads z_image_Q8_0.gguf
2. CLIP loads the Qwen3-4B GGUF text encoder; encode the prompt
3. Replace the default KSampler with Detail Daemon Sampler (if you must keep KSampler, create a custom sampler preset via the BlehSetSamplerPreset node and select it)
4. Sampler settings: res_2s (one of the best samplers verified by community workflows), steps per Turbo/Base model requirements
5. Decode with flux_ae.safetensors VAE

Starting Parameter Configuration

Parameter	Starting Value	Notes
detail_amount	0.4	Gentle enhancement first; observe
start / end	0.2 / 0.8	Covers mid-range sampling
bias	0	Default
exponent	1.0	Smooth curve
sampler	res_2s	Community-verified combo

Quality Comparison: GGUF + Detail Daemon vs Native BF16

Community results (CivitAI workflow reviews + Reddit r/comfyui discussions):

Setup	VRAM Usage	Quality	Speed
BF16 native (no enhancement)	16GB+	Baseline (full detail)	Baseline
GGUF Q8_0 (no enhancement)	~8GB	Slight detail softening	Similar
GGUF Q8_0 + Detail Daemon	~8GB	Close to native BF16 detail	Nearly zero extra cost

Key takeaway: Detail Daemon adds almost no VRAM or inference time (it only adjusts the sigma schedule — no extra compute modules), yet it significantly recovers the micro-detail lost to 8-bit quantization. For users with 12GB or less VRAM, this is the highest value-for-money quality upgrade available.

Best Configurations for Low-VRAM Scenarios

• 8GB VRAM: z_image_Q8_0 + Qwen3-4B-UD-Q8_K_XL + Detail Daemon (detail_amount 0.4 ~ 0.6)
• 6GB VRAM: consider lower-bit GGUF (e.g., Q6_K) with detail_amount 0.6 ~ 0.8 to compensate
• 12GB VRAM: z_image_turbo-Q8_0.gguf + Detail Daemon for a speed/quality balance

FAQ

Q1: Image looks oversharpened / HDR-like after adding Detail Daemon?
Lower detail_amount (e.g., 0.4 → 0.2), or raise start (e.g., 0.2 → 0.35) to focus the adjustment on later sampling steps.

Q2: Can't use Detail Daemon with KSampler?
Detail Daemon works with custom samplers by default (SamplerCustomAdvanced). For KSampler, create a preset with the BlehSetSamplerPreset node.

Q3: Why doesn't the Graph Sigmas node change my output?
It only graphs the curve for preview; it doesn't affect generation. Make sure it shares the same parameters as the Sampler node.

Q4: Does Detail Daemon work with both Z-Image Base and Turbo?
Yes. Turbo has fewer steps (8), so set start low (0.1~0.2) to intervene early; Base has more steps, so the default 0.2/0.8 works well.

Summary

Z-Image GGUF quantization gave low-VRAM users the ability to run a 6B model, and Detail Daemon — using the near-zero-cost trick of adjusting the sigma schedule — recovers the detail that quantization lost. This "GGUF + Qwen3-4B + Detail Daemon" combo has become the standard low-VRAM high-detail setup in the Z-Image community. Remember three golden rules: start detail_amount at 0.3~0.4, use Graph Sigmas to visualize tuning, and when oversharpening occurs, lower the strength — don't change the range. Your 8GB GPU can deliver near-native-BF16 detail.