MOSS-Image: OpenMOSS releases a 5-billion-parameter image model under the Apache-2.0 license
Weights, code and a permissive license: MOSS-Image comes in two versions, Base and SFT. Its strong layout ranking is, for now, self-reported.

On October 16, the OpenMOSS team released MOSS-Image, a 5-billion-parameter image generation model. The most important point is not its size but its license: Apache-2.0, one of the most permissive there is, which allows commercial use, modification and redistribution with no revenue condition.
The model comes in two variants: Base, the pre-trained model, and SFT, refined through supervised fine-tuning. The weights are published on Hugging Face and the code on GitHub, so anyone can audit it and fine-tune it themselves.
A ranking still to be confirmed
According to the team’s report, MOSS-Image ranks 2nd on RealLayoutArena, a benchmark focused on layout. That is promising for uses where composition matters (posters, visuals with text), but it is a self-reported result: we are waiting for an independent measurement.
Already an editing add-on, with caution
A secondary source reports a community add-on, Moss-Image-Edit, which lets you edit an image with a single sentence in ComfyUI and is said to run on an 8 GB RTX 4060 in 8-bit. The problem: its weights have no clear license. For professional use, it is better to stick to the official model for now.
Our take
A 5-billion-parameter model under Apache-2.0, with weights and code, is exactly what studios that want to integrate image generation without negotiating a license were missing. Its quality still needs to be verified outside its authors’ own report.
Sources
- OpenMOSS — MOSS-Image-Base (weights, Hugging Face) Primary source
- OpenMOSS — MOSS-Image (code, GitHub) Primary source
- Fervor Creative AI — October 25, 2026 briefing (Moss-Image-Edit) Secondary source
A primary source comes directly from the company, lab or organization concerned. A secondary source reports the information without being its author: we flag it as such. Spotted an error? See our corrections policy.
