Bonus: Top up now and we'll double your first deposit — get x2 credits instantly.

FLUX.1-schnell: Self-Hosting & Deployment Guide

FLUX.1-schnell is an open-weight text-to-image model.

What is FLUX.1-schnell?

FLUX.1-schnell is an open-weight text-to-image model, published by Black Forest Labs with open weights at black-forest-labs/FLUX.1-schnell. LLM API does not route this model today, so there is no endpoint or code sample for it here. What this page does give you is the self-hosting picture: published weight sizes, the VRAM each quantisation needs and the commands to serve it yourself. Every figure is read from the public repository and refreshed weekly. At import it had 525,415 downloads on Hugging Face in the previous 30 days, under the apache-2.0 licence.

How to run FLUX.1-schnell yourself

Open weights (apache-2.0), 11.9B parameters. Below: how much memory the weights need at each quantization, which hardware fits them, and the commands to serve it.

FLUX.1-schnell VRAM requirements

Precision / quantizationWeightsFigureSource
BF16 (full precision)23.8 GBEstimate11.9B params × 2 bytes
MLX 4-bit7 GBFile sizeargmaxinc/mlx-FLUX.1-schnell-4bit-quantized
GGUF Q8_012.7 GBFile sizecity96/FLUX.1-schnell-gguf
GGUF Q2_K4 GBFile sizecity96/FLUX.1-schnell-gguf

File size = actual download size on Hugging Face. Estimate = parameter count × bytes per weight. Weights only — the KV cache for long contexts needs extra memory; the fit tables below add 15% headroom as a rule of thumb.

GPU requirements: deploy FLUX.1-schnell on your hardware

HardwareBF16 (full precision)MLX 4-bitGGUF Q8_0GGUF Q2_K
NVIDIA H200141 GB1×1×1×1×
NVIDIA H10080 GB1×1×1×1×
NVIDIA A100 80GB80 GB1×1×1×1×
NVIDIA L40S48 GB1×1×1×1×

GPUs needed per variant.

HardwareGGUF Q8_0GGUF Q2_K
RTX 509032 GB1×1×
RTX 409024 GB1×1×
RTX 309024 GB1×1×

GGUF via llama.cpp; more cards or CPU offload for larger files.

HardwareGGUF Q8_0GGUF Q2_KMLX 4-bit
Mac, 512 GBM3 UltraFitsFitsFits
Mac, 192 GBM2 UltraFitsFitsFits
Mac, 128 GBM4 Max / M3 MaxFitsFitsFits
Mac, 64 GBM4 Pro / MaxFitsFitsFits

Assumes ~75% of unified memory is usable by the GPU.

HardwareBF16 (full precision)MLX 4-bitGGUF Q8_0GGUF Q2_K
AWS p5.48xlarge8× H100 · 640 GBFitsFitsFitsFits
AWS p4de.24xlarge8× A100 80GB · 640 GBFitsFitsFitsFits
AWS g6e.12xlarge4× L40S · 192 GBFitsFitsFitsFits
Google Cloud a3-highgpu-8g8× H100 · 640 GBFitsFitsFitsFits
Azure ND H100 v58× H100 · 640 GBFitsFitsFitsFits

Whole-instance GPU memory; public instance specs.

Not on LLM.API yet

We do not route this model through our API at the moment. Browse the models you can call today — most workloads have a close match already live.

Not available on LLM API yet

We do not route this model through our API at the moment, so there is no endpoint or code snippet for it yet. Browse the models you can call today — most workloads have a close match already live.

Browse available models

When to Use — When NOT to Use

Use it if...

  • You need images generated from a text prompt, or edited from a reference image (FLUX.1-schnell)
  • You want image generation on the same LLM API key as your text models, with no extra vendor SDK
  • Your pipeline can take the result as a URL or base64 payload rather than a streamed response
  • You want per-image pricing you can read off the catalogue before you commit

Avoid if...

  • You need a chat, coding or reasoning model — this model returns images, not text
  • You need token-by-token streaming: image calls return once the picture is finished
  • You need video, speech or embeddings; those are separate models in the catalogue
  • Your licensing review has not cleared generated imagery for commercial use

Get one key to every model

Swap your API key. Keep your code.