Krea 2 Goes Open Source: What the RAW and Turbo Split Means for Image Generation

Krea AI has released Krea 2 as an open-source model, and the shape of the release tells you as much as the model itself. Instead of a single checkpoint, the company shipped two: Krea 2 RAW, an undistilled base model built for fine-tuning, and Krea 2 Turbo, a distilled version that produces finished images in eight inference steps. The weights are on Hugging Face, the official inference code is on GitHub, a long technical report went up the same day, and the launch came bundled with a Reddit AMA and a ComfyUI livestream.

Nobody stages a launch like that for a side project. This is infrastructure Krea expects people to build businesses on. Open-source image generation has been dominated by the Stable Diffusion lineage and FLUX for years, and Krea 2 arrives with a different pitch: it is not trying to be the most obedient model, it is trying to be the one with the best taste.

What “aesthetic-first” actually means in practice

Most image models are optimized for prompt fidelity. You describe a scene, and the model is graded on how literally it reproduces your description. Krea 2 inverts that priority. MindStudio’s breakdown describes K2 as “aesthetically opinionated”: where models like GPT Image 2 or SDXL behave like transcription engines, K2 interprets a prompt through a learned sense of composition and style. Give it a vague prompt and it will still steer toward an image that looks deliberate, rather than one that is technically compliant and visually flat.

There is an obvious trade-off here, and Krea does not pretend otherwise. Users who need pixel-level control over every element of a scene may find the model too willing to make its own decisions. But for creative work, a collaborator with taste is frequently more useful than an executor with none. The technical report frames the design goal as a balance between “wide aesthetic diversity and user creative control” — a model with opinions that still knows when to defer to yours. Seventeen authors are credited on that report, which gives some sense of how much engineering went into holding those two goals in tension.

Two checkpoints, one workflow: train on RAW, run on Turbo

The most practically useful decision in this release is the split between a training model and an inference model. Krea’s own framing is compact enough to be a slogan: TRAIN on Raw, RUN on Turbo.

Krea 2 RAW is the undistilled base checkpoint, with no step distillation and no guidance distillation applied. It runs at a default of 28 steps with a CFG of 4.5 and supports resolutions from 1024 up to 2048. Because nothing has been baked in or stripped out, it remains malleable. The official GitHub repository positions it explicitly for LoRA training, fine-tuning, and post-training research. Krea 2 Turbo is the production side of the pair: an 8-step distilled checkpoint that needs no classifier-free guidance at all (guidance scale is simply set to zero) and is tuned for fast, polished text-to-image output.

What connects the two is the part that matters. LoRAs trained on RAW are designed to express strongly when applied to Turbo. In other words, you develop a style on the flexible base model, then deploy that style on the fast model, without retraining anything. Anyone who has spent time in the open-source image ecosystem will recognize the pain this addresses: training adapters on distilled models tends to produce weak or broken results, while running production inference on undistilled base models is too slow to be economical. Until now, the community mostly picked one problem and lived with it. Krea 2 is the first major release to treat the train/serve split as a first-class design constraint rather than an unfortunate side effect.

Under the hood: MMDiT plus two control systems

Architecturally, Krea 2 sits in the same technical generation as FLUX. The GitHub repository’s core files — mmdit.py, autoencoder.py, encoder.py, sampling.py — identify it as a latent diffusion model built on an MMDiT (multimodal diffusion transformer) backbone. That choice is unsurprising; what distinguishes the release is the machinery Krea built around the diffusion model itself.

The first piece is a prompt expander. It is a language model, fine-tuned from open-source LLMs through a two-stage pipeline of supervised fine-tuning followed by reinforcement learning, whose job is to take short, underspecified user prompts and expand them into richer visual descriptions without overriding the user’s intent. The training data construction is clever: Krea used another language model to work backwards from long, detailed captions to synthetic “user captions”: shorter, conversational prompts that deliberately omit visual details. That produces paired data mapping incomplete input to ideal output. The team also synthesized thinking traces during training to preserve the expander’s reasoning ability, reporting that an intermediate intent-reconstruction step measurably improves downstream image quality. On the data side, the report describes oversampling visually rich and artistic imagery so the expander has broad coverage of creative territory.

The second piece is a style-reference system, which handles the cases where words fail. Users can supply one or more reference images, and the system injects their style and mood into generation while keeping content leakage to a minimum — it learns the feel of the reference, not its objects. Between the two systems, Krea 2 offers a text path and an image path to the same destination: getting what was in your head onto the canvas without writing a four-hundred-word prompt.

A day-one ecosystem that looks like a v3 launch

