MOSS Image is a 5B parameter text-to-image DiT from the OpenMOSS team, built for accurate in-image text, layout control and long prompts. It pairs a Qwen3.5 9B text encoder with the FLUX.2 VAE, accepts prompts of up to 4K tokens in natural language, booru-style tags or a JSON layout, and renders from 512px up to 2K at any aspect ratio.
Originally released by OpenMOSS on Hugging Face. All credit for the model goes to the OpenMOSS team. Civitai hosts a mirror so creators can generate with it on-site and train against it. Head to the original repo for the reference pipeline, the user guide and updates.
Two versions
SFT is the supervised fine-tune of Base on curated data. OpenMOSS recommends it for generation: cleaner text grouping and more organised layouts.
Base is the undistilled base model with no post-training. OpenMOSS recommends it for fine-tuning and LoRA training. LoRAs trained on Base can also be used on SFT, with partial compatibility.
Both run at 50 steps with CFG 3 (raise it for short prompts), flow-matching Euler, shift 5. OpenMOSS recommends English prompts; Chinese and other languages are supported. Use line breaks and quotes around text you want rendered.
Files
Each version carries the diffusion model in bf16 and int8, from the Comfy-Org repackage. The Qwen3.5 text encoder and FLUX.2 VAE ship in the same repo. The original Diffusers weights are at MOSS-Image-Base and MOSS-Image-SFT.
Generating on Civitai
Both versions are in the Civitai generator for text-to-image, with steps, CFG and a negative prompt exposed. JSON layout prompts work as plain prompt text. Image editing and reference images are not part of this release.
License
MOSS Image weights and inference code are released under the Apache License 2.0. Commercial use, derivatives and LoRAs are allowed; keep the licence notice with any redistribution.
Links
Description
FAQ
Comments (86)
ohh can't wait to try this one ! Thank you !!!!
I'm never optimistic about newer models, but this is THE model kids, remember to use BBox, and for creators do your stuff and start creating LoRA's, this model has the potential to replace Krea 2
yeah bbox works quite well with minimal prompt leakage
@Lynx2025 Model is insane, my Krea prompts are simplistisc AF (I don't use LLM's) but this model understands basically the most basic stuff and it gets right, it has some deformation with fingers and sometimes it gets body horror's but I believe that is a issue with the turbo LoRA, but with time it will be a great model.
Yeah this is gonna replace Krea 2 probably. Hopefully Krea 3 takes notes otherwise it'll be irrelevant with this model's release.
What is Moss Image and how dose it comepare to Krea 3/2 and Qwen Image 2.1?
Interesting. Quite costly at like 40 buzz / image. But this is without Turbo LoRAs.
RIP Flux3 klein for sure .... and probably Krea2 and Anima (new anime dataset cutoff ~05.2026).
Krea2 still good for the near future. 12 buzz/image with Turbo. A lot of LoRAs and checkpoints. It'll take a few months for MOSS to truly unseat it.
Cant make it work localy on Comfyui, it just not see config.json in transformer/
comfyui works fine. update comfy to latest build instead of stable, or just wait a bit for a new stable update
WOW, fully uncensored from the factory
One day I'll see an open weight diffusion transformer this small that looks good and edits too.
It knows many characters and concepts (best NSFW base model yet), but prompting is hard: results are unstable with many artifacts. Maybe a good skill with decent LLM can make it right, utilizing it's 4K context window (Krea 2 only has 512)
This is, to date, the most knowledge-rich open-source text-to-image model (for realistic).
It is capable of handling both anime and realistic styles, and it is uncensored. Although there are occasional issues with limb structure, I believe it will only get better in the future.
This is a nice little model, size wise, cause in terms of realism it can give Qwen2.1 a run for their money. I still like Anima more but I've heard they're working on Anime targeted version.
A new king is here🙌.Moss blow out of the water Krea 3 Klein and I’d say it’s slightly superior to the Krea 2.
I don't think it's superior to Krea2 honestly, but definitely a nice mix of Flux and Anima. If they release MOSS XL or something like a 12B parameter model, then yeah possibly. The license is very good as well.
This model is pretty damn incredible.
it can handle complex poses pretty well, and is pretty creative with compositions and styles.
MOSS Image extension for Neo by eduardoabreu81:
https://github.com/eduardoabreu81/moss-image-forge-neo
That was quick.
This model has potential.
Out of the box, its uncensored and shows decent prompt adherence to both tags and natural language. It's got bounding boxes which enable more complex compositions as well.
I've not got it to work with artist style tags, so I'm guessing they were pruned from the dataset.
With a good finetune, this would overshadow Anima, however, I'm interested to know what differences in training methodology would this model require. Guess it's time to take a look at the paper.
Adding on for anyone interested in training as well, the paper only covers their dataset preparation methodology briefly.
For a better idea of how the MOSS team captioned their images, do check out this guide under their GitHub repo -> https://github.com/OpenMOSS/MOSS-Image/blob/main/USERGUIDE.md#post-training
Edit: Turbo lora in comments, generation times is now 1/10th of what it was, quality is also great (bit softer skins and some defmored legs - higher steps ~25 will fix the skin).
Generations are too Slow (+100seconds). needs turbo lora.
Quality is really good tho, one of if not the best.
there is a turbo lora
https://huggingface.co/lodestones/MOSS-Image-SFT-8-steps-dmd
I used for the following images:
https://civitai.red/images/145922389
https://civitai.red/images/145919628
https://civitai.red/images/145915725
https://civitai.red/images/145899953
@aj_prime8517 man that was fast :D thank you very much
@aj_prime8517 Super fast gens with the turbo lora thx. 1.5mp takes 10 secs now lmao
@mu5ic3oy337 yep. 12second now for me and quality is great too.
@infernahermit846 you are welcome!!
But all the praise for the creator of the lora, I am only an user of it
@aj_prime8517 I understand but I had no idea there was a lora before you mentioned it.
quality above speed, Turbo loras kill quality, the model is fast to begin with if you play with the settings and have a capable GPU
@hRUSTIN474 Every model is fast if you have a capable gpu, thats not the point and we dont have capable gpus. also the lora with 15 to 25 steps generates superb images with high quality and since we are using 1 CFG it's fast.
@infernahermit846 other option is to use the lora with 8 steps and CFG 3 that is I use with my images, in generation time should be equivalent to 16 steps with CFG 1, I don't know which combination provide better quality (concept that on the other hand is subjective) and maybe it will depend on the kind of images are generated, for instance I don't usually generate realistic images of people
@aj_prime8517 True. for me any CFG higher than 1 burns the image a little bit but at 15 to 25 steps gives me a really high quality output. it's fine with 8 step 1cfg but body hair, grass becomes plastic(ish) and skin gets too soft.
But for cartoon/3d looking stuff cfg3 works really well, like the bee you made.
All the images I uploaded here were generated in 8-steps with the unfinished Turbo Lora from Lodestones. CFG1.0 Euler-SGMUniform. Seems to work pretty well.
@Talanca Yep, me too, uploaded 8 images, with the range from 10 to 25 steps.
This model just killed Anima
Update:
1: Content
This model is impressive, it was trained on a lot of booru stuff
It can do 2D anime style, 3D cgi style and even realism very well
2: Prompting
This model can process prompts from very complicated and descriptive to simple tags like SDXL
It can accept simple and even vague prompts, unlike Anima where you HAVE to be very descriptive if you want a good result
It accepts negative prompts
3: The good
It uses very little vram, I don't know what dark magic the devs used for this but somehow it's running on about 6GB on q8 gguf
completely uncensored, so you will not have to run some lora or a modified model that ends up messing with the weights
And you will not suffer with incompatible loras because someone changed a 0,0001 to 0,00015 on some obscure setting on a merging tool
4: The bad
It's a bit slow, not Qwen image 2.1 slow, but noticeable
there are 8 steps and 4 steps loras right now, so it can be bearable
(On the 4steps lora i had to run on 6 steps to get a good result, so that's just 2 steps less than the 8 steps lora)
when prompting, some times you will have to be a bit forceful to get the style you want
For example, i was trying to make a mecha girl, for some reason it kept defaulting to Gundan
I had to play around with the promp for a bit to get a result that wasn't gundan related
It tends to add a focus effect on things
you basically have to tell it to not do that
Very often it focuses on the main subject and leaves everything else unfocused
You will notice that
Some times it generates extra limbs, legs most of the time
On text rendering...
Krea, Qwen image and even Zimage can casually render text
MOSS you have to specify the text, where and how it's going to be
Else you'll have a bunch of gibberish text
Not as bad as IL but meaningless
No image editing besides using a reference to an end result
Conclusion:
I don't know how it compares to Krea 2/3 or Qwen Image 2.1
For sure it does not reach them on quality
but beats them on speed
This model kills Anima and IL
vram, size, quality, speed, prompting, diversity of content and general features
I believe this will become the default for many people as Anima is quite dumb and IL can't do text or realism very well
What i expect for the future:
Turbo model, It's preferable to a turbo lora
SVDQuant, I don't expect the developers to make that, but i can't wait for someone to do it
Anime focused model, I prefer how it is right now as it can hit many different styles, but i know many people like anime style models and it would completely end Anima
Extra:
Clip skip is useless, it just makes images foggy
don't even bother touching that setting
Same people are focusing on an anime version. Imagine that.
No innate support for artist tags is a huge negative sadly ;_;
@DaddysLilMistake Yeah, but it's always better to use a lora for that as it will always give a better result
One thing i like a lot is that it's able to get characters very well
I even tested on some obscure characters and the model was able to make them
@DaddysLilMistake Had a feeling "kills Anima" was a bit overstated.
This is future(especially work with 8 steps lora)
Great tool to generate moss in particular!
An original scheduler for the checkpoint from creators: https://huggingface.co/OpenMOSS-Team/MOSS-Image-Base/tree/main/scheduler
Could you tell me how to use this?
https://github.com/OpenMOSS/MOSS-Image/tree/main/comfyui
Official node pack doesnt have a custom scheduler node
I'm not a comfy user but according to Grok:
1. Create a folder for the node
Bash
cd /path/to/ComfyUI/custom_nodes
mkdir my_moss_scheduler # or any name you like
2. Put the .py file inside
Copy your ready Python file into the new folder, for example:
text
custom_nodes/my_moss_scheduler/moss_scheduler.py3. Create init.py
In the same folder create a file named exactly init.py with content like this (adjust the import and class name to match your file):
Python
from .moss_scheduler import YourSchedulerClassName # change to the actual class name inside the .py
NODE_CLASS_MAPPINGS = {
"MOSS Custom Scheduler": YourSchedulerClassName, # the key is the internal name
}
# Optional – nicer name that appears in the menu
NODE_DISPLAY_NAME_MAPPINGS = {
"MOSS Custom Scheduler": "MOSS Custom Scheduler",
}
__all__ = ["NODE_CLASS_MAPPINGS", "NODE_DISPLAY_NAME_MAPPINGS"]How to find the class name: Open the .py file and look for a class that has:
INPUT_TYPES (or the newer define_schema)
RETURN_TYPES (often ("SIGMAS",))
FUNCTION = "get_sigmas" or similar
CATEGORY = "sampling/custom_sampling/schedulers" (or similar)
Use that class name in the import.
4. Restart ComfyUI completely
Close the server and start it again. Refresh the browser (Ctrl+F5).
After restart, search for the node name in the node menu (right-click → Add Node, or the search bar). It should appear under the category defined in the file (usually sampling/custom_sampling/schedulers).
5. How to use it
Most custom scheduler nodes output a SIGMAS tensor. Typical wiring:
Connect your MODEL (and steps / denoise if the node asks for them) into the custom scheduler node.
Connect the SIGMAS output into a SamplerCustom, SamplerCustomAdvanced, or KSamplerAdvanced (the sigmas input).
Do not use the normal scheduler dropdown on a regular KSampler when you feed custom sigmas.
Quick checklist if it doesn’t appear
Look at the ComfyUI console / terminal for import errors (red text).
Make sure the folder contains both the .py file and init.py.
Class name and import must match exactly (case-sensitive).
No syntax errors in the Python file.
If the file already contains NODE_CLASS_MAPPINGS at the bottom, you can sometimes just drop the single .py into custom_nodes/, but the folder + init.py method is more reliable
画师提示词的效果几乎没有,如果能修复这一点将是绝杀
Hello CIVITAI, again, can you STOP RENAMING FILES PLEASE? @CivitaiOfficial @JustMaier. How come "qwen3.5_9b_int8_convrot" becomes "mossImage_sft_txt_int8"? This really is a nightmare that has to stop
Are you sure this qwen was not finetuned?
so NVIDIA only huh
no
I'm using my Intel Arc b580.
(Intel cards) For fast enough int8 you should rewrite default pytorch int8 processing - asked AI to do it. Currently 1.5 seconds per step (was 4 seconds per step in int8 initially), but can be better as bf16 is initially 1.5 seconds per step without any improvements - it just have better software support. I have used only free coding agents for it. Waiting for limits lift to continue optimization.
no sir... 9070XT here (2Mp latent) : "100%|██████████| 50/50 [01:20<00:00, 1.61s/it]"
;)
I'm running it just fine without NIVDIA
Why are the file names that actually download almost all different from the names listed on this page before you download? Did someone literally take files with proper names from the Moss creators, which would allow people to know what they have, and rename them for no reason, or are we not getting what we think we are getting?
Will Moss be added to the AItoolkit on CIVITAI?
Brudda I got my storage full of Illu, Krea, Q2.1 and H3 models, have some mercy
That’s the same for me, bro lol
I cleared out the storage for Krea 2 and Qwen 2.1, but Krea 3 is already coming out...
remove ALL old image models
2. VAE differences
Official ComfyUI packages use the full FLUX.2 VAE, which is different from the one used in our official ckpt. We use a smaller decoder version to help eliminate some strange artifacts and spots in generated images. This shouldn't have any noticeable impact on inference efficiency.
FLUX.2 small decoder: https://huggingface.co/black-forest-labs/FLUX.2-small-decoder
You found a lot of information on this topic, awesome! I've subscribed, keep it up, bro :)🔥
thanks for your information!
It is a great model, it is completely uncensored. Follow very good the prompts and it has a great quality. I think it has the same quality as Krea2, but it is faster.
Better than krea2 I think. No need for uncensor loras, has no plastic skin or vae issues and is faster.
OH YES! It is completely uncensored. It can do tentacles as well! :D :D
@bpbp2 my first impression is its on par. it feels less 'alive' than krea2 though, just a feeling i get after looking at a bunch of images. seed variety is much better though.
They are gonna release anime/donghua version as well so it make sense that moss doesnt have character knowledge yet
Considerung its size its a really good model although its inferior to krea 2 in terms of image quality. Definitely better than qwen 2.1 and flux 3 klein. Im talking about straight t2i here. It would probably surpass krea 2 if it had double or triple the parameters.
I have tried several of the workflows attached, and I am getting an error on the ComfyUI Desktop versions. Is this model not yet supported on Desktop? I assume some of you are using the portable version? The workflow I am using has basic nodes.
I just used my Krea2 flow - switch the clip to moss-image and switch the models out.
You do need to update your comfy to the latest version.
@Fatbuns did it already, i get '
The value moss_image for Load CLIP's type is not available.'
I'm using latest protable version. it is not yet added to comfy's templates either. but works for me.
@yoloswagg45 Not sure if it will help (or if you already tried this), but I was getting the same error after installing the latest requirements, did a git pull in the comfyui folder and the moss image option for the clip appeared after that.
Looking at the images here… Damn! Is this models really can do everything without loras?
Yes, but it's extremely sensitive concerning correct hand and feet anatomy, and hardcore NSFW stuff depends a lot on the seed and you need some luck.
Yeah it seems crazy but it legit works, and as @Experimental_dAIver stated, hardcore stuff is a dice roll, I tried cunnilingus (as that's the hardest thing for ai to do nsfw) and I get it like 1/5 seed attempts.
For 5B checkpoint it's even great, can be compared with ZIT/ZIB with more parameters. Don't ask about FLUX Klein, 2 and 3. Just forget them.
It has various minuses in textures but TBH, I don't look at them because the subj is a loyal to weak GPUs with good perfomance. SDXL/SD1.5 were also poor someday.
Seed variety and texture are excellent with the full 50 step treatment. Krea2 is much better at expressions though, all the ones in here are the dead eyes again like in many other models
Avoid this model in anime anatomy. It makes it incorrect.
Details
Files
mossImage_base_txt_int4.safetensors
Mirrors
flux2-vae.safetensors
Mirrors
FLUX_2_Klein_Train_VAE.safetensors
flux2_vae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2_ae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
kx7_m_1032dadf51.safetensors
flux2-vae.safetensors
kx7_m_1032dadf51.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2_vae.safetensors
flux2-vae (1).safetensors
flux2-vae.safetensors
flux2-vae.safetensors
FLUX.2 VAE [FP32].safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
Flux2-vae.safetensors
kx7_m_1032dadf51.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2_ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2_ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2_ae.safetensors
flux2_ae.safetensors
flux2-vae.safetensors
flux2vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2_ae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-dev-vae.safetensors
flux2-dev-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
ae.safetensors
flux2-vae.safetensors
ae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
vae_flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
ae.safetensors
ae.safetensors
flux2-vae.safetensors
decoder-01.safetensors
ae.safetensors
ae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
ae.safetensors
flux2-vae.safetensors
ae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
ae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors
flux2-vae.safetensors





