Turbo or Raw.
Krea 2 is Krea’s own 12.8B model, trained from scratch and released on 22 June 2026. It isn’t related to Flux.1 Krea Dev, the older model Krea made with Black Forest Labs. It comes in two versions.
- Turbo is the one to generate with. Eight steps, CFG 1, sizes from 1K to 2K.
- Raw is the undistilled base, meant for training LoRAs and further tuning. It takes 52 steps at CFG 3.5, follows a negative prompt, and was trained up to 1K.
Krea’s own advice is to train on Raw and run on Turbo. Users on the model pages agree that Raw alone makes weak pictures.
Files you need.
One model, one text encoder, one VAE. The encoder is Qwen3-VL 4B, and the VAE is the one from Qwen-Image.
Turbo
-
Model13.1 GB Download
krea2_turbo_fp8_scaled.safetensorsComfyUI/models/diffusion_models/ or krea2_turbo_int8_convrot, 13.5 GB. Full precision: krea2_turbo_bf16, 26.3 GB -
Text encoder5.2 GB Download
qwen3vl_4b_fp8_scaled.safetensorsComfyUI/models/text_encoders/ full precision: qwen3vl_4b_bf16.safetensors, 8.9 GB -
VAE0.3 GB Download
qwen_image_vae.safetensorsComfyUI/models/vae/
Raw
-
Model26.3 GB Download
krea2_raw_bf16.safetensorsComfyUI/models/diffusion_models/ smaller: krea2_raw_fp8_scaled 13.1 GB, krea2_raw_int8_convrot 13.5 GB. Same encoder and VAE -
LoRA0.5 GB Download
krea2_turbo_lora_rank_64_bf16.safetensorsComfyUI/models/loras/ optional: makes Raw behave like Turbo
Which 13 GB file: in a 96-image test against bf16 on an RTX 4090, int8 convrot came closest, ahead of mxfp8 and fp8. int8 needs PyTorch built for CUDA 13.0 (cu130) to run fast, and it helped on AMD too. On an RTX 50-series card there is also krea2_turbo_nvfp4 at 7.7 GB, about 15% faster than fp8 on a 5090. Comfy-Org also hosts nine style LoRAs; three from the launch were pulled at Krea’s request.
models/
├── diffusion_models/
│ └── krea2_turbo_fp8_scaled.safetensors
├── text_encoders/
│ └── qwen3vl_4b_fp8_scaled.safetensors
└── vae/
└── qwen_image_vae.safetensors
GGUF: not yet
realrebelai’s Krea 2 GGUFs run from 7.2 GB (Turbo Q4_K_M) to 13.6 GB (Q8_0). The main branch of ComfyUI-GGUF rejects their krea2 architecture (issue #464), so they need a fork for now. A Qwen3-VL 4B GGUF encoder loads, but without its vision part.
What fits your computer.
Turbo at about 1 megapixel. The text encoder runs first and ComfyUI moves it out of the way before sampling, so the model file sets the limit. A model that doesn’t fit still runs with part of it in system RAM, only slower.
- 6 GBNo
Not a realistic fit. Z-Image Turbo or Flux.2 Klein 4B are.
- 8 GBOffloads
Turbo fp8 with ComfyUI’s dynamic VRAM and at least 24 GB of system RAM. An RTX 3060 Ti takes about 30 s per image.
- 12 GBTight
Turbo fp8: an RTX 3060 12 GB made 1280 × 720 in 37 s at 8 steps, peaking near 11.8 GB.
- 16 GBFits
Turbo fp8 or int8 comfortably. The size most users settle on.
- 24 GBFits
Turbo up to 2K, or Raw in fp8 or int8. An RTX 3090 makes a 1024 image in about 13 s.
- 32 GBFits
Turbo or Raw at full precision (26.3 GB).
- Mac 32 GBNo
The bf16 Turbo needs about 31 GB resident, and the smaller files don’t work on a Mac yet.
- Mac 64 GB+Fits
Turbo in bf16: an M1 Max with 64 GB took about 212 s per 1024 image at 8 steps.
Set it up.
-
Update ComfyUI
Krea 2 support arrived in ComfyUI at launch, in June 2026. Anything older doesn’t know the
krea2encoder type. ComfyUI Desktop updates itself; the portable build has an update script. In a manual install:Terminal, in the ComfyUI foldergit pull pip install -r requirements.txt
-
Download the three files
Model, text encoder and VAE from the lists above. Comfy-Org’s repo needs no sign-in.
-
Put them in their folders
Model in
diffusion_models, encoder intext_encoders, VAE invae. Restart ComfyUI so the loaders list them. -
Open the Krea 2 template
In the template browser, pick Krea-2: Text to Image, or Krea-2 Int8: Text to Image for the int8 file. It comes with a style LoRA and an LLM prompt enhancer switched on; bypass either if you don’t want them. If it says it could not load subgraphs, update ComfyUI’s frontend.
-
Check the loaders
Load Diffusion Model gets the Krea 2 file. Load CLIP gets the Qwen3-VL 4B encoder with type
krea2. Load VAE getsqwen_image_vae. Turbo needs no ModelSampling node: ComfyUI’s default shift for Krea 2, 1.15, is Krea’s own Turbo value. -
Write a long prompt
Krea 2 likes long, detailed, natural sentences. Put text you want in the picture in quotes. Negations like “without flame” tend to fail; describe what you want instead, such as “an unlit torch”.
Settings that work.
Turbo
- Steps
- 8
- CFG
- 1
- Sampler
- euler
- Scheduler
- simple
- Size
- 1024 to 2048
- Shift
- 1.15, default
- Negative
- none
- Text encoder
- Load CLIP, krea2
Krea’s README runs Turbo at 8 steps with CFG off and a fixed shift of 1.15, which is what Comfy’s template does. For 2K, stay near 2 megapixels.
Raw
- Steps
- 52
- CFG
- 3.5
- Sampler
- euler
- Scheduler
- simple
- Size
- up to 1024
- Shift
- from image size
- Negative
- yes
- Latent
- EmptyLatentImage
These are the settings in Krea’s README, and ComfyUI’s Krea 2 docs also say 52 steps. The 28 steps and CFG 4.5 in Krea’s inference.py are generic defaults, not the Raw recipe. Raw’s shift grows with the image size, from 0.5 to 1.15; in ComfyUI, add ModelSamplingFlux with max shift 1.15 and base shift 0.5. For the negative prompt, replace the template’s ConditioningZeroOut with a second text encode.
The Krea2T Enhancer
ComfyUI-Krea2T-Enhancer is an optional community node by capitan01R. It patches Krea 2’s text path to follow the prompt more closely. It goes between the model loader and the sampler, with strength 1.0 by default, from 0 (off) to 2. The author calls it experimental and suggests starting at 1.0 and going lower when you stack LoRAs. The pack also has a node for (phrase:weight) prompt weighting, since normal weighting doesn’t map onto Krea 2.
How fast.
| GPU | File | Size | Time |
|---|---|---|---|
| RTX 4090 | Turbo fp8 | 1024 px | 1.6 it/s[1] |
| RTX 3090 | Turbo fp8, 8 steps | 1024 px | 13 s[2] |
| RTX 3060 12 GB | Turbo fp8, 8 steps | 1280 × 720 | 37 s[3] |
| RTX 3060 12 GB | Turbo fp8, 8 steps | 1920 × 1080 | 88 s[3] |
| RTX 3060 Ti 8 GB | Turbo fp8 | not given | 30 s[4] |
| RX 9060 XT 16 GB | Turbo fp8 | 1 MP | 200 to 300 s[4] |
| M1 Max 64 GB | Turbo bf16, 8 steps | 1024 px | 212 s[5] |
Times after the first run, which loads the models. The 4090 reached 1.9 it/s with ComfyUI’s --fast flag. On AMD, try the int8 file.
When it goes wrong.
- Out of memory on 8 to 12 GB
- Use the fp8 or int8 file, keep dynamic VRAM on, and have 24 to 32 GB of system RAM.
- The template says it could not load subgraphs
- The frontend is older than the template. Update ComfyUI’s frontend, or build the plain graph: loaders, text encode, empty latent, KSampler, VAE decode.
- Raw makes mush at any CFG
- Use 52 steps at CFG 3.5, keep it at 1024 or below, or try the Turbo LoRA at 0.6 as above.
- Black images on a Mac
- Start ComfyUI with
--fp16-vae. If the fp8 file is rejected, use the bf16 one. - ComfyUI-GGUF says the architecture is unknown
- Its main branch doesn’t support
krea2yet. Use the safetensors files. - Template LoRAs missing (warmpastel, plasmoid, coolblue)
- Krea had them removed. Pick one of the other style LoRAs.
- Raw’s shift stays after you bypass
ModelSamplingFlux - A dynamic VRAM bug on low-memory cards. Restart ComfyUI, or start it with
--disable-dynamic-vram.
Raw looks bad at every CFG from 1 to 10, even at 50 steps. Is that expected?
How much VRAM does Turbo really need, and will it run on an 8 GB card?
Raw is a base for training, and the Turbo LoRA trick came out of the first thread. The second found 8 GB workable with dynamic VRAM and 24 GB of system RAM.
Questions.
How much VRAM does Krea 2 need?
16 GB is comfortable for Turbo in fp8 (13.1 GB). 12 GB works with a little offloading, and 8 GB works with ComfyUI’s dynamic VRAM and at least 24 GB of system RAM, at about 30 s per image. The full-precision files need 32 GB.
Should I use Krea 2 Turbo or Raw?
Turbo for making images: 8 steps at CFG 1. Raw is the undistilled base for training LoRAs. Krea’s own advice is to train on Raw and run on Turbo.
Can I use Krea 2 commercially?
Only if your company, with its affiliates, makes less than $1 million a year in revenue. Above that you need an enterprise licence from Krea. You own the images you generate either way.
Is Krea 2 the same as Flux.1 Krea Dev?
No. Flux.1 Krea Dev is a Flux.1 model Krea made with Black Forest Labs in 2025. Krea 2 is Krea’s own model, trained from scratch, with a different encoder and VAE. Their files and LoRAs don’t mix.
Does Krea 2 run on a Mac?
Yes, with the bf16 files and ComfyUI started with --fp16-vae. fp8 files were rejected on Apple GPUs in testing, and Krea 2 GGUFs don’t load yet. An M1 Max with 64 GB took about 212 s per image.
Do Krea 2 GGUFs work in ComfyUI?
Not with the main branch of ComfyUI-GGUF, which rejects the krea2 architecture. Use the fp8 or int8 safetensors files for now.
What does the Krea2T Enhancer do?
It is an optional community node by capitan01R that patches Krea 2’s text path for closer prompt following. It sits between the model loader and the sampler, with strength 1.0 by default. The author calls it experimental.
Sources: Krea 2 repository and README, Krea 2 Turbo model card, Krea 2 licensing, ComfyUI Krea 2 tutorial, Krea 2 speed and quality thread [1], comfylab Krea 2 guide [2], RTX 3060 low-VRAM test [3], Krea 2 Turbo VRAM thread [4], Krea 2 on an M1 Max [5], quantisation comparison, Krea2T Enhancer.