cd /news/generative-ai/minimax-h3-image-native-4k-at-16-8mp… · home › topics › generative-ai › article
[ARTICLE · art-173725] src=dev.to ↗ pub= topic=generative-ai verified=true sentiment=↑ positive

MiniMax H3-Image: Native 4K at 16.8MP in Six Steps - Three ComfyUI Workflows Compared

A developer published three ComfyUI workflows for MiniMax's H3-Image model, which generates natively at 4K-class resolution (about 16.8 megapixels) in six sampling steps rather than upscaling. The workflows cover text-to-image (six nodes), single-image editing (48 nodes), and a 16-image reference edit (48 nodes) for character and product consistency, and ship as JSON graphs without bundled model weights. All three were tested as online workflows on RunningHub, with the open question being whether the 16-image branch preserves identity when references conflict.

recommendation

Run the six-node text-to-image graph first to validate H3-Image at 4K on your hardware, then move to the 48-node edit graphs and test the 16-image branch for identity drift when references disagree.

more in playbook: Inference and self-hosting
by read2 min views3 publishedNov 21, 2026

MiniMax H3-Image: native 4K at 16.8 megapixels in six sampling steps (three ComfyUI workflows)

MiniMax's H3-Image is unusual for one reason: it does not upscale its way to a big picture. It generates natively at 4K-class resolution - about 16.8 megapixels - and it does it in six sampling steps. This episode tests that claim with three separate ComfyUI workflows, each built for a different job.

Who this is for

The three workflows, and when to use each

Text to image - AIKSK_H3_Image_文生图.json

The simplest chain: prompt in, 6 steps of sampling, 4K image out. Six nodes total, so you can read the whole graph in a minute. Use it when the image does not exist yet.

Online: https://www.runninghub.ai/zh-cn/post/2120808839725920258/?inviteCode=rh-v1111 Single image edit - H3_Image_单图像编辑.json

48 nodes. One reference image goes in with an instruction, and the model re-renders while keeping the parts you did not ask it to change. This is the workflow for "same photo, different weather / different light / fix this corner".

Online: https://www.runninghub.ai/zh-cn/post/2120808831056293890/?inviteCode=rh-v1111 16-image reference edit - H3_Image_16图编辑.json

Also 48 nodes, but the reference side is a bank of up to sixteen images. That is what you want for character consistency across angles, or for feeding a whole product set into one edit so the result matches all of them.

Online: https://www.runninghub.ai/zh-cn/post/2120808834377023490/?inviteCode=rh-v1111 What is inside the JSON

qwen3.8_27b_w4a8 for the prompt path.minimax_h3_image_pruned_int8_convrot, minimax_h3_image_vae_fp16, qwen3.5_9b_w4a8_gptq, qwen3vl_32b_minimax_h3_int8_convrot. No model weights are bundled in the repos. You bring the weights; the workflow carries the wiring, the sampling settings and the conditioning structure.

Known limits

How to try it without a local install

All three run as online workflows on RunningHub, which is what we used for the tests in the episode - same graph, no GPU required on your side:

Episode links

Where this goes next

The interesting question is not whether 4K native generation looks good in a hero shot - it does. It is whether the 16-image branch holds identity when the references disagree with each other. That is the test worth running yourself.

── more in #generative-ai 4 stories · sorted by recency
── more on @minimax 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/minimax-h3-image-nat…] indexed:0 read:2min 2026-11-21 · —