Early-bird pricing (ends Dec 25), locked in while you stay subscribed: Go $10/mo (normally $20), Plus with Opus 5.5 just $30/mo (normally $50)Subscribe →

MiniMax H3-Image API: 4K Cost, Limits, VRAM (2026)

MiniMax H3-Image renders 4096 × 4096-class output in a reported 10.3 seconds P50 on Highspeed and 16.0 seconds on Standard, per MiniMax's latency chart. For straight text-to-image at 4K, its Standard example price ($0.06879) sits below the third-party hosted price listed in this article (WaveSpeed: $0.03 per image at 1K/2K, $0.09 at 4K); Highspeed ($0.13001) sits above it — but for multi-reference editing that must preserve identity, linked user reports say to look elsewhere.

4K in about 10 seconds, but early edits disappoint

H3-Image is a new open-weight image model built on MiniMax H3 video. It does text-to-image, reference-based generation, and editing, with up to 16 reference images and up to 10 outputs per request. Its 1K/2K/4K area levels target 1,048,576 / 4,194,304 / 16,777,216 pixels; the server derives exact width and height from the aspect ratio and reports them in data[].size, so 4K is a target area, not always a literal 4096×4096 square.

MiniMax reports strong P50 latency, although its 4K comparison is narrow. MiniMax's P50 latency chart lists 7.7s at 1K and 10.3s at 4K for Highspeed text-to-image, versus 10.6s and 16.0s for Standard. At 4K the chart only compares against Nano Banana 2.1 (50–51s), so the "5x faster than mainstream" claim rests on a thin slice.

In the linked Reddit threads, commenters confirm fast T2I but report the same two gaps: likeness loss on references, and soft detail at claimed high resolution.

"Sadly it is very bad as a ref2i model compared to the actual H3 video model for ref2i" — u/Omegapepper on r/StableDiffusion

"People might get mad at me, but from what I've tested, it's significantly inferior to QI 2.1 [...] for multi-reference editing." — u/Crazy-Repeat-2006 on r/StableDiffusion

In the linked recommended-sizes thread, testers describe low-resolution softness and blur on outputs that should be sharp, and debate whether claimed high resolution carries genuine high-frequency detail. These are early anecdotal reports, not a controlled benchmark — but they point the same direction.

What the API actually sells: two models, two endpoints plus expansion

There are two model IDs, two image endpoints, plus a prompt-expansion step on the MiniMax API docs.

ItemMiniMax-H3-Image (Standard)MiniMax-H3-Image-Highspeed
GoalLowest cost per imageLowest latency
Text input$2.30 / 1M tokens$2.30 / 1M tokens
Image input$1.50 / 1M tokens$3.00 / 1M tokens
Image output$3.80 / 1M tokens$7.60 / 1M tokens

Endpoints (Global host below; China accounts use the China endpoint from the same docs):

  1. POST https://api.minimax.io/v1/images/generations — text-to-image; verified params include model, prompt (max 32,000 chars), disable_prompt_enhanced (default false), n (1–10), size (auto or WIDTHxHEIGHT), aspect_ratio, area (1K/2K/4K, default 4K), output_format (default jpeg), response_format (url/b64_json), stream, output_compression.
  2. POST /v1/images/edits — editing with 1–16 references; refs accept JPG/PNG/WebP/HEIC/HEIF, 128–8192 px per side.
  3. H3-Image-Context-IR — prompt-expansion step (not an image endpoint) that rewrites a short prompt and picks an aspect ratio.

Copy-pasteable shape (Global host):

bash
curl https://api.minimax.io/v1/images/generations \
  -H "Authorization: Bearer $MINIMAX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"MiniMax-H3-Image","prompt":"...","size":"auto","aspect_ratio":"16:9","area":"2K","disable_prompt_enhanced":false,"response_format":"url"}'

The docs specify that requests are non-idempotent, the server may take up to 600 seconds, generation continues after a client timeout or disconnect, a completed image is still charged, and only successful images are billed (usage counts successes). MiniMax recommends max_retries=0 with the OpenAI SDK. Partial success returns HTTP 200 with per-image data[].error entries (including content-safety failures), so inspect every item; only all-failed batches return 4xx/5xx. Treat most 4xx as terminal config errors, never re-POST on ambiguous timeouts, and on async providers poll the existing job instead of submitting another.

Prompt enhancement is on by default, can be disabled for text-to-image but not for edits, and the API returns the rewritten prompt in data[].revised_prompt. Log it and compare it against your submitted prompt before tuning anything else. Note the disabled-enhancer limits: the model then reads roughly the first 4,096 tokens, and you must supply an exact size or an explicit aspect ratio.

Self-hosting is not 10 seconds: weights, VRAM and license

Weights are live at Hugging Face MiniMaxAI/MiniMax-H3-Image and GitHub MiniMax-AI/MiniMax-H3-Image, with ComfyUI converted weights and a image_minimax_h3_image_t2i.json workflow template. The card documents a 33.1B-parameter diffusion transformer, a 68.65 GB BF16 checkpoint, and a separate 66.7 GB H3 text encoder — roughly 135 GB before the optional 17.9 GB prompt-expander. The card pins the local server to 6 inference steps with guidance scale 1 (other values return HTTP 400 there) and no negative prompts.

