MiniMax's first image model, released November 10, 2026 — and this site's first image-model topic: one 33.1B checkpoint for text-to-image and image editing, native output of about 16.8 megapixels (4096×4096) with no upscaler, distilled to six sampling steps, with up to 16 reference images. MiniMax claims a 4K image in under 10 seconds, but its own official comparison chart shows a 16.0-second median for Standard and 10.3 seconds for Highspeed; the weights are public, but the custom community license excludes the United States, the European Union, the United Kingdom and South Korea. The API costs about $0.022 per 1K image and $0.069 per 4K image, with 4K at half price until November 17. This page collects the official specs, pricing, licensing and the first hands-on reviews — with unverified claims clearly marked.
What is confirmed: an image model derived from MiniMax's H3 video model, one checkpoint for generation and multi-reference editing, with native 4K as its real strength — but the "under 10 seconds" claim doesn't match the vendor's own chart, the license is far stricter than the word "open" suggests, and image quality has no independent score at all.
Three and a half months from the H3 video model to the image model; on launch day the announcement, weights, API and ComfyUI support all landed at once — but the repository had been created a week earlier and sat empty until then.
MiniMax-H3 video model weights land on Hugging Face (API release notes say Jul 31); H3-Image is built on H3 and reuses its text encoder.
MiniMax-M3.1-Flash weights land on HF (API release notes say Oct 19); MiniMax's latest LLM.
H3-Image repo created (06:34 UTC), then empty for a week; Pruna releases the third-party P-H3-Image the same day (an 8-step distillation at 8MP, unrelated to the official release).
MiniMax-H3-Image-PE repo created (15:35 UTC): an optional prompt-expansion model (17.9 GB), not a variant of H3-Image.
Announced on X: "16 million pixel. 10-20 seconds. Open weights."
Weights go public on Hugging Face: 68.65 GB, under the community license agreement dated the same day.
ComfyUI blog announces native support; v0.45.0 ships the same day with text-to-image and editing workflow templates.
Official blog publishes (Nov 11, 00:23 Beijing): "Bringing 4K Image Generation into the 10-Second Era," with the latency comparison chart and pricing examples.
First coverage from Times of AI, Qiniu, agidaily and XenoSpectrum; OrcaRouter notes no third-party timing and no AA image-board entry as of that day.
437,039 downloads on the main HF repo; this topic page goes live.
The 4K half-price offer expires (Nov 18, 00:00 Beijing); list prices resume.
As published by MiniMax (Hugging Face model card, API guide and official blog, checked Nov 13, 2026). Note: 33.1B counts the DiT only, not the text encoder; the gap between the speed claim and the chart is covered in section 06C.
/v1/images/generations (JSON), editing /v1/images/edits (multipart form); PNG returned in data[0].b64_json; prompts capped at 32,000 characters, only about the first 4,096 tokens take effectFastest are the API and Hailuo; to run it yourself, the weights are public and ComfyUI supported them on day one — but budget about 135 GB of downloads and read the license first.
platform.minimax.io (global) / platform.minimax.cn (China), models MiniMax-H3-Image and MiniMax-H3-Image-Highspeed. Text-to-image and editing endpoints, token-based billing; 4K at half price until Nov 17. Note that neither endpoint is idempotent: the server finishes and charges even after a client timeout, and the guide advises turning off automatic retries.
Web app at hailuoai.video (global) / hailuoai.com (China), plus a desktop app at agent.minimax.io. No code needed; whether its pricing matches the API is unverified.
H3-Image is available inside MiniMax Code, listed by the official blog as one of the three entry points alongside the API and Hailuo.
Native support from day one (v0.45.0, Nov 10): download the weights and run on your own GPU, or use Partner Nodes to call the MiniMax API without downloading weights. Official text-to-image and editing workflow templates are provided; the Qwen3-VL text encoder is shared with H3, so existing H3 users don't re-download it.
Downloadable from Hugging Face: 68.65 GB for the model plus a 66.7 GB text encoder loaded from the MiniMax-H3 repo, about 135 GB total; the PE prompt expander is an optional 17.9 GB. The model card recommends SGLang (the reference path, with a cookbook and a single-GPU command), vLLM-Omni (recipes for H200 / RTX PRO 6000 Blackwell / MI350X), diffusers and LightX2V. MiniMax publishes no VRAM guidance — don't estimate GPUs from the file size.
Billing is per token, not per image — but MiniMax publishes a full set of per-image examples. A 4K image holds 16× the pixels of a 1K image and costs only about 3.2× as much: the shape of the price ladder that matters most. The half-price offer has days left: it ends Nov 17 at 16:00 UTC. Prices checked Nov 13, 2026 (both the USD and RMB price pages read); the checkout page is authoritative.
| Rate (per 1M tokens) | Standard | Highspeed | RMB Standard | RMB Highspeed |
|---|---|---|---|---|
| Text input | $2.30 | $2.30 | ¥15 | ¥15 |
| Image input | $1.50 | $3.00 | ¥10 | ¥20 |
| Image output | $3.80 | $7.60 | ¥25 | ¥50 |
| H3-Image-Context-IR (prompt enhancement, input) | $2.30 | ¥15 | ||
| Task | Standard | Highspeed |
|---|---|---|
| Text-to-image 1K | $0.02179 | $0.03529 |
| Text-to-image 2K | $0.02333 | $0.03622 |
| Text-to-image 4K | ||
| Edit, 1 reference · 1K / 2K / 4K | $0.02654 / $0.02658 / | $0.04525 / $0.04576 / |
| Edit, 3 references · 1K / 2K / 4K | $0.03563 / $0.04177 / | $0.06037 / $0.06069 / |
Struck-through prices are list prices; bold prices are the discounted 4K rates. RMB examples: text-to-image 1K ¥0.1430, 2K ¥0.1531, 4K ¥0.4522 → ¥0.2261; the full RMB table is in our pricing guide.
Orders are half price when the delivered image has at least 16,600,000 pixels, until November 17, 2026, at 16:00 UTC (Nov 18, 00:00 Beijing, exclusive); a 4K image (16,777,216 pixels) qualifies, 2K does not. The small print: the examples are "illustrative, not fixed per-image prices or averages," "some 1K/2K example amounts have been adjusted for presentation," actual charges depend on token usage, and promotional totals are halved before rounding.

