back to local model checker

FLUX.2 Dev

ImagePopular

Black Forest Labs · 32B · Dense

Flagship open-weight FLUX.2 — text-to-image and multi-reference editing up to 4MP

FLUX Non-Commercial
Downloads

0

Likes

0

Released

2025-11

Context

32K tokens

Use cases

image

Your hardware

16 GB Reference Desktop

Quant
Q4_K_M
Memory
16.9 GB
Speed
~8 tok/s
Fit
Too heavy

Quantization options

What is quantization?
QuantBitsVRAMDiskQualityStatus
Q2_K210.7 GB9.8 GBlowTight fit · ~19 t/s
Q3_K_M314.8 GB13.7 GBmoderateBarely runs · ~14 t/s
Q4_K_M416.9 GB15.6 GBgoodToo heavy · ~8 t/s
Q5_K_M521 GB19.6 GBgoodBarely runs · ~4 t/s
Q6_K625.1 GB23.5 GBexcellentBarely runs · ~3 t/s
Q8_0833.3 GB31.3 GBexcellentBarely runs · ~1 t/s
F161666.1 GB62.6 GBlosslessToo heavy · ~1 t/s

About this model

FLUX.2 Dev (FLUX.2 dev) is a 32B image generation architecture released by Black Forest Labs. Unlike autoregressive text LLMs whose KV cache grows with chat turns, local image and video diffusion pipelines allocate memory simultaneously for the transformer backbone, companion text encoders (such as T5/CLIP), and high-resolution VAE latent decoding buffers.

Baseline sizing plans for 17.9 GB minimum memory and 29.8 GB recommended memory, with the Q4_K_M checkpoint requiring roughly 16.9 GB of VRAM and 15.6 GB of SSD storage. Exceeding dedicated VRAM forces PCIe weight swapping across host RAM and slows step sampling dramatically.

Desktop NVIDIA RTX workstations using ComfyUI or Diffusers with CUDA acceleration deliver the cleanest generation throughput, while high-memory Apple Silicon Macs can execute workloads via MPS with conservative batch size 1 and lower output dimensions. Under the FLUX Non-Commercial license, verify commercial deployment terms on the official repository card before production use.

Highlights

  • Generation VRAM Budget17.9 GB minimum and 29.8 GB recommended across backbone, encoder, and VAE buffers.
  • Baseline QuantizationQ4_K_M targets 16.9 GB memory and 15.6 GB storage.
  • Recommended PipelineComfyUI or Diffusers on NVIDIA CUDA desktop GPUs or high-RAM Apple Silicon Macs.

System requirements by device

Memory planning targets 17.9 GB minimum RAM/VRAM and 29.8 GB recommended memory. The baseline quant is Q4_K_M, estimated at 16.9 GB memory and 15.6 GB disk. Actual runtime usage shifts with context length, KV cache precision, and OS background overhead.

DeviceNotes
Mac (Apple silicon)Use unified memory headroom (~75% physical RAM max) as the primary fit signal. Start with Q4_K_M and close heavy browser tabs first.
Windows / Linux GPUPrefer dedicated NVIDIA RTX VRAM via CUDA (ComfyUI / Diffusers) so UNet, text encoder, and VAE buffers stay off PCIe RAM.
Phones & Compact Edge BoardsNot supported locally: mobile RAM ceilings and app watchdogs cannot hold multi-stage diffusion and VAE buffers.

Start with a short session and leave memory for the operating system. A file fitting on disk does not guarantee that it will load in memory.

Estimated memory by quantization

These are rough estimates, not tested minimum requirements. Check the actual file and runtime documentation; context, offloading and operating-system overhead can change the memory needed.

Quant TierEstimated memoryDisk SizeQuality
Q2_K10.7 GB9.8 GBlow
Q3_K_M14.8 GB13.7 GBmoderate
Q4_K_M16.9 GB15.6 GBgood
Q5_K_M21.0 GB19.6 GBgood
Q6_K25.1 GB23.5 GBexcellent
Q8_033.3 GB31.3 GBexcellent
F1666.1 GB62.6 GBlossless

How to run FLUX.2 Dev on your device

Start with a short prompt and the smallest quant that still gives the quality you need. A clean first run is more useful than loading a larger file with no memory headroom.

Windows

Run FLUX.2 Dev on Windows / Linux GPU

  1. Install ComfyUI or a current Diffusers Python environment with PyTorch CUDA enabled.
  2. Select a quantized checkpoint such as Q4_K_M (16.9 GB) and confirm at least 17.9 GB of free VRAM.
  3. Keep VAE tiling enabled and test a standard resolution (e.g., 1024x1024 or short frame count) before increasing batch or step counts.
  4. Avoid spilling diffusion UNet/DiT weights across PCIe into system RAM if interactive generation speed matters.
Device how-to guide
Mac

Run FLUX.2 Dev on Apple Silicon Mac

  1. Confirm your Mac has at least 29.8 GB unified memory so Metal buffers do not force macOS swap.
  2. Load Q4_K_M weights inside ComfyUI (MPS) or a native Apple Silicon Diffusers workflow.
  3. Close memory-heavy browsers and keep latent batch size at 1 during initial generation tests.
  4. Consult the Mac hardware guide when planning multi-step image or video pipelines.
Device how-to guide

FLUX.2 Dev vs alternatives

ModelParamsContextMin RAMLicense
FLUX.2 Dev32B32K17.9 GBFLUX Non-Commercial
FLUX.2 Klein 9B9B32K5 GBFLUX Non-Commercial
FLUX.2 Klein 4B4B32K2.2 GBApache 2.0
Qwen 2.5 32B32B128K17.9 GBApache 2.0
Qwen 2.5 Coder 32B32B128K17.9 GBApache 2.0
Qwen 3 32B32B128K17.9 GBApache 2.0

Use this table to choose the smallest nearby model that still matches the job. A related model with lower RAM can be the better local choice when the current page fits only at the edge of available memory.

Frequently asked questions

What is FLUX.2 Dev?
FLUX.2 Dev is a 32B media generation model from Black Forest Labs. Sizing estimates allocate 17.9 GB minimum VRAM and 29.8 GB recommended memory for weights, text encoders, and VAE decode buffers.
How do I download and install FLUX.2 dev?
Download a GGUF build for FLUX.2 Dev, start with Q4_K_M, and confirm the model fits locally before increasing context or quant quality.
How much VRAM or RAM does FLUX.2 Dev require?
At Q4_K_M, FLUX.2 Dev occupies roughly 16.9 GB of active memory and 15.6 GB on disk. Add 2–6 GB of spare headroom for KV cache buffers, runtime scratch space, and OS apps (29.8 GB recommended).
Which software runs FLUX.2 Dev locally?
Run FLUX.2 Dev inside ComfyUI or Hugging Face Diffusers on an NVIDIA CUDA desktop GPU or high-memory Apple Silicon Mac. Start with Q4_K_M or FP8 builds before testing higher-precision weights.
Can phones run FLUX.2 Dev locally?
No. Desktop image and video diffusion checkpoints require high-bandwidth desktop GPUs or high-memory Apple Silicon Macs rather than smartphone runtimes.
How does FLUX.2 Dev compare to FLUX.2 Klein 9B?
FLUX.2 Klein 9B (9B, 5 GB min RAM) sits closest in size. Compare active parameters, context ceiling (32K vs 32K), and license terms (FLUX Non-Commercial) before switching.