Update 29.03.2026. Lustify V8 (Apex) IS OUT! Native 1536px support, new concepts. You can find the full changelog and details about this version <a target="_blank" rel="ugc" href="https://civarchive.com/articles/27900">there</a>. Recomended workflow: <a target="_blank" rel="ugc" href="https://civarchive.com/models/2503119">https://civarchive.com/models/2503119</a><h3 id="if-you-want-to-support-me-or-get-access-to-exclusive-stuff-consider-subscribing-to-my-boosty.-alternatively-you-can-send-bitcoin-(btc)-donation-to-1comzvrxtrxbz7bczdvxifsjhqhaf1yuzs.-every-donation-goes-to-developing-models-(z-image-in-plans)-and-loras.">If you want to support me or get access to exclusive stuff, consider subscribing to <a target="_blank" rel="ugc" href="https://boosty.to/coyotte">my Boosty</a>. Alternatively you can send Bitcoin (BTC) donation to 1CoMZvrXtRXbz7BCzdvxifSjHqhaf1yUZs. Every donation goes to developing models (Z-Image in plans) and loras.</h3> LUSTIFY! A photoreal checkpoint, which intended use is creating pictures of women in sexual scenarios. It understands both danbooru tags and natural language prompting, because it was trained like that. If you manage to fight the nsfw bias, it can also create gorgeous SFW pics of objects/animals/fantasy creatures/you name it. A couple of things I need to make clear before you download the checkpoint:1) This model ISN'T PONY-BASED OR ILLUSTRIOUS-BASED. Don't use loras for these and expect them to work. 2) Sometimes you can get bad hands and bad faces at distant shots. These are hard to fix with finetuning, but really easy with inpainting/adetailer. So, please, don't bother me with the complaints about this. Either adapt to the needs of this checkpoint, or use something else (spoiler, 99% of checkpoints suffer from that because of the limitations of this tech). 3) Everything I do is experimental, and I do a lot of dumb-crazy stuff that in theory shouldn't work. So it's to be expected that something, what used to work with other checkpoint for you, might not work with this one. Let me know if there are such things, and I'd see if I can do anything about it. Recomended parameters: Sampler: DPM++ 2M SDE/DPM++ 3M SDE, Scheduler: Exponential/Karras Steps: 30 Cfg: 2.5-4.5. Highres.fix: upscale by 1.4-1.5, denoising ~0.4 For the distant shots of people you probably wanna use highres.fix and/or adetailer.Also, use reasonable positive/negative prompts, shizoprompting does more harm than good (with any SDXL model). Some tags that have a big visual impact with this model:<ol><li>Camera type tags: "shot on Polaroid SX-70", "shot on Kodak Funsaver", "shot on GoPro Hero", "shot on Canon EOS 5D", "shot on Leica T".</li><li>Photography styles: "analog photo", "glamour photography", "street fashion photography", "candid photo", "amateur photo".</li><li>Lighting types: "cinematic lighting", "neon lighting", "soft lighting", "dramatic lighting", "low key lighting", "bright flash photography", "warm golden hour lighting", "radiant god rays".</li><li>Film types: "Ilford HP5 Plus", "Lomochrome color film", "Fujicolor Pro".</li><li>Photographers: Alessio Albi, Martin Schoeller, Miles Aldridge, Oleg Oprisco, Tim Walker.</li><li>Others: "film grain", "bokeh", "dreamy haze", "technicolor", "underexposed", "low quality", "lowres"</li></ol>Alternatively, you can give a read to <a target="_blank" rel="ugc" href="https://civarchive.com/models/118213/creating-photorealistic-images-with-ai-using-stable-diffusion">this </a>wonderful prompting guide by <a target="_blank" rel="ugc" href="https://civarchive.com/user/PromptGeek">PromptGeek</a>. It has A LOT of useful tips I didn't know about even after years of using SD.

LUSTIFY! [SDXL NSFW checkpoint]

Lightning version. Recomended parameters:<ol><li>DPM++ SDE</li><li>Karras / Exponential scheduler</li><li>4 Steps</li><li>Cfg: 1-2.</li><li>Highres.fix: upscale by 1.4, 2 steps, denoising ~0.4, upscale model "nmkd siax" or "nmkd superscale"</li></ol>Due the nature of "lightning" models, this version might follow your prompts worse then the regular one. Also, I've noticed that the lighting type tags need more weight in this version, for example "(neon lighting:1.3), (cinematic lighting:1.1)".

Files with SHA256: cf99bdb39dd00840c3d8df7944eb4e56c29bc6e90315138241fed23e08a8267a