Inference Tooling and Deployment
Applied diffusion work is dominated by a small number of inference frontends. The distinction that matters is between fixed-pipeline interfaces, which expose a parameter form over a predetermined graph, and node-based systems, which expose the computation graph itself.
ComfyUI
A node-based frontend that exposes the diffusion pipeline as an explicit directed graph — model loading, conditioning, sampling, latent operations and decoding are all separate, rewireable nodes. This makes non-standard pipelines (multi-pass sampling, region-specific conditioning, mixed models, video workflows) expressible without code, and it is why new research techniques almost always ship as ComfyUI nodes first. Now the de facto standard for serious work, at the cost of a steep initial learning curve.
Automatic1111 WebUI
The original mass-adoption interface, and still the most direct route from checkpoint to image. A fixed pipeline with an extensive parameter surface and a large extension ecosystem. Development has slowed considerably in favour of the Forge fork, but its API and directory conventions remain a de facto standard that other tools follow.
Forge / Forge Neo
A fork of the Automatic1111 WebUI with a substantially rewritten backend — better memory management, faster sampling, and support for newer architectures including FLUX. Generally the recommended choice over upstream A1111 for anyone who prefers a fixed-pipeline interface.
InvokeAI
A production-oriented frontend with a unified canvas that treats generation, inpainting and outpainting as operations on a single workspace rather than separate modes. Also ships a node editor. The most coherent option for iterative compositing workflows.
Diffusers (Hugging Face)
The reference Python library rather than an interface — modular pipelines, schedulers and model classes covering essentially every published diffusion architecture. The right layer for programmatic work, custom research, and anything that needs to run as a service rather than as an application.
SD.Next
A heavily refactored fork emphasising broad backend support — CUDA, ROCm, Intel XPU, Apple MPS, DirectML — and rapid adoption of new model architectures. The pragmatic choice on non-NVIDIA hardware.
Fooocus
A deliberately minimal interface that hides nearly every parameter behind curated defaults and automatic prompt expansion. Useful as a baseline for what a well-tuned default pipeline produces, and as a low-friction deployment for non-technical users.
DiffusionBee
A self-contained macOS application built on Apple Silicon's unified memory architecture, requiring no Python environment. The simplest possible local deployment on a Mac.
Deployment constraints. VRAM, not compute, is the binding limit for local inference. Roughly: SD 1.5 runs comfortably in 4GB, SDXL wants 8–12GB, and FLUX-class transformer models need 16–24GB at full precision — or considerably less with 8- and 4-bit quantisation, attention slicing, sequential CPU offloading, and VAE tiling for high-resolution decoding. Where local hardware is insufficient, managed platforms (Replicate, RunDiffusion, fal, Hugging Face Inference Endpoints) offer the same models per-second, and several provide one-click ComfyUI or A1111 instances.