Comfy-Org's FLUX.1-dev Single-File Package Hits 1 Million Downloads

Comfy-Org bundles FLUX.1-dev and its control variants into single-file safetensors with built-in text encoders, cutting setup friction for ComfyUI users under 24GB VRAM.

·
·
·
Comfy-Org's FLUX.1-dev Single-File Package Hits 1 Million DownloadsPRO
  • Comfy-Org/Flux-1-Dev repackages FLUX.1-dev into single-file safetensors for ComfyUI, with text encoders bundled in.
  • FP8 checkpoint is 17.2GB and runs on 8GB+ VRAM; full version is 23.8GB.
  • Repo also includes repackaged Canny, Depth (NVFP4), Fill, and Redux control variants.
  • Load with the standard Load Checkpoint node, no DualCLIPLoader wiring needed.
  • Ready-made workflow templates cover inpaint, outpaint, Canny, depth LoRA, and reference generation.
  • Over 1M downloads; non-commercial Flux.1-dev license still applies to all files.

Comfy-Org’s single-file packaging of Black Forest Labs’ FLUX.1-dev has passed one million downloads on Hugging Face. The repository turns a four-component ComfyUI setup into two drop-in checkpoint options, allowing developers to load the model, VAE, and text encoders through one standard node. Fewer artifacts make workflows easier to share and reduce failures caused by missing files, incorrect paths, or mismatched precision settings.

Black Forest Labs released FLUX.1-dev as a 12-billion-parameter, guidance-distilled image model. ComfyUI’s split-file workflow treats its diffusion transformer, VAE, CLIP-L encoder, and T5-XXL encoder as separate assets. The ComfyUI team maintains the repository, repackaging the source weights for ComfyUI’s loader conventions without retraining the model or adding network layers.

Four loaders become one

Each file in checkpoints/ bundles the diffusion model, VAE, CLIP-L, and T5-XXL components. ComfyUI’s Load Checkpoint node exposes the model, text-encoder, and VAE outputs required by the rest of the graph. This replaces the separate Load Diffusion Model, DualCLIPLoader, and Load VAE nodes used by the modular workflow.

Checkpoint Size Best fit Main caveat
flux1-dev.safetensors 23.8 GB Systems with more memory and storage headroom Larger downloads and higher resource use
flux1-dev-fp8.safetensors 17.2 GB Consumer GPUs and lower-memory systems Quantization can introduce small output differences

File size does not translate directly into a fixed VRAM requirement. ComfyUI can offload model components to system memory, so some 8 GB GPUs can run the FP8 checkpoint with low-VRAM settings. Resolution, batch size, attention implementation, active nodes, and available system RAM all affect whether a workflow completes and how quickly it runs. Heavy offloading can make generation substantially slower.

Pro article

This story is for Pro members

You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.

Trending
  • No trending articles

Comments

avatar

Next Reads