Official pages: MiniMax official blog · Official pricing (USD) · Official pricing (RMB) · Hugging Face weights repo
Everything below is a first read from Nov 10–13 — and they share one trait: nobody has actually run a benchmark or timed anything; every speed and quality conclusion traces back to MiniMax's own materials. "Read the local article" opens this site's rewritten deep dive, with the original source at the end.
Source: Qiniu, 2026-11-11 (model-card verification, RMB prices, API endpoints)
Checks the official model card item by item: about 16MP native output, 6-step sampling, local inference paths; gives the RMB Standard rates (¥15 text in / ¥10 image in / ¥25 image out per 1M tokens) and both API endpoints; warns that commercial use and hosted services each need their own authorization check under the custom community license.
Read the local article → (our own write-up)
Source: agidaily, 2026-11-11 (licensor Nanonoble, comparison with the H3 video license)
Notes the licensor is Nanonoble Pte. Ltd. of Singapore, the excluded territory matches the Aug 2 H3 video license, but the revenue threshold dropped from $20M to $1M — and hosted services need written authorization regardless of revenue; also records ComfyUI's Nov 10 blog with native workflows and Partner Nodes.
Read the local article → (our own write-up)
Source: CellCog, 2026-11-10 (9 sections: announcement, API docs, prices, license, what's missing)
Works through the X post, API guide, price list and model card item by item: size presets, aspect ratios, images per request, output formats; flags three API behaviors — non-idempotent endpoints (timeouts still charged), a 600-second server wait, prompt enhancement always on for edits; unpacks the license clause by clause and warns that P-H3-Image is not this release. CellCog states it has not tested H3-Image and is based in the US, an excluded territory.
Read the local article → (our own write-up)
Source: OrcaRouter, 2026-11-10 (claim-vs-evidence table, price ladder, deployment costs)
Core judgment: ten seconds is architecturally plausible — six unguided steps are genuinely a different cost class from a thirty-step guided sampler — but "plausibility is not evidence": the model card states no generation time anywhere, no third-party timing existed as of Nov 11, there is no AA image-board entry, no GenEval, no DPG-Bench and no human-preference numbers; also notes the vLLM-Omni recipe exercises only 9 reference images, a first local generation needs about 135 GB of downloads, and proposes three tests worth running (API timing, identity consistency, blind A/B). OrcaRouter states it does not serve H3-Image.
Read the local article → (our own write-up)
Source: XenoSpectrum, 2026-11-11 (Japanese; numbers extracted from the official latency chart)
Extracts all H3-Image figures from the official chart: text-to-image 16.0s Standard / 10.3s Highspeed, 1-reference edits 18.2/12.5s, 3-reference edits 21.4/14.4s — while cautioning that whether the blog's "under 10 seconds" and the chart medians were measured under the same conditions is unknown, so the difference alone doesn't prove either wrong; P50 is a median, not a guarantee; and the footnote says H3-Image uses second-round P50 while other models use original data, so the chart is not a same-environment ranking.
Read the local article → (our own write-up)
Source: ComfyUI blog, 2026-11-10 16:05 UTC (native support, Partner Nodes, shared text encoder with H3)
Two ways to run it: download the weights and run natively on your own GPU, or use Partner Nodes to call the MiniMax API without downloading weights; text-to-image and editing share one graph, switching modes when reference images are connected; the Qwen3-VL text encoder is shared with H3, so existing H3 users don't re-download it. Official text-to-image and editing workflow templates are provided.
Read the local article → (our own write-up)
Source: Times of AI, 2026-11-12 (release facts + license terms)
Summarizes the release: a 33.1B DiT, six sampling steps, 4K in under 10 seconds (the vendor's claim), up to 16 reference images; the focus is the license: the EU, UK, South Korea and US are excluded, and written authorization is required above $1M in annual revenue or for hosted services.
The six articles below are our own rewritten and reorganized deep dives — restructured, with added conclusions and selection advice, and facts and figures checked against the original reviews. Open any one to read it on this site; the original source is linked at the end.
H3-Image has no benchmark scores — no GenEval, no DPG-Bench, no AA image-board entry. The only numbers that can be checked are speed: the blog says 4K in "under 10 seconds," the official chart says 16.0 seconds. Below are all the H3-Image figures from the chart (P50 median latency, seconds) and the state of independent measurement.
| 4K task (official chart P50) | Standard | Highspeed | Blog claim |
|---|---|---|---|
| Text-to-image | 16.0 | 10.3 | Under 10 seconds |
| Edit · 1 reference image | 18.2 | 12.5 | — |
| Edit · 3 reference images | 21.4 | 14.4 | — |
| 1K / 2K text-to-image (official chart P50) | Standard | Highspeed |
|---|---|---|
| 1K text-to-image | 10.6 | 7.7 |
| 2K text-to-image | 10.5 | 7.6 |
| 1K edit · 1 reference image | 14.2 | 10.0 |
| 2K edit · 1 reference image | 13.7 | 10.0 |
| 1K edit · 3 reference images | 17.3 | 12.0 |
| 2K edit · 3 reference images | 15.8 | 11.2 |
| Measurement | Source | H3-Image result | Notes |
|---|---|---|---|
| AA image boards | Artificial Analysis | No entry (as of Nov 11) | Neither image board has it — not a low rank |
| GenEval / DPG-Bench | — | None | Not published by MiniMax, not run by third parties |
| Human-preference scores | — | None | — |
| Third-party 4K timing | — | None (as of Nov 11) | Checked by OrcaRouter |
| HF downloads | Hugging Face API | 437,039 downloads / 965 likes | Evening of Nov 13; a popularity metric, not a quality metric |
Full coverage in our 10-second claim fact-check →

| Dimension | H3-Image (image) | H3 (video) |
|---|---|---|
| Released | 2026-11-10 | 2026-07-28 (weights) |
| Task | Text-to-image + image editing | Text/image/video/audio generation (video-first) |
| Architecture | H3-Base without the audio branch; 33.1B DiT | H3-Base, with the audio branch |
| Text encoder | Reuses H3's full Qwen3-VL encoder | Own Qwen3-VL encoder |
| Sampling | 6 steps, no CFG | Video diffusion sampling (step count not checked here) |
| License revenue threshold | $1M/year | $20M/year |
| Excluded territories | US, EU, UK, South Korea | US, EU, UK, South Korea (identical) |
H3-Image isn't a renamed H3: it drops the audio branch and specializes in still images, but the text encoder is fully shared — existing H3 users don't need to re-download 66.7 GB for local deployment. The image license is stricter: the revenue threshold fell from $20M to $1M, and a hosted-service trigger was added.
| Dimension | H3-Image (official MiniMax) | P-H3-Image (Pruna, third party) |
|---|---|---|
| Released | 2026-11-10 | 2026-11-03 |
| Origin | Official MiniMax checkpoint | Pruna distills the H3 video model into an image model |
| Sampling steps | 6 | 8 |
| Native resolution | About 16MP (4096×4096) | About 8MP (2912×2912) |
| Local size | About 135 GB (incl. text encoder) | About 21 GB in 4-bit |
| License | MiniMax-H3-Image community license ($1M threshold) | Older MiniMax H3 community license |
| ComfyUI | v0.45.0 native support (Nov 10) | v0.44.0 native support (Nov 4) |
The names differ by one letter P and the releases are a week apart, but they are entirely different things: P-H3-Image is a third-party distilled build that shipped a week before the official image model, and there is no sourced side-by-side quality test between them.
| 4K text-to-image P50 (official chart) | H3-Image Standard | H3-Image Highspeed | Nano Banana 2.1 medium | Nano Banana 2.1 high |
|---|---|---|---|---|
| Text-to-image 4K | 16.0s | 10.3s | 50.0s | 51.0s |
| Edit · 1 reference · 4K | 18.2s | 12.5s | 48.0s | 54.0s |
| Edit · 3 references · 4K | 21.4s | 14.4s | 62.0s | 64.0s |
The confusion around H3-Image comes from three places: two versions of "10 seconds," a similarly named third-party model, and the word "open source" used too loosely. Each claim, addressed in turn.
The blog's headline and text say so, but the official comparison chart puts 4K text-to-image at a 16.0-second median for Standard and 10.3 seconds for Highspeed — even the fast tier exceeds 10 seconds. The X announcement's "10–20 seconds" matches the chart better. 1K/2K text-to-image on Highspeed genuinely runs under 10 seconds (7.7/7.6s) — "under 10 seconds" only fails at 4K. Also note: MiniMax hasn't said whether the blog claim and the chart medians were measured under the same conditions.
The weights are genuinely public and downloadable, but the license is not a standard open-source license like MIT or Apache: a custom community license that excludes the US, EU, UK and South Korea, requires written authorization above $1M annualized revenue or for hosted services, requires commercial interfaces to display the model name, and forbids using outputs to train other models. Hugging Face lists it as license: other. "Open weights" is accurate; "open source" misleads.
P-H3-Image is Pruna's Nov 3 third-party distillation: the H3 video model converted into an 8-step image model, 8MP, about 21 GB in 4-bit, under the older H3 community license. The official H3-Image is a Nov 10 release: 6 steps, 16MP, about 135 GB. The names differ by one letter and the releases are a week apart, but the origin, specs and license are all different.
MiniMax-H3-Image-PE (repo created Nov 8) is not a model variant but an optional prompt-expansion model: 17.9 GB, NVFP4, fine-tuned from Qwen3.8-27B, for reproducing the API's prompt expansion locally (expanding short prompts into detailed English descriptions). H3-Image runs without it.
68.65 GB is only the H3-Image repo itself; the 66.7 GB text encoder lives in the MiniMax-H3 repo and must be downloaded separately on first deployment, about 135 GB in total. Also note: file size is not VRAM — MiniMax publishes no GPU guidance, so don't estimate graphics cards from 135 GB.
Half price is a launch-week promotion: 50% off when the delivered image has at least 16,600,000 pixels, until November 17, 2026 at 16:00 UTC. After that, 4K text-to-image returns to the $0.06879 (Standard) and $0.13001 (Highspeed) list prices. Budget at list price.
The announcement (X post 14:15 UTC), the weights (14:50 UTC) and the API release notes are all Nov 10; the official blog published at 16:23 UTC on Nov 10, which is 00:23 Beijing time on Nov 11 — "released Nov 11" is the Beijing-time phrasing. This site uses Nov 10 as the release date.
November 10, 2026: the X announcement at 14:15 UTC, weights on Hugging Face at 14:50 UTC, API release notes and native ComfyUI support the same day; the official blog at 16:23 UTC (00:23 Beijing on Nov 11). See section 02 for the full timeline.
By MiniMax's own official chart: no. The 4K text-to-image P50 median is 16.0 seconds for Standard and 10.3 seconds for Highspeed; 1-reference edits are 18.2/12.5s, 3-reference edits 21.4/14.4s. Whether the blog's "under 10 seconds" and the chart medians were measured under the same conditions is unstated; the X post's "10–20 seconds" matches the chart better. 1K/2K text-to-image on Highspeed genuinely runs under 10 seconds (7.7/7.6s). See our 10-second claim fact-check.
The weights are public, but not under a standard open-source license. The MiniMax-H3-Image Community License excludes the US, EU, UK and South Korea; written authorization is required above $1M annualized revenue or for hosted services; commercial interfaces must display the model name; outputs may not train other models. Hugging Face lists it as license: other. See our license deep dive.
Token-based billing: Standard $2.30/$1.50/$3.80 (text in / image in / image out, per 1M tokens), RMB ¥15/¥10/¥25. Examples: text-to-image 1K $0.02179, 2K $0.02333, 4K $0.06879; orders are half price when the delivered image has at least 16,600,000 pixels, until November 17, 2026 at 16:00 UTC (Nov 18, 00:00 Beijing). See our pricing guide.
Hugging Face MiniMaxAI/MiniMax-H3-Image: 68.65 GB for the model, plus a 66.7 GB text encoder from the MiniMax-H3 repo, about 135 GB total; PE prompt expansion is an optional 17.9 GB. Framework support: SGLang, vLLM-Omni, diffusers, LightX2V, ComfyUI. MiniMax publishes no VRAM guidance. See our local deployment article.
Yes, with native support from day one: the ComfyUI blog announced it on Nov 10, and v0.45.0 includes H3-Image nodes with text-to-image and editing workflow templates. Two ways to run it: download the weights and run on your own GPU, or use Partner Nodes to call the MiniMax API without downloading weights. The Qwen3-VL text encoder is shared with H3, so existing H3 users don't re-download it.
Up to 16, addressed in the prompt as "Picture 1" through "Picture 16" in upload order. Note that vLLM-Omni's day-one recipe only exercises 9 images per request — 16 is the model limit, 9 is what that framework's recipe measured. Reference images support JPG/PNG/WebP/HEIC/HEIF, 128–8,192 pixels per side.
The API guide explicitly lists as unsupported: masked edits, transparent backgrounds and preview images. Sampling parameters are locked: steps can only be 6 and guidance only 1 (other values return HTTP 400), with no negative prompts. Prompt rewriting is always on for edits and can't be disabled. Both endpoints are also non-idempotent: if the client times out, the server still finishes and charges.
P-H3-Image is Pruna's Nov 3 third-party distillation (8 steps, 8MP, about 21 GB in 4-bit, under the older H3 license), not a MiniMax release; H3-Image is MiniMax's Nov 10 official model (6 steps, 16MP, about 135 GB). There is no sourced quality comparison between them.
The model is designed for detailed English prompts describing the whole image. The API expands short prompts in any language via H3-Image-Context-IR into detailed English before generating; local deployments can use the optional PE model (17.9 GB) for the same expansion, though MiniMax doesn't guarantee it matches the API exactly. Prompts are capped at 32,000 characters, with only about the first 4,096 tokens taking effect.
As of Nov 11, there are no independent benchmarks: no Artificial Analysis image-board entry, no GenEval, DPG-Bench or human-preference scores, and MiniMax itself publishes no evaluation table. The model card's claim of "the strongest instruction-following among open-source models" has no numbers behind it. This site will keep tracking it.
The weights license excludes the US, EU, UK and South Korea — anyone there needs a separate license from MiniMax before using the weights. API use is governed by the service terms instead, which may differ from the weights license — check the service terms separately before using the API.
All facts on this page come from the public sources below (checked Nov 13, 2026).