MiniMax H3 Image in ComfyUI: Three Fixes Remove the "Crunchy" Skin Without Changing the Model
MiniMax H3 Image in ComfyUI often renders "crunchy" skin: a grainy mesh and mangled fine details, as if the picture were over-sharpened. Reddit users found the cause: the model is tuned for 16 MP, while the default templates run it at 4 MP or lower. Three fixes address it: generate at 8–16 MP and downscale by half, lower s_noise from 1.10 to 0.90, and write a coherent prompt instead of tags. Before changing the model, reconfigure the pipeline.
AI-processed from TG: @cgevent (Метаверсище и ИИще); edited by Hamidun NewsDid you run MiniMax H3 Image in ComfyUI (a node-based editor for building image generation pipelines) using a ready-made template and get skin that looks like it went through harsh sharpening? Faces in a grainy mesh, blocky artifacts on hair and fabric, mangled fine details: the community calls this the "crunchy" effect. On r/StableDiffusion, users worked out how to get rid of it.
You don't need to change the model: three pipeline adjustments are enough. The first is to raise the generation resolution to 8–16 megapixels and then halve the image. The second is to lower s_noise (the amount of noise added at each step) from 1.
10 to 0.90 or below. The third is to write a coherent scene description instead of a set of tags and to connect two community patches.
Why the image comes out "crunchy"
MiniMax H3 Image is a distilled diffusion transformer. Distillation means a large model has been "compressed" into a fast version that needs only six generation steps. Its step schedule is set by the pdd_sigmas scheme, CFG is fixed at 1.0, and no negative prompt is used. The text encoders are large models from the Qwen family.
An important detail: the model was originally designed for ultra-high resolutions, up to 16 megapixels. Natively, it runs comfortably on graphics cards with 16–24 GB of VRAM or more. On cards with 8–12 GB, people run it through GGUF quants (Q2_K, Q3_K, Q4_K) with part of the weights offloaded.
When it is run at small resolutions, 4 MP or lower, or with the standard samplers from the templates, high-frequency noise does not have time to dissipate. It clumps into a characteristic mesh across faces and textures. Put simply, the model is accustomed to drawing fine details on a large canvas, and it was handed a small one.
Three settings that help
First: higher resolution. Users recommend generating close to the model's native size, that is, 8–16 MP or more. The discussion cites an example of 3552×4736. The result is then halved in size. This produces more natural details than trying to fit them into 4 MP. It does not make the process painfully slow: the post's author calls the model very fast even at these sizes.
Second: a different sampler. The suggestion is a SamplerLCM node with the Simple scheduler at six steps. The main lever here is the s_noise parameter. If you lower it from 1.10 to 0.90 or below one, micro-noise is smoothed out and the mesh disappears. This is the quickest fix: change one number and compare the results.
Third: the prompt and community patches. Instead of comma-separated tags, it is better to give the model a coherent scene description, as you would for Qwen encoders. Users additionally connect two community patches. The first is the MiniMaxH3PromptWeight node from ComfyUI-KJNodes, which helps control the weights of words in the prompt. The second is a single-frame decoder such as minimax_h3_single_frame_500k_comfy.safetensors, which replaces the base video VAE. The logic is clear: the base decoder is designed for video, while a specialized variant handles the details of a single image better.
What this means in practice
Artifacts are not always a sign of a weak model. Often the template and the launch mode are to blame. Before abandoning the model, it is worth checking three things: resolution, sampler parameters, and prompt type. It is most convenient to start with s_noise: this fix requires no new nodes and no extra render time.
Owners of 8–12 GB cards should keep a trade-off in mind. Generating at 8–16 MP on that much memory is possible only with quantized versions and offloading. This slows things down and may affect quality. How much, the discussion does not reveal.
Limitations
This is advice from a user thread, not the result of lab testing. The material contains no measured metrics, such as quality scores or generation times. Values like 0.90 for s_noise should be treated as a starting point for experimentation, not as a universal rule. Community patches are also third-party: compatibility with your version of ComfyUI and KJNodes will have to be verified yourself.
Still, for studios and enthusiasts already using MiniMax H3 Image, this is an inexpensive checklist. It takes a few minutes, requires no fine-tuning, and shows whether clean texture is achievable on the same hardware and with the same model.
- Nov 21, 2026Google Releases Gemini 4 Hydrogen: Paired with Carbon, It Cuts Quota Use by 24% and Speeds Up Tasks by 19%
- Nov 21, 2026KAIST's AI Reads Lips and Gets Only 19.4% of Words Wrong
- Nov 21, 2026Audio AI Scores Well on Tests Even With Random Noise, MIT and IBM Find
- Nov 21, 2026Anthropic Heads to IPO at $1.4 Trillion, but Seven Founders Keep 50.1% of the Votes
Key Questions Answered
Why the image comes out "crunchy"?
MiniMax H3 Image is a distilled diffusion transformer. Distillation means a large model has been "compressed" into a fast version that needs only six generation steps. Its step schedule is set by the pdd_sigmas scheme, CFG is fixed at 1.0, and no negative prompt is used. The text encoders are large models from the Qwen family. An important detail: the model was originally designed for ultra-high resolutions, up to 16 megapixels. Natively, it runs comfortably on graphics cards with 16–24 GB of VRAM or more.
What are the key details on Three settings that help?
First: higher resolution. Users recommend generating close to the model's native size, that is, 8–16 MP or more. The discussion cites an example of 3552×4736. The result is then halved in size. This produces more natural details than trying to fit them into 4 MP. It does not make the process painfully slow: the post's author calls the model very fast even at these sizes. Second: a different sampler. The suggestion is a SamplerLCM node with the Simple scheduler at six steps.
What this means in practice?
Artifacts are not always a sign of a weak model. Often the template and the launch mode are to blame. Before abandoning the model, it is worth checking three things: resolution, sampler parameters, and prompt type. It is most convenient to start with s_noise: this fix requires no new nodes and no extra render time. Owners of 8–12 GB cards should keep a trade-off in mind. Generating at 8–16 MP on that much memory is possible only with quantized versions and offloading. This slows things down and may affect quality.
Test Frontier LLMs & Autonomous Agents in One Workspace
Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.