Z-Image Notes

Current default assumption

Z-Image is in scope for collection and optimization alongside FLUX.2-klein, LTX, and MiniMax.

strong official text-to-image workflows
reference and edit workflows
outpaint / inpaint workflows
high-quality upscaling or restoration-adjacent workflows
any workflow that clearly beats a comparable FLUX path in practical image quality or simplicity

models/zimage/z-image-turbo-official-example/
models/zimage/z-image-turbo-inpainting-community/
models/zimage/z-image-turbo-controlnet-union-community/
models/zimage/qujincheng-z-image-lora-facetailer/ for face-detail follow-up, not as a core generator
optimized/image-edit/zimage-turbo-3070-inpaint-start/ is currently a straight hold of z-image-turbo-inpainting-community, so it should stay a curated import until a real graph-side improvement appears.

Prefer real workflow assets over showcase pages.
Favor workflows with clear node requirements and portable imports.
Treat Z-Image as especially relevant for image-generation and image-edit categories, not video categories.
Keep the official example as the clean text-to-image baseline, then compare the community inpaint and controlnet-union graphs against it for real edit gains.
Treat facetailer-style graphs as post-pass helpers unless they prove they can stand alone.
Do not spend optimization time on the inpaint master unless a new run shows a concrete advantage over the imported community graph.

which Z-Image workflows are genuinely stronger than the best current FLUX image-generation paths
whether Z-Image should become a category-master candidate for text-to-image or image-edit
whether the inpaint or union-style community graph is the better maintained edit baseline on Chris's machine