The partner list for this release reads less like a debut and more like an established platform’s anniversary announcement: Hugging Face, Nous Research, Replicate, Cloudflare, Together AI, Google Cloud, AWS, SGLang, FAL, and ComfyUI were all lined up at launch.

A few names on that list deserve a second look. Nous Research appearing as an open-source partner suggests Krea wants credibility with the research community, not just deployment reach. Cloudflare and the two hyperscalers cover hosted inference for teams that will never touch a GPU directly, while Replicate, Together AI, and FAL serve the API-first crowd that wants an endpoint within the hour.

Developer support was equally immediate. The Hugging Face model card documents a Krea2Pipeline integration for diffusers, running eight-step inference in bfloat16, and SGLang ships CLI support alongside a full cookbook. The launch-day Reddit AMA on r/StableDiffusion, hosted by the model team itself, rounded out the picture: this was a release aimed squarely at the community that has kept open-source image generation alive since the first Stable Diffusion weights appeared. The ComfyUI livestream on launch day was a deliberate signal to the community that actually decides whether open-source image models get adopted: the workflow builders. We made a similar observation in our review of the Qwen3.5 small models — real-world adoption of open models tracks ecosystem readiness far more closely than benchmark scores. Krea appears to have internalized that lesson before shipping, not after.

Getting started: three practical on-ramps

For developers who want to try the model rather than read about it, there are three distinct entry points, each suited to a different kind of user.

The lowest-friction path is diffusers. The model card documents a dedicated Krea2Pipeline class: load krea/Krea-2-Turbo in bfloat16, move it to a GPU, and generate with num_inference_steps=8 and guidance_scale=0.0. That last parameter is easy to miss and important to get right: Turbo has guidance distilled into the checkpoint, so adding classifier-free guidance on top of it degrades output rather than improving it. Anyone arriving from SDXL habits, where cranking CFG is the first tuning knob, will need to unlearn that reflex.

The second path is SGLang, which is the more interesting option for anyone serving images at volume. The launch includes first-class CLI support — a single sglang generate command with model path, prompt, step count, and resolution — plus a full cookbook covering deployment. Eight-step inference changes the economics of serving image generation, and the SGLang integration is clearly aimed at teams who care about throughput per GPU-hour rather than one-off experiments.

The third path is the official repository itself, which contains the reference implementation for both checkpoints. Running RAW there means accepting its research-grade defaults of 28 steps and CFG 4.5, at resolutions anywhere from 1024 to 2048. The repo also carries Krea’s recommended toolchain for fine-tuning, and its advice is unambiguous: train your LoRA against RAW, validate it, then attach it to Turbo for production inference.

Read the license before you deploy

Krea 2 ships under the company’s own Community License, described as permissive for general use, with a commercial licensing path available by contacting opensource@krea.ai. Most coverage of the release will stop there. The model card, however, contains an obligation worth reading twice: deployers are required to implement content filtering measures or equivalent review processes to prevent the generation and distribution of unlawful or policy-violating content. Failure to implement those safeguards constitutes a breach of the license.

That clause quietly shifts responsibility for content safety from the model provider to whoever deploys the model. For a team planning to wrap Krea 2 into a product, this is not boilerplate; it is a concrete engineering requirement with legal weight, and it belongs on the compliance checklist next to data handling and attribution. The model card also states plainly that Krea 2 is not intended to provide factual information, that prompt adherence varies with phrasing and specificity, and that developers should perform their own safety testing before deployment. Compared with the vagueness of some open-model licenses, spelling out the obligations this explicitly is arguably a favor to serious builders — the rules are at least written down.

What this changes for creators and developers

Zoom out and Krea 2 fits a pattern we have been tracking across the creative AI stack: the competition is moving from single-capability demos to workflow integration. Our looks at AI music video generation tools and Epic Games’ generative art pipeline for Fortnite both landed on the same conclusion: the tools that win are the ones that slot into how people already produce work. The RAW/Turbo split is precisely that kind of design. Style assets accumulate as LoRAs on the base model; production throughput runs on the distilled model; nothing in between requires switching stacks.

Three things are worth watching over the coming months. First, whether a community LoRA ecosystem actually takes root on RAW — the architecture invites it, but ecosystems grow on momentum, not invitations. Second, whether Turbo’s eight-step output holds up in sustained, real production use rather than curated launch-day galleries. Third, how deployment platforms operationalize the Community License’s content-filtering requirement, because that clause will shape where and how the model can be legally hosted. If all three break in Krea’s favor, the shortlist of first-tier open-source image models is due for a rewrite.