Kromoss: MOSS-Image fine-tuned, with Turbo LoRAs for 8-step images
Developer lodestones has released Kromoss, a fine-tuned version of the MOSS-Image-Base image model. Two Turbo LoRAs come with it, cutting generation from 50 steps to 8. Everything is Apache-2.0.

What this is about
Hugging Face user lodestones has released a text-to-image model called Kromoss. It is a full fine-tune (all transformer parameters are trained further) of MOSS-Image-Base from the OpenMOSS team, at 1024 px resolution. The architecture, inference pipeline, text encoder (Qwen3.5-9B) and VAE (the "small decoder" from FLUX.2, which turns the compressed latent format back into images) are identical to MOSS-Image-SFT. That means you can use Kromoss as a direct replacement. The model has about 5.1 billion parameters and is released under Apache-2.0.
What's in the package
Besides the main model, the repo contains two "Turbo" LoRAs (LoRAs are small add-on weights that change one aspect of a model's behavior). They were distilled from MOSS-Image-Base, meaning they were trained to imitate the output of a slow process (50 steps, CFG 3) in just 8 steps:
8-steps-dmd-lora.safetensors: data-space distillation with DMD, 12,000 updates.8-steps-dmd2-lora.safetensors(recommended): the same run, continued for 3,000 more updates with the second stage of DMD2, a GAN discriminator against real images, at a quarter of the learning rate. According to the card, this gives slightly more contrast and detail.
With a LoRA you need CFG 1 (CFG, classifier-free guidance, controls how closely the image follows the prompt). There is then no negative branch, which halves the compute per step. The card says 4 steps also work. Both LoRAs are fp32 with rank 128 and alpha 128 on all projections in every block. Use only one at a time, and don't merge them into the bf16 weights, because the change sits close to bf16's rounding step.
Training
Training was a fine-tune of all transformer parameters at 1024 px; images below 896² pixels were discarded. It used the final-stage recipe from the MOSS-Image report, scaled to 64 images per update: hybrid Muon-AdamW (the optimizer) with a learning rate of 9e-6 and 200 warmup steps, truncated logit-normal timesteps, q/k-norm decay in the last block down to one, and EMA 0.999. The released weights are the EMA weights from update 11000, trained on 704,000 images.
The numbers
The CLIP ViT-L/14 score was measured on 100 PartiPrompts (higher is better; CLIP measures how well image and text match):
| Model | CLIP |
|---|---|
| MOSS-Image-Base, 50 steps, CFG 3 | 27.19 |
| Base + DMD LoRA, 8 steps | 27.53 |
| Base + DMD2 LoRA, 8 steps | 27.59 |
| Kromoss, 50 steps, CFG 3 | 27.90 |
| Kromoss + DMD LoRA, 8 steps | 27.99 |
| Kromoss + DMD2 LoRA, 8 steps | 28.13 |
The differences are small and rest on only 100 prompts and an automated metric. Whether the images look better to people is backed only by side-by-side example images on the card, not by a user study.
What you need to try it
- GPU: The card gives no VRAM requirement. The transformer has 5.1B parameters (about 10 GB in bf16), plus the Qwen3.5-9B text encoder (about 18 GB in bf16). This is our own estimate; CPU offloading or the Int8 version makes it more manageable.
- Int8 variant:
kromoss_int8_convrot.safetensorsis 5.4 GB (W8A8 with Hadamard rotation) and works in ComfyUI and with the LoRAs. - Software: diffusers ≥ 0.38, transformers ≥ 5.3, accelerate ≥ 1.10, or a current ComfyUI (master).
- Mac/CPU/Colab: Not mentioned in the source. The examples use CUDA.
Using it in ComfyUI and diffusers
In ComfyUI, the files go in the usual folders (diffusion_models, text_encoders, vae, loras). Load the text encoder with type moss_image. With a LoRA: KSampler, euler/simple, 8 steps, CFG 1. Without a LoRA: 50 steps, CFG 3, shift 5, and layer 22 is skipped in the negative branch. Included scripts convert your own MOSS-Image fine-tunes to ComfyUI format (convert_to_comfy.py) and quantize them to Int8 (quantize_convrot.py); the author says they reproduce the Comfy-Org files byte for byte. In diffusers, you load the pipeline with trust_remote_code=True, and the LoRA is applied unmerged via a forward hook.
Our take
Kromoss is a community fine-tune, not a major release. It's interesting if you already use MOSS-Image and want a slightly better model or faster generation with little effort. The quality gains rest on a small CLIP test alone, but the Turbo LoRAs are a practical win: 8 steps with no negative branch take far less compute than 50 steps with CFG. Still unclear are the training data (only the figure of 704k images is given), how it compares with other image models, and how it handles text rendering or styles. The model card is in English.
Sources
- Hugging Face Trending huggingface.co
- r/StableDiffusion huggingface.co
Try it yourself: Kromoss
Explained step by step, no prior knowledge needed – on your own computer or free in your browser.
What can I do with it?
You can generate 1024×1024 images from English text descriptions, either in 50 steps for maximum quality or in just 8 steps with a Turbo LoRA.
Who is it worth it for?
Good for ComfyUI or diffusers users who want to try MOSS-Image or generate images faster. Less suitable if you only have a small GPU and no way to offload.
What your computer needs
With enough VRAM, use the bf16 file; if memory is tight, use the Int8 file (5.4 GB). For fast results, use the 8-steps-dmd2-lora with 8 steps and CFG 1.
- The transformer and text encoder run in bfloat16; the VAE and initial noise run in float32.
- The Qwen3.5-9B text encoder is large; the card gives no minimum VRAM requirement.
- The Int8 ConvRot file is 5.4 GB.
- The examples on the card assume a CUDA GPU.
- With a LoRA, the negative branch is dropped, which saves compute.
How do I find out what my computer has?
- Windows: Press Ctrl + Shift + Esc → Task Manager → Performance tab → click GPU on the left. At the bottom you'll see Dedicated GPU memory (that's your VRAM). You'll find system memory under Memory.
- Mac: Apple menu at the top left → About This Mac. You'll see your chip (e.g. M2) and memory (e.g. 16 GB). On Apple chips, graphics and processor share this memory.
- Linux: Type
nvidia-smiin the terminal (shows your graphics card and its memory) andfree -hfor system memory.
Guide
Google Colab (in your browser, no installation)
Google Colab is a free service from Google. It gives you a computer with a graphics card in your browser for a few hours. All you need is a Google account. For this model: Colab Pro only – Free Colab has only 12.7 GB of RAM – not enough for this model.
- Download the notebook. Click the button and save the file.
- Open Colab. Go to colab.research.google.com and sign in with your Google account.
- Upload the notebook. In the window that appears, click Upload on the left (or choose File → Upload notebook at the top) and select the file
colab.ipynb. - Turn on the GPU. In the top menu, go to Runtime → Change runtime type → under Hardware accelerator, select T4 GPU (with Colab Pro: L4 or A100) → Save.
- Start everything. Runtime → Run all (keyboard shortcut Ctrl + F9). If you see the warning “This notebook was not authored by Google,” click Run anyway.
- Wait. The cells run one after another. A green checkmark appears to the left of each cell when it's done. Installation and download take about 25 minutes here.
- Try it out. The result appears below the last cell. To test something else, change the text in the cell and run it again with Shift + Enter.
- Clean up. When you're done: Runtime → Disconnect and delete runtime. This saves your free quota.
Good to know: The free GPU is limited (usually a few hours per day). After about 90 minutes of inactivity, Colab disconnects, and you'll have to start everything over.
Windows 10 / 11
This model runs on Python. Our script handles the setup automatically: it creates an isolated Python environment, installs the required packages (PyTorch, approx. 3 GB) and downloads the model (62 GB (about 83 min at 100 Mbit/s)).
- Update your graphics driver (NVIDIA): install the latest driver. Without an NVIDIA card, it runs on the CPU – much more slowly.
- Install Python. Download Python 3.12 from python.org and run the installer. Important: At the bottom of the first window, tick Add python.exe to PATH, then click Install Now.
- Create a folder and download the files. Create a folder, e.g.
Documents\AI-Test, and save both files into it: - Open a terminal in the folder. Open the folder in File Explorer, right-click an empty spot → Open in Terminal.
- Run it. Paste this command and press Enter:
Installation and download are running now. The first time, this can take 10–30 minutes.powershell -ExecutionPolicy Bypass -File try_windows.ps1 - Result. The folder now contains the generated image
output.png. - Try your own input: Open
demo.pyin an editor, change the sample text, and save. Then run this in the terminal:.\.venv-kromoss\Scripts\Activate.ps1 python demo.py
macOS
Macs with an Apple chip (M1 to M5) are ideal. Older Intel Macs are very slow.
- Open Terminal. Press Cmd + Space, type Terminal, and press Enter.
- Install the developer tools (first time only; includes Python):
Click Install in the window. If you see "already installed," everything is already in place.xcode-select --install - Download the files – both end up in your Downloads folder:
- Run it:
The first time, installation and download take 10–30 minutes.cd ~/Downloads bash try_mac.sh - Result. The folder now contains the generated image
output.png.
Linux
- Check your GPU.
nvidia-smishould show your card. If it doesn't, install the driver on Ubuntu and restart:sudo ubuntu-drivers install - Install the Python basics (Ubuntu/Debian):
sudo apt update && sudo apt install -y python3-venv python3-pip git - Put the files in a folder and open a terminal there:
- Run it:
bash try_linux.sh - Result. The folder now contains the generated image
output.png.
Try it
a tabby cat holding a sign that says KROMOSSa cozy wooden cabin in a snowy forest at dusk, warm light in the windows, photorealistica watercolor painting of a market street in Lisbon with colorful tiles
If something goes wrong
Needs recent libraries: diffusers ≥ 0.38 and transformers ≥ 5.3, otherwise the pipeline won't load.
In diffusers, trust_remote_code=True is required because a custom pipeline is loaded.
Don't merge the LoRAs into the bf16 weights; apply them unmerged.
In ComfyUI, load the text encoder with type moss_image, and you need a current master build.
With a LoRA, set CFG 1 and 8 steps, otherwise results will be poor.
“out of memory,” a crash, or your computer freezes
The model is too big for your VRAM (video memory). Pick a smaller variant from the table above and close other programs, especially games and browsers with lots of tabs.
It runs, but extremely slowly
Your CPU is probably doing the work instead of your graphics card. In Ollama, the PROCESSOR column of ollama ps shows how much runs on the GPU. If it says "100% CPU", update your graphics driver or pick a smaller variant that fits entirely into VRAM (video memory).
“ollama” or “python” is not found
Close the terminal window and open it again so it recognizes the newly installed program. For Python on Windows: reinstall it and check Add python.exe to PATH.
Windows: "Running scripts is disabled on this system"
Run the script with exactly the command above: powershell -ExecutionPolicy Bypass -File try_windows.ps1. This allows execution for this one time only.
Error message when loading the model (version, "trust_remote_code", unknown architecture)
Brand-new models often need the latest software version. With Ollama: update Ollama. With Python: pip install -U transformers in the activated environment. The Model Card usually lists the exact version.
Tokenstrom generates the scripts and notebook automatically. Please take a quick look before running them – they're plain, readable text. Mind the model's license: apache-2.0.
Ask the AI assistant
Questions about this article, installation or background? Our assistant knows this page and runs on our own machine, not in someone else's cloud.
The Assistant is an AI (Gemma 4) and can make mistakes – please check important details against the source. Questions are used only to generate an answer and are deleted after one hour. Please don't enter any personal data.
Comments
What do you think? Already tried it? Write it here, no sign-up needed.
Comments are public. Links aren't allowed, and we delete abusive posts. You can delete your own comment at any time in this browser. Learn more in the Privacy Policy.