MiniMax H3's Early Local Runs: Settings Before Speed
IMAGE, VIDEO & AUDIO
MiniMax H3's Early Local Runs: Settings Before Speed
Early H3 reports mix different GPUs, resolutions and step counts. They are useful for finding configurations to try, but do not form a controlled speed ranking. This roundup keeps those reports separate from the narrow 1080 Ti observation and the hosted service's capabilities.
In this article
This roundup records community reports from the first three days after release: GPU timings, output impressions and the license terms that accompanied the weights. Those reports use different prompts and settings, so the timing table is not a controlled GPU benchmark.
Model and service specifications
| Item | Details |
|---|---|
| Announcement / weights | 2026.07.31 announced → 2026.08.03 on Hugging Face |
| Architecture | 33.1B dense omni-transformer (13B is the AdaLN branch — skippable at inference) |
| Input | Text · image · video · audio unified (up to 9 reference images + 3 videos + 3 audio) |
| Output | Up to 15s · 24fps · 768p (local) / 2K (API) · native stereo audio |
| Text encoder | Qwen3VL-32B (51.5GB bf16 — the size culprit; the int4 version at 15.7GB solves it) |
| Minimum local setup | pruned int8 combo at 42.5GB (full bf16 is 123.6GB) |
| License | MiniMax H3 Community License — excludes EU, UK, US, and South Korea!! (see #6) |
video and audio are generated in the same pass. A character video with dialogue isn't "motion only, add voice later" — lip-sync, voice, and SFX all come out at once.
Early community impressions
Reactions poured into Reddit within a day of release. Highlights only:
This is insane. After using it, Wan 2.2 feels like ancient technology.— r/StableDiffusion, 56 pts
Still testing via API and it's ridiculously strong. Wan 2.2 looks like ChatGPT 1.0 next to it. The fact that this runs on consumer hardware is a game changer.— r/StableDiffusion, 51 pts
Just swapped a character out of a movie clip. No LoRA, default settings. WTF.— r/StableDiffusion, 18 pts
A single plain paragraph nails even physics effects in one shot. The prompt comprehension is insane and the output is stunning. This is a game changer.— r/StableDiffusion
Eye direction and facial expressions tracked almost perfectly. Slight plastic feel, but it's a very minor thing.— r/StableDiffusion, after first test
Selected community reports praised prompt adherence and local access, while others described long generation times. The LTX and H3 examples cited here use different resolutions, models and settings. They are leads for further testing, not a representative consensus or a controlled speed comparison.
Reported GPU timings and settings
Real measurements gathered from Reddit and Discord. Resolutions and step counts vary, so this isn't a clean comparison — use it to get a feel for "would my GPU even be worth trying."
| GPU | Settings | 5s clip time | Verdict |
|---|---|---|---|
| RTX 3050 8GB | 864×480, 32 steps | 15 min 24 s | It runs, technically |
| RTX 4060 Ti 8GB | 632×632, 20 steps | 5 min 29 s | "Faster than expected" |
| RTX 3090 24GB | 736×416, 10s clip | Under 7 min | Bearable |
| RTX 4090 | 480p-ish, 5s | ~100 s | Actually usable |
| RTX 5070 Ti 16GB | 720p, 20s (distill) | 4 min (for 20s) | Distill + tweaks |
| RTX 5090 32GB | 768×1376 (1K), 24 steps | 222 s | Worked on first try |
Some early workflows recommended 12GB VRAM, 32GB RAM and NVMe storage, and reported pinned-memory problems on 3060-class cards. These are configuration-specific reports, not a universal minimum. Check the current versioned workflow before copying a flag; the 11GB observation below uses a much smaller output setup.
⚡ I ran it too (GTX 1080Ti 11GB)
The recorded GTX 1080 Ti run used a 0.1MP, 16:9 ComfyUI setup and 20 steps for a five-second clip, taking about 14 minutes. A ten-step attempt was reported at seven to eight minutes. There was no controlled quality evaluation, so the shorter attempt should not be presented as equivalent output or as evidence about every low-VRAM card.
Output strengths and limitations
👍 The good
· Prompt adherence: "one plain paragraph, done in one shot" is a repeated verdict. Handles compound instructions (this image's character + this video's camera move + this audio's voice) in a single pass
· Reference-conditional generation (ref2va): many reports say character consistency is solid even without LoRA. Swapping a character inside a video clip works out of the box
· Native audio: lip-sync, dialogue, and SFX in one pass. No comparison to the old workflow (video and sound separately)
· Editing / motion transfer: #1 in Artificial Analysis video editing. Grabbing motion from a reference video is especially strong
👎 The not-so-good
Generation time depends on the workflow, step count, precision and offloading. The twenty-step examples here do not establish a fixed step requirement, and changing steps needs a separate quality check.
· Physics / anatomy errors: the surface quality is so high that "pretty but wrong" mistakes are more dangerous. Reported cases: a weirdly drawn heart diagram, a paper boat collapsing as it moves
· Local is capped at 768p: the marketing 2K is the API-only H3-Regenerate-2K pass. Local gets 768p as the base canvas
· The Qwen3VL-32B encoder: 51.5GB in bf16 — first time a text encoder has been this big. Grab the int4 version (15.7GB) instead
Launch API prices
Video generation bills per second. Here's the community price comparison under the same conditions.
Source: community price comparison (Seedance 2.5 $5.48 / Seedance 2 $2.99 / MiniMax H3 $1.45, per generation). MiniMax officially claims per-second pricing at 2K is under 1/3 of mainstream models.
Same model, full bf16 123.6GB → pruned int8 combo 42.5GB. ComfyUI's pruning (turning ~40% of modulation weights into a lookup table) plus int8 quantization achieves a 66% memory cut.
Weight-license conditions
Territory restrictions in the cited license
The MiniMax H3 Community License lists EU, UK, US, and South Korea as Excluded Territories. The gist: downloading the weights, local execution, modification, distribution, and even using the outputs are all outside the license grant in those regions.
So "it's open-weight, use it freely!" doesn't hold. For commercial use, even organizations under $20M annual revenue have an attribution obligation ("MiniMax H3" notice), and above that threshold you need separate approval. There's also a no-distillation clause.
The practical reality: there's no geo-block on Hugging Face, so downloads work. The international community's take is mostly "they can't really stop it," and MiniMax has opened a dedicated license-inquiry channel (QA docs). People are just running it for personal tests, but before any commercial project — contact MiniMax about the license first. This post is an information summary, not legal advice.
Local artifacts and workflow
| File | Size | Purpose |
|---|---|---|
| fl2va pruned int8 | 20.97 GB | text→video / image→video |
| ref2va pruned int8 | 20.97 GB | reference-based video (both = 63.4GB) |
| Qwen3VL-32B nvfp4 encoder | 15.69 GB | shared across all workflows |
| Video VAE + Audio VAE | 5.21 + 0.61 GB | video & audio decoding |
Warning: the full original repo (MiniMaxAI/MiniMax-H3) is 498GB. Grab only what you need from the Comfy-Org mirror. Native support in ComfyUI 0.30.0+ (Kijai merged it into core rather than a separate wrapper — workflow templates included).
What the early reports establish
"A turning point for open-weight video models" is the most accurate phrase. Quality approaches the closed-tier leaders, reference control (character, voice, camera) is arguably stronger, and it runs on a 42.5GB download + 12GB-class GPU. The mood right now: people who waited 20 minutes per Wan 2.2 clip last week asking "this got released for free?"
The early reports establish that low-VRAM experiments are possible with substantial compromises. They do not establish consistent quality, a fixed speed advantage or resolved usage rights. For the later 1080 Ti encoder experiment, see the measured ClipProj test; retain its narrower setup when reading the results.
Note: this is a community-impressions roundup from three days after release. No verified long-term evaluation exists yet. Flux 3's announcement the same day also split the spotlight.
Related on this blog: H3 Max: 5 Seconds of Video in Under 3 — and It's Not MiniMax's Model · MiniMax H3 went open-weight, so I did the math on whether my PC can run it
Comments
Post a Comment