MiniMax H3-Image: open weights, 16 megapixels, and a speed claim with no named rival
MiniMax's H3-Image renders 16MP stills in under 10 seconds, but the launch post names no comparator and the licence excludes the US, UK, EU and South Korea.
Vlad Makarovreviewed and publishedMiniMax published the weights for H3-Image on November 10 and led with a stopwatch: a 4096 by 4096 image in under ten seconds, up to sixteen reference images, generation and editing in one checkpoint. The launch post is detailed about throughput and price and nearly silent about quality. There is no benchmark table, no comparison sheet, no independent evaluation we could find, and nothing on the Hugging Face card that substitutes for one; on release day the model's merits rest on a vendor demo and a latency chart. So separate what MiniMax measured from what it asserted, and spend the space the post did not on the two things that decide whether open weights are usable: the download and the licence.
Three multipliers, three configurations, no baseline
The speed claim appears three times, and it is a different claim each time.
| Where it appears | Claim as printed | Comparator |
|---|---|---|
| Speed section, 4K generation | "up to 5x the speed of mainstream alternatives" | not named |
| Pricing section, Standard mode | 1.5-2x as fast | not named |
| Pricing section, Highspeed mode | 3-4x as fast | not named |
All three can be true at once, because they describe different configurations: the 5x figure belongs to the 4K latency chart, the smaller numbers to two serving modes on the hosted API. The problem is that "mainstream alternatives" is never resolved into a model, a resolution, a batch size or a piece of hardware. A 5x claim against an unnamed rival cannot be checked by anyone outside MiniMax, and the pricing line has the same hole: H3-Image costs 50-70% of "comparable mainstream offerings" that are never listed. The one concrete term is a launch-week discount of 50% on requests at 4K and above.
Quality gets identical treatment. MiniMax calls prompt adherence "state-of-the-art among open-weight models"; the card upgrades that to "the strongest instruction following among open-source models". No eval, no human-preference study, no fidelity numbers. TechNode's write-up repeats the resolution and the ten-second figure under the hedge "says", which is the right amount of credence for an untested claim.
A stripped-down H3, 33.1 billion parameters deep
The card is more informative than the blog. H3-Image is the H3 architecture with the audio branch removed: a dense single-stream diffusion transformer of 33.1 billion parameters, 50 layers, hidden size 5376, 56 attention heads, FFN width 14336, 3D multimodal RoPE, the same block as the H3-Omni-Transformer. It is distilled to six sampling steps with classifier-free guidance off, and the server enforces it: num_inference_steps must be 6 or omitted and guidance_scale must be 1, or the request returns HTTP 400.
The VAE pairs a CNN encoder with a 24-layer 2D ViT decoder, 16x spatial downsampling and 24 latent channels; the transformer patchifies 2x2, so each token covers 32x32 pixels and a 4096 by 4096 request is 16,384 tokens in one packed sequence. Native output runs from 4096 by 4096 at 1:1 to 6272 by 2688 at 21:9, all near 16 megapixels and without an upscaler. That is the genuinely notable engineering result, since most open image models reach 4K by tiling or upscaling a smaller latent.
What the download actually costs
The model zoo prints 68.65 GB for the checkpoint and 17.9 GB for an optional prompt expander. The first number is honest but partial: the diffusion transformer (66.28 GB of BF16 shards, embeddings and output layers in FP32) plus the VAE (2.34 GB). It excludes the text encoder, which the card says is fetched from the parent MiniMax-H3 repository and adds 66.7 GB.
The arithmetic is not subtle. 33.1 billion parameters at two bytes each is 66.2 GB, matching the shard total, so a working install is about 135 GB of weights before activations — decimal gigabytes, roughly 126 GiB, a gap that matters when you clear a disk. The repository is bigger still: the tree API reports 100 files and 204.02 GB, because the upload carries two complete copies of the model, transformer/ and vae/ alongside transformer_diffusers/ and vae_diffusers/. The card also says the text encoder is "not in this repository", yet the tree lists a text_encoder/ folder of fourteen shards totalling 66.73 GB; one of the two is stale, and a downloader should check before trusting either.
MiniMax ships no quantized build. The docs point at SGLang, vLLM-Omni, diffusers and ComfyUI; the vLLM-Omni recipe names H200, RTX PRO 6000 Blackwell and AMD MI350X, with four-GPU parallelism for lower latency. The seventeen quantizations on the model tree are community uploads. This is not a 24 GB consumer-card story, and MiniMax never states the number a buyer needs. The hosted route is the one most users will take, through the MiniMax API, MiniMax Code and Hailuo AI.
Open weights, restricted territory
The licence will travel furthest, and it is not permissive. Hugging Face tags the model license: other, with license_name: minimax-h3-image-community-license-agreement and the text in the repository. Section I defines the "Applicable Territory" as "worldwide, excluding the Excluded Territories" — the European Union, the United Kingdom, the Republic of Korea and the United States. Section II grants rights "solely within the Applicable Territory". Section IV requires written authorization if your annualized revenue exceeds one million dollars or if you provide a hosted service. Section V forbids using the model or its outputs to improve any other AI model.
Read plainly: the files download everywhere, but the grant is void in four jurisdictions holding most of the market for image generation, and a studio putting H3-Image behind an API needs a signature first. The r/LocalLLaMA thread noticed the territory clause, and u/libregrape asked the obvious question: "I don't understand their logic. Why would they even release weights on hf, if they wanted it not be used outside of the 'applicable territory'?"
Where it sits against the rest of H3
The family has been consistent: one base model, repeated post-training passes aimed at different workloads. H3 arrived as an omni-modal video model at 2K with native stereo audio, promising weights within days. H3 Max was fal's post-trained variant, which bought throughput by dropping to 480P and 768P and was still withholding weights when we covered it. H3-Image takes the same base, removes the audio layers video needed, keeps the text encoder whole and spends the savings on resolution and step count. Every release argues from a stopwatch.
The test nobody has run
What would change the verdict is unglamorous: a fixed prompt set, the same seed, a blind comparison against the open-weight leaders at 16 megapixels, and a per-image cost measured on hardware MiniMax does not own. Until then the defensible claims are narrow. Sixteen megapixels natively in six steps is a real efficiency gain per pixel. The weights are downloadable and the licence is not open in any ordinary sense. And the headline speed number points at a competitor the post declines to identify.