Do not plan for 10 seconds on a gaming card. ComfyUI threads ask whether the model fits a 5090 even at 4-bit quantization. In the linked open-weights thread, one RTX 5090 user reports about 21 seconds for 16 MP in INT8 with grainy output, needing BF16 for sharpness at longer time. One RTX 3070 Ti user in the ComfyUI thread calls T2I fast for 16 MP output, but says reference editing ignored the prompt — a single-user datapoint, not proof that aggressive quantization is safe for reference work.

License matters more than VRAM for many teams. The model card uses the MiniMax-H3-Image Community License Agreement dated November 10, 2026: the default grant excludes the United States, European Union, United Kingdom and Republic of Korea, requires prior written authorization above $1M annualized revenue or for hosted services to third parties, and requires commercial interfaces to display "MiniMax-H3-Image". US- or EU-based teams should clear licensing before self-hosting.

What a 1K, 2K and 4K image costs: MiniMax example math

All figures below are MiniMax-provided example costs, not fixed prices: billing is token-based, so your prompt length and reference count move the total. The examples assume 1K reference images where refs are involved.

TaskStandard exampleHighspeed example
T2I 1K area$0.02179$0.03529
T2I 2K area$0.02333$0.03622
T2I 4K area$0.06879 ($0.03439 promo)$0.13001 ($0.06501 promo)
Edit 4K + 1 ref$0.07312 ($0.03656 promo)$0.13673 ($0.06837 promo)
Edit 4K + 3 refs$0.07914 ($0.03957 promo)$0.15407 ($0.07703 promo)

Three things save money. First, 2K costs almost the same as 1K ($0.02333 vs $0.02179) for 4x the target pixels — order 2K over 1K when either works. Second, 4K carries 16x the pixels of 1K at roughly 3.2x the example price, so native 4K is efficient when you need print detail. Third, the launch promo halves qualifying 4K to $0.03439 standard until November 17, 2026 at 16:00 UTC, for outputs with at least 16,600,000 pixels.

Highspeed roughly doubles image-token rates for 3–7 seconds saved. At 4K T2I that is $0.13001 vs $0.06879 (1.89x). Unless you batch catalog renders against a latency SLO, Standard wins. Each extra reference adds input-image tokens, so a 3-ref 4K edit costs about 8% more than a 1-ref edit before quality is even considered.

Should your API call go here, or to Qwen, Krea or H3 video?

If your workload is bulk text-to-image at high resolution, H3-Image is attractive on MiniMax's published price and latency examples. If it is identity preservation, benchmark the alternatives below before committing.

Use casePickWhy
Bulk T2I posters, backgrounds, 4K landscapesH3-Image Standard$0.023 for 2K, $0.069 for 4K examples; fastest 4K in MiniMax chart
Latency-sensitive batch (ads, live previews)H3-Image Highspeed7.7s at 1K to 10.3s at 4K; pay 1.9x to save ~6s
Multi-reference character / product consistencyQwen Image via Alibaba Cloud or H3 video ref2iLinked threads report H3-Image weaker than QI 2.1 for multi-ref edits; several users keep H3 video for ref2i
Managed editing UI rather than API/self-hostingKreaNo ~135 GB local footprint; a UI alternative, not an API equivalent
Self-host on 24GB or lessWait for pruned/INT4 buildsBF16 needs datacenter-class VRAM today

When likeness matters, a cheaper per-image example price evaporates in retries.

Shipping checklist that avoids blurry bills

  • Start from 1K/2K presets and scale to 4K only for keepers; testers report soft default 4K, so verify sharpness at 2K first.
  • Log revised_prompt every run and diff it against your submitted prompt before changing anything else.
  • Allow client timeouts above 600s (the server may take up to 600s), disable SDK auto-retries, track a client-side dedupe key for reconciliation only, and on async providers poll the job instead of re-POSTing.
  • Handle per-image data[].error entries inside HTTP 200 multi-output batches; check the edits reference for the error envelope before you code the loop.
  • Confirm license, response_format, and prompt downloads: per the API docs, url responses are not guaranteed durable storage.

MiniMax H3-Image API FAQ

What is the difference between MiniMax H3-Image and MiniMax H3?

H3 is the video model; H3-Image is the still-image model built on it for text-to-image and editing at 4K-class areas. For reference-to-image consistency, several users in the linked threads still prefer H3 video.

What is the official endpoint and model ID?

POST https://api.minimax.io/v1/images/generations with model: MiniMax-H3-Image or MiniMax-H3-Image-Highspeed, plus /v1/images/edits and H3-Image-Context-IR for prompt expansion.

Can I disable prompt enhancement?

For text-to-image yes (disable_prompt_enhanced: true); for editing no. The API returns the rewritten prompt it used.

Can I run H3-Image locally on a consumer GPU?

Only with quantization and patience: ~135 GB in BF16 before the prompt-expander. The model card names H200, RTX PRO 6000 and MI350X-class accelerators for server recipes.

Is it commercially usable?

Only after clearing the MiniMax-H3-Image Community License: default grant excludes the US, EU, UK and Korea, and needs authorization above $1M revenue or for hosted third-party services.