If you want to run a local AI image model, the practical decision comes down to three things: what your GPU can hold, what license you can live with, and whether you need text-to-image only or image editing too. This comparison covers FLUX.1-dev, HunyuanImage 3.0, and Qwen-Image-Edit-2511 using the official model cards and repository documentation. For the shorter route into ComfyUI, 8GB, and Mac, use the local AI image generator guide.
VRAM, speed, and commercial use
The table keeps a cell only when the cited source states it. There is no images-per-second column because none of these three sources publishes one on the pages used here.
| Model | VRAM | Speed notes | Commercial use |
|---|---|---|---|
| FLUX.1-dev | 12B parameters in BF16. The model card does not state a minimum. Its Diffusers example calls enable_model_cpu_offload(). |
The card says guidance distillation makes the model more efficient. The Diffusers example uses 50 steps. No latency figure is published. | FLUX.1 [dev] Non-Commercial License. The card says generated outputs can be used for personal, scientific, and commercial purposes as described in that license. |
| HunyuanImage 3.0 | The hardware guide, citing Tencent's model table, lists at least 3 × 80GB for the base checkpoint and at least 8 × 80GB for Instruct and Distil. Distillation does not lower that VRAM recommendation. | Distil is the faster-inference variant, with 8-step sampling recommended on this site's VRAM guide. The repository describes FlashInfer as enabling up to 3× faster inference. No images-per-second figure is published here. | Tencent Hunyuan Community License. Review the current terms before commercial deployment. |
| Qwen-Image-Edit-2511 | 20B parameters in BF16. The model card does not publish one universal minimum. | The model-card example uses 40 steps. No latency figure is published. | Apache 2.0 on the Qwen-Image-Edit-2511 model card. |
An 8GB figure elsewhere on this site is the hardware guide's floor for SDXL-class generation, not a minimum for the three models above.
What each model actually is
FLUX.1-dev
FLUX.1-dev is a 12 billion parameter rectified flow transformer from Black Forest Labs. The model card describes it as capable of generating images from text descriptions, with output quality second only to FLUX.1 [pro] and competitive prompt following. It is released under the FLUX.1 [dev] Non-Commercial License, and the Hugging Face repository is gated: you must accept the license terms before downloading files. The card also lists ComfyUI and Diffusers as supported local routes. The same Black Forest Labs model tree lists additional editing- and control-focused FLUX.1 variants, including FLUX.1-Fill-dev, FLUX.1-Redux-dev, FLUX.1-canny-dev, and FLUX.1-Depth-dev, which are sibling models in the FLUX.1 family rather than capabilities baked into FLUX.1-dev itself. See the FLUX.1-dev model card for the full license and usage details.
HunyuanImage 3.0
HunyuanImage 3.0 is Tencent's native multimodal image generation model. The GitHub repository describes it as a Mixture-of-Experts model with 13 billion activated parameters per token, while the Nano Banana quickstart page lists it as an 80 billion parameter open-weight MoE. The two figures come from different sources and describe different things: the 80B is the model's total parameter count as listed on the quickstart page, and the 13B-activated figure is the per-token active parameter count from the GitHub repository. HunyuanImage 3.0 supports text-to-image, image-to-image editing, multi-image fusion with up to three reference images, and prompt self-rewrite. The repository provides three variants: HunyuanImage-3.0 for text-to-image, HunyuanImage-3.0-Instruct for editing and reasoning, and HunyuanImage-3.0-Instruct-Distil for faster inference. It is licensed under the Tencent Hunyuan Community License. See the HunyuanImage 3.0 repository for installation and usage.
Qwen Image
Qwen Image on the quickstart page is a hosted dense-layout route for long prompts and information-rich images, with a 4.5K-token context. That page does not state a parameter count or VRAM figure for the hosted product. The open checkpoint in the table above is Qwen-Image-Edit-2511, which its model card lists at 20B parameters in BF16 and which has an official Diffusers pipeline. For the hosted route and the other local variants, use the quickstart guide.
AI image model VRAM requirements
VRAM is the first filter. The supplied sources give concrete numbers for some models and leave others unspecified.
- FLUX.1-dev: The model card's Diffusers example uses
torch.bfloat16and callspipe.enable_model_cpu_offload()with the comment "save some VRAM by offloading the model to CPU. Remove this if you have enough GPU power." The card does not state a minimum VRAM figure. The model is 12B parameters in BF16, so you can estimate the weight footprint, but the official minimum is not published in the source. - HunyuanImage 3.0: The quickstart page lists it as an 80B open-weight MoE. The hardware guide, citing Tencent's model table, recommends at least 3 × 80GB for the base checkpoint and at least 8 × 80GB for Instruct and Distil. The repository also recommends CUDA 12.8, PyTorch 2.8.0, and FlashInfer 0.5.0 for up to 3× faster inference.
- Qwen-Image-Edit-2511: The model card lists 20B parameters in BF16 and an official Diffusers pipeline. It does not state one universal VRAM figure. The hosted Qwen Image product described on the quickstart page is a separate route, and this page does not copy a VRAM number for it.
For a broader framework on estimating VRAM from parameter count, quantization, and offloading, see the hardware requirements guide. FLUX.1-dev is documented at 12B parameters without an official minimum, HunyuanImage 3.0 is documented at 80B total with 13B activated per token and a multi-GPU recommendation, and Qwen-Image-Edit-2511 is documented at 20B BF16 without one universal minimum. Those facts do not support a single light-to-heavy ranking that invents the missing minima.
Installation: concrete steps
FLUX.1-dev with Diffusers
The model card provides a reference Diffusers example. Install or upgrade Diffusers first:
pip install -U diffusers
Then run the pipeline. The card's example uses FluxPipeline and enable_model_cpu_offload():
import torch
from diffusers import FluxPipeline
pipe = FluxPipeline.from_pretrained(
"black-forest-labs/FLUX.1-dev",
torch_dtype=torch.bfloat16
)
pipe.enable_model_cpu_offload() # save some VRAM by offloading the model to CPU
prompt = "A cat holding a sign that says hello world"
image = pipe(
prompt,
height=1024,
width=1024,
guidance_scale=3.5,
num_inference_steps=50,
max_sequence_length=512,
generator=torch.Generator("cpu").manual_seed(0)
).images[0]
image.save("flux-dev.png")
Note that the repository is gated, so you must accept the license on Hugging Face before the download will work. The card also lists ComfyUI as a local inference option.
HunyuanImage 3.0 local installation
The repository gives a step-by-step local install. The environment requires Python 3.12+ and CUDA 12.8. Install PyTorch first:
pip install torch==2.8.0 torchvision==0.23.0 torchaudio==2.8.0 --index-url https://download.pytorch.org/whl/cu128
Then install the remaining dependencies:
pip install -r requirements.txt
For up to 3x faster inference, the repository recommends FlashInfer 0.5.0:
pip install flashinfer-python==0.5.0
Clone the repository and download weights:
git clone https://github.com/Tencent-Hunyuan/HunyuanImage-3.0.git
cd HunyuanImage-3.0/
hf download tencent/HunyuanImage-3.0-Instruct --local-dir ./HunyuanImage-3-Instruct
Run the demo:
export MODEL_PATH="./HunyuanImage-3-Instruct"
bash run_demo_instruct.sh
The repository warns that when FlashInfer is enabled, the first inference may take about 10 minutes due to kernel compilation, and subsequent runs on the same machine will be much faster. It also notes that the CUDA version used by PyTorch must match the system CUDA version, and GCC 9 or higher is recommended.
Qwen Image local installation
The Qwen-Image-Edit-2511 model card documents an official Diffusers pipeline, QwenImageEditPlusPipeline, and tells you to install Diffusers from source. The worked example is on the Qwen local editing guide and the model card. This page does not invent a second install script.
Which one should you choose?
Use this decision list:
- You have a mid-range GPU and want text-to-image only. Start with FLUX.1-dev. It is 12B parameters, has a documented Diffusers example with CPU offloading, and the model card describes cutting-edge output quality. Check the non-commercial license first.
- You need image editing, multi-image fusion, or reasoning over prompts. Editing capability is not exclusive to one model in this comparison. The supplied sources document editing for HunyuanImage 3.0 (the Instruct variant), for the FLUX.1 family (FLUX.1-Fill-dev, FLUX.1-Redux-dev, FLUX.1-canny-dev, and FLUX.1-Depth-dev appear in the same model tree as FLUX.1-dev), and for Qwen-Image-Edit-2511, which the quickstart page lists as an open local image editing model with an official Diffusers pipeline. HunyuanImage 3.0 is also the heaviest documented here, so confirm your VRAM before committing.
- You need long prompts and information-rich layouts. The quickstart page positions Qwen Image as the dense-layout route with a 4.5K-token context. For local use, look at Qwen-Image-Edit-2511 and its official Diffusers pipeline.
- You do not own a GPU. None of these are cloud APIs. If you want to run a hosted model, use a cloud route instead. The quickstart page separates hosted APIs from open local models, and the quickstart guide covers both.
Licensing and practical constraints
FLUX.1-dev uses the FLUX.1 [dev] Non-Commercial License. The model card states that generated outputs can be used for personal, scientific, and commercial purposes as described in that license, so read the license before commercial deployment. HunyuanImage 3.0 uses the Tencent Hunyuan Community License; the quickstart page advises reviewing the repository's current license terms and restrictions before commercial deployment. Qwen-Image-Edit-2511 is Apache 2.0 on its model card. That license statement is about the Edit-2511 checkpoint, not a claim about every hosted Qwen product.
One more boundary: the supplied sources do not provide benchmark scores or Elo rankings for these three models. If you want to compare them on measured quality, the Nano Banana benchmarks page is the place to look, but treat any single score as one snapshot rather than a permanent verdict.
Bottom line
FLUX.1-dev is the most documented local starting point for text-to-image, with a 12B parameter model and a Diffusers example that includes CPU offloading; editing-focused siblings exist in the same FLUX.1 family but are separate checkpoints. HunyuanImage 3.0 is documented as an 80B total-parameter MoE with 13B activated per token and as a heavy VRAM route, with editing and multi-image fusion covered by its Instruct variant. Qwen-Image-Edit-2511 is the open editing checkpoint in this comparison: 20B BF16, Apache 2.0, an official Diffusers pipeline, and no single published VRAM minimum. Editing is documented for more than one of these models. Pick based on your GPU, your license needs, and whether you need editing. Then follow the official install steps rather than improvising.