Datasheet for local AI49 models98 GPUsData read 2026-09-25
No adsNo tracking
Check my GPU →

Can the Radeon 8060S (Strix Halo) 96 GB run FLUX.1 [dev]?

Image model · 12B96 GB LPDDR5X (shared system memory) · 256-bit · 256 GB/s · RDNA 3.5Data 2026-09-25
Runs well
Yes — and comfortably.

Download 16-bit (23.8 GB). With the model's working memory it needs about 26.1 GB, leaving 69.9 GB spare on 96 GB. Quality: the original weights.

Best file16-bit
File size23.8 GB
GPU memory needed~26.1 GB
Shared memory35 / 128 GB
Memory map · Radeon 8060S (Strix Halo) 96 GB26.1 GB / 96 GB
048 GB96 GB
Weights 16-bit · 23.8 GBWorking memory · 1.5 GBReserve · 0.8 GBFree · 69.9 GB
calculated from real file sizes plus working memory. Real-world results people have reported are listed further down. How this works.

01What to download

PartFileFolderSize
Modelflux1-dev.safetensors
16-bit · black-forest-labs/FLUX.1-dev
models/diffusion_models23.8 GBDownload →
Text encodert5xxl_fp8_e4m3fn.safetensors
T5-XXL FP8 · comfyanonymous/flux_text_encoders
models/text_encoders4.9 GBDownload →
Text encoderclip_l.safetensors
CLIP-L · comfyanonymous/flux_text_encoders
models/text_encoders0.2 GBDownload →
VAEae.safetensors
FLUX.1 VAE (ae) · Comfy-Org/Lumina_Image_2.0_Repackaged
models/vae0.3 GBDownload →
Total download · keep about the same free on disk29.3 GB

Alternatives: T5-XXL FP16 (9.8 GB). The 16-bit text encoder is a little more faithful; the smaller one is chosen here because it loads faster and needs less RAM. Sizes read from Hugging Face (2026-09-25). “Download” links start the file directly; the file name links are the same files the official ComfyUI workflows use.

Shared memory: about 35.3 GB of your 128 GB. On this machine the model, the text encoder, the VAE and the operating system all use the same memory. That leaves room, so nothing has to be swapped to disk. calculated

02Every FLUX.1 dev file on 96 GB

FileSizeNeededOn this cardQualityDownload
16-bit ←
SAFETENSORS · black-forest-labs
23.8 GB26.1 GBfits · 69.9 GB sparethe original weightsHugging Face →
Q8_0
GGUF · city96
12.7 GB15.0 GBfits · 81.0 GB sparepractically identical to the originalHugging Face →
FP8
SAFETENSORS · Kijai
11.9 GB14.2 GBfits · 81.8 GB sparepractically identical to the originalHugging Face →
Q6_K
GGUF · city96
9.9 GB12.2 GBfits · 83.8 GB sparevery close to the originalHugging Face →
Q5_K_S
GGUF · city96
8.3 GB10.6 GBfits · 85.4 GB spareclose; small differences in fine detailHugging Face →
Q4_K_S
GGUF · city96
6.8 GB9.1 GBfits · 86.9 GB sparegood; some loss in fine detail and textHugging Face →
Q3_K_S
GGUF · city96
5.2 GB7.5 GBfits · 88.5 GB sparenoticeable loss of detailHugging Face →
Q2_K
GGUF · city96
4.0 GB6.3 GBfits · 89.7 GB spareheavy loss; a last resortHugging Face →

Sizes from the Hugging Face file listing, read 2026-09-25. “Needed” = file + 1.5 GB working memory for this model + 0.8 GB kept free for the system.

03The text encoder

T5-XXL: 9.8 GB as 16-bit, 4.9 GB as FP8, 2.9 GB as GGUF Q4_K_M (plus CLIP-L (0.25 GB)). ComfyUI encodes the prompt first and can push the encoder out of VRAM before sampling, so it does not have to fit together with the model. On 96 GB the FP8 encoder fits on its own, so prompt encoding stays fast.

04About this GPU

This is an integrated GPU that uses system memory. AMD states that up to 96 GB of the 128 GB can be set aside as graphics memory on Windows, which is why it can hold models no consumer graphics card can. The catch is speed: the GPU itself (40 compute units) is far smaller than a big desktop card, and its memory bandwidth is a fraction of one, so each step takes much longer. Treat the verdicts here as 'it fits', not 'it is fast'.

Radeon 8060S (Strix Halo) 96 GB: 96 GB LPDDR5X (shared system memory) · 256-bit · 256 GB/s · RDNA 3.5. Everything that runs on the Radeon 8060S (Strix Halo) 96 GB →

05What more VRAM would change

Nothing to gain for this model: the Radeon 8060S (Strix Halo) 96 GB already runs a top-quality file entirely in VRAM. More memory would only help with bigger images, longer clips or several models at once.

06Measured and reported results

LabelSetupResultPeak VRAMDateSource
reportedflux1-dev full precision (23.8 GB) + t5xxl_fp16 · 1024x1024 · 20 steps
“Steady state | 3.64 s/it | 77.56 s”
AMD ROCm blog, Ryzen AI Max+ 395 / Radeon 8060S, 128 GB unified, Windows ComfyUI; first run 103.89 s; vendor-published measurement
77.56 s / image · 3.64 s/it—2026-07-14rocm.blogs.amd.com →

Reported results are other people's numbers, copied as published, with a link. Settings, drivers and ComfyUI versions differ, so compare them with care. Send yours.

07Questions

How much VRAM does FLUX.1 dev need?

Around 6.3 GB with the smallest file (Q2_K) and 14.2 GB with an 8-bit file (FP8), counting working memory and a small system reserve. The full 16-bit file needs about 26.1 GB.

Which FLUX.1 dev file should I download for the Radeon 8060S (Strix Halo) 96 GB?

16-bit (23.8 GB) from black-forest-labs/FLUX.1-dev.

Is FP8 faster than GGUF on the Radeon 8060S (Strix Halo) 96 GB?

No. This GPU has no FP8 compute, so ComfyUI converts FP8 weights back before the maths. FP8 only saves memory here; Q8_0 GGUF is the closer-to-original 8-bit pick.

How much do I need to download for FLUX.1 dev on the Radeon 8060S (Strix Halo) 96 GB?

About 29.3 GB for the model file, text encoder and VAE listed on this page, and the same again free on disk. With a 96 GB card, 48 GB of system RAM or more is recommended.