Skip to main content

Local setup

MOSS Image ComfyUI guide

MOSS Image runs natively in ComfyUI 0.42.0 and later. Pick your GPU memory and this MOSS Image ComfyUI guide shows which files to download, where they go and the settings to start with.

Your GPU memory

12 GB: the official int8 set

These are the files ComfyUI's own MOSS-Image templates load. A community test on a 12 GB RTX 4070 ran a larger set, with the int8 text encoder, at 832 x 1216 in about 51 seconds for 50 steps.

Download

Total download: 13.0 GB

Start with

  • Template defaults: 25 steps, CFG 2.5, er_sde sampler
  • For more detail: the official 50 steps and CFG 3
  • 1 to 2 megapixels, width and height in multiples of 16

File sizes are from the Hugging Face repos (Comfy-Org/MOSS-Image, realrebelai/MOSS-Image_GGUFs), checked October 20, 2026. Memory tiers come from community tests and file sizes, not our own runs; real use depends on resolution and what else is on the GPU. Sources are listed at the end of this page.

Files

Where the MOSS Image ComfyUI files go

Three files make a working MOSS Image ComfyUI setup: the diffusion model, the Qwen3.5 9B text encoder and the FLUX.2 VAE. Each goes in its own models folder.

  • UNET Loader reads the diffusion model
  • CLIPLoader reads the text encoder, with type set to moss_image
  • VAE Loader reads flux2-vae_small or flux2-vae

Full list of builds: Comfy-Org/MOSS-Image on Hugging Face.

ComfyUI
# 12 GB set, from Comfy-Org/MOSS-Image on Hugging Face$ mv moss_image_sft_int8_convrot.safetensors ComfyUI/models/diffusion_models/$ mv qwen3.5_9b_w4a8_gptq.safetensors ComfyUI/models/text_encoders/$ mv flux2-vae_small.safetensors ComfyUI/models/vae/# Restart ComfyUI so the loaders list the new files

Setup

How to set up MOSS Image in ComfyUI

From an existing ComfyUI install to the first image in five steps.

  1. 01

    Update ComfyUI to 0.42.0 or later

    The 0.42.0 release on October 18, 2026 lists MOSS-Image support in its notes; ComfyUI's own guide names 0.41.3 as the minimum. The desktop app updates itself; a git install needs a pull, the portable build its update script.

  2. 02

    Download the files for your GPU

    Pick your memory in the guide at the top of this page. The 12 GB set is the one the official templates expect.

  3. 03

    Move them into the models folders

    diffusion_models, text_encoders and vae, then restart ComfyUI.

  4. 04

    Open a MOSS-Image template

    Browse Templates and search "MOSS-Image". There are four: Text to Image and Layout-Guided Text to Image, each for SFT and Base. Start with SFT.

  5. 05

    Describe the finished image and run

    Write what the picture looks like, put every word to print in quotes and add line breaks where the text should wrap.

Settings

MOSS Image ComfyUI settings: template vs official

The ComfyUI templates trade some detail for speed. When an image looks soft or unfinished, switch to the values OpenMOSS publishes.

FeatureComfyUI templateOpenMOSS recommendation
Steps2550
CFG2.53
Samplerer_sdeEuler (flow matching)
ShiftIn the template subgraph5
Skip layer guidanceOn, layer 22On, layer 22
Negative promptnsfw, worst quality, bad anatomy, watermark, jpeg artifactEmpty
Resolution1 megapixel1 to 2 megapixels

Speed

Faster MOSS Image in ComfyUI

Fifty steps on a 5B model take a while on consumer cards. Three ways to cut the wait, from simplest to most involved.

  • Keep the template at 25 steps

    Half the official step count, already set in the official templates. Raise it only for images that need finer detail.

  • Turbo int8 build: 8 steps

    A community 8-step version of the SFT model (toxicdog/MOSS-Image-SFT-Turbo-INT8-ConvRot, 5.41 GB) that drops into UNET Loader. Run it at 8 steps, CFG 1, euler, simple. Experimental: compare it with the standard model on your own prompts.

  • Step-distilled LoRAs: for tinkerers

    There are 4-step and 8-step LoRAs (akhaliq, darask0, lodestones), but they ship extra time embeddings and some need an fp32 model and their own sampler. Wait for a ready-made workflow unless you enjoy wiring nodes.

Troubleshooting

Fix common MOSS Image ComfyUI errors

The MOSS Image ComfyUI problems people hit most in the first week, and what fixes each one.

  1. 01

    Missing nodes, or no moss_image type in CLIPLoader

    Your ComfyUI is older than 0.42.0. Update it, or install the OpenMOSS MOSS-Image plugin from ComfyUI Manager.

  2. 02

    Every image is pure noise

    A ModelSamplingSD3 node in the workflow causes it. Replace it with ModelSamplingAuraFlow or ModelSamplingFlux, or start again from the official template, which has none (ComfyUI issue 17119).

  3. 03

    Out of memory

    Switch to the int8 files, stay at 1 megapixel, start ComfyUI with --lowvram, or move to the GGUF route on 8 GB cards.

  4. 04

    Text comes out garbled

    Quote every word to print, add real line breaks and keep each block short. For exact placement, use the Layout-Guided template.

  5. 05

    A GGUF file will not load

    GGUF builds need the ComfyUI-MOSS-GGUF and ComfyUI-GGUF custom nodes and their own loaders. The W4A8 safetensors model files do not load in that node.

  6. 06

    Images take far too long

    Your GPU is short of memory and ComfyUI is swapping to system RAM. Use a smaller set from the guide at the top, or run MOSS Image online.

Sources

Checked October 20, 2026. Memory tiers and speeds come from these community reports, not our own runs.

Skip the setup and run MOSS Image online

No download and no GPU. Type a prompt or plan a layout in the browser; new accounts start with 6 free credits.

FAQ

MOSS Image ComfyUI questions