MiniMax H3 benchmarks local runs on RTX 3060 to 5090 GPUs

• Local MiniMax H3 runs are already spread across consumer GPUs: a 3060 setup took about an hour for a 10-second 0.9MP clip in irmemon225's 3060 post, while a 5090 produced a 15.1-second clip in 84 seconds in ItchyNothing7646's 5090 post.
• RAM can be the choke point before VRAM: in Obvious_Set5239's edit test, 64GB RAM hit almost 100% usage while a 3060 12GB handled 0.35MP reference-video editing.
• The strongest creator pattern is scripted shot control: lazyspock's South Park prompt specifies exact identity hierarchy, camera cuts, voices, and nine timed taps.
• The weak spots are motion, action, and retries: Best_Candidate_9060's creature test called out unnatural fire, off creature motion, and lost continuity, while egeberkina said only about 1 in 4 or 5 runs really nailed the result.
• H3 is being treated as a local-model milestone because community testers were already sharing open-weight runs four days in, as kaigani put it, but the official MiniMax H3 model card says full 2K validation still combines the API with locally deployed H3-Base.

The MiniMax H3 model card lists 4 to 15 second outputs, 24 FPS video, 32 kHz stereo audio, and a local H3-Base path for 768p validation. The same spec says Ref2VA can take up to 9 images, up to 3 videos, and up to 3 audio clips, capped at 12 files total. A RunComfy Ref2VA workflow wraps H3 with a 4-step Turbo LoRA, while ComfyUI Wiki says that LoRA is an early FL2V preview and Ref2V distillation is still on the roadmap.

MiniMax describes H3 as an omni-modal system with three pieces: H3-Context-IR, H3-Base, and H3-Regenerate-2K. The local release covers H3-Base checkpoints for FL2VA and Ref2VA, while the model card says H3-Context-IR is hosted and H3-Regenerate-2K is not yet open-sourced.

The official local caveat matters because the community screenshots are mostly H3-Base experimentation, not the full hosted pipeline. MiniMax says local H3-Base validates 768p output, and the full 2K workflow uses the Open Platform API with locally deployed H3-Base.

The open release still unlocked a real weekend of tinkering. kaigani called the first four days of H3 development “unreal,” and gokayfem described H3 as open-weights, controllable, and fast on fal for 768p generations.

The useful numbers came from messy field reports, not a clean benchmark table.

• RTX 3060 12GB, 16GB RAM: 0.9MP, 10 seconds, 25 steps, Sage Attn plus Spectrum, no Turbo LoRA, about 1 hour in irmemon225's post.
• RTX 3060 12GB, 64GB RAM: 0.35MP, 5 seconds, 4 steps, 0.25MP reference video, roughly 100 seconds per iteration in Obvious_Set5239's post.
• RTX 5060 Ti 16GB, 48GB RAM: 9:16, 0.6MP, 5 seconds, Turbo v4 600 LoRA, Euler beta, 8 steps, about 2 minutes per clip in Fabulous-Snow4366's character test.
• RTX 4070 Ti: 15-second text-to-video POV dragon flight in ajrss2009's post, with no runtime listed.
• RTX 5080: 832x480, 15 seconds, 8 steps, fl2va pruned int8, int8 VAE, GGUF q4 K M text encoder, 210 seconds in PensionNew1814's post.
• RTX 5090: 15.1 seconds, 16:9 sitcom prompt, 84 seconds in ItchyNothing7646's post.

The 3060 reports are the more interesting floor. One creator waited an hour and still called the result worth it, while another hit a RAM ceiling during video editing even with 64GB installed.

Turbo is already changing iteration speed, but the early 4-step path has rough edges.

ComfyUI Wiki says the Lightx2v and ModelTC LoRA distills H3 FL2V from roughly 20 sampling steps to 4, with Ref2V distillation still planned. That lines up with Niko3dx's question about 4-step Ref2VA producing a mess while image-to-video worked fine.

Reference handling also showed weird failure modes. In Obvious_Set5239's edit test, a Pikachu reference image pushed the generation toward the reference image location instead of the source video, and removing the reference image improved the run while creating a Rick-in-a-Pikachu-costume problem.

The H3 prompt style circulating through Reddit reads like a shooting script with audio direction attached.

Creators are writing prompts with:

• shot numbers and timecodes, as in ItchyNothing7646's sitcom scene;
• exact voice labels and dialogue lines, as in Fabulous-Snow4366's Brad Pitt test;
• identity rules and visual hierarchy, as in lazyspock's South Park crossover;
• continuous camera motion, banking, motion blur, and soundscape notes, as in ajrss2009's dragon-flight prompt;
• scene-level continuity instructions, as in irmemon225's minimarket Ref2V prompt.

The South Park example is the nerdiest prompt in the batch. It specifies that the Big Bang Theory identities should control faces, South Park should control animation language, and Sheldon should deliver exactly three groups of three taps before each “Penny?” line.

Music-video creators are treating H3 as a clip generator inside a larger editing stack.

For “Feral Couture,” ai_artworkgen described this Hailuo H3 workflow:

• split the Suno track into 15-second segments;
• upload a character sheet;
• upload one 15-second audio clip;
• add up to 7 environment reference images;
• use @ references at the beginning so prompt text can point to assets;
• direct camera cuts and character attitude in the prompt;
• edit the best parts in CapCut;
• recut lyrics and rerun segments when a 15-second cut lands badly.

ai_artworkgen's full thread credits Midjourney, Nano Banana Pro, GPT-2 via Magnific, Hailuo H3, Suno, and CapCut in one pipeline.

Reference audio also showed up in character replacement. ozansihay used a personal character reference and a Breaking Bad scene, then asked H3 to replace Jesse, translate the scene into Turkish, and write the dialogue.

H3 can make polished frames before movement exposes the seams.

In Best_Candidate_9060's 15-second test, the character, materials, and static shots held up, but fire behavior, creature motion, and shot continuity broke down once the scene moved. Artedeingenio put the same limit bluntly: too much action makes H3 struggle, while simpler animation can look stunning.

Consistency still takes retries. egeberkina estimated that only 1 out of every 4 or 5 tries really nailed the intended look, with the rest drifting into different-looking characters.

That failure mode explains why reference-heavy workflows keep falling back to editorial assembly. Creators are generating sections, picking the best moments, and stitching rather than expecting one perfect pass.

The H3 comparisons were less about leaderboard scores and more about taste, motion, and cost.

GlennHasABeard's split-screen test put MiniMax H3 beside Seedance 2.5 on a transforming-machine prompt. In the replies, GlennHasABeard said H3 handled the machine physics better, and another reply from GlennHasABeard said H3’s camera quality almost felt like an 80s movie.

Other creators framed the split by use case. gokayfem put H3 in the open-weight, controllable, fast local bucket, while assigning Seedance 2.5 to long-term generation with lots of references. BLVCKLIGHTai compared the same 30-second prompt against Seedance 2.5 and said he would specify H3’s dialogue more tightly on a rerun.

The creator spread quickly moved past parody sitcoms.

stevibe used MiniMax H3 for an Apple-style scrolling product page background video and Codex for the page, then shared the product-film prompt with a 10-second unbroken camera move through a late-1990s ATX tower.

H3 also became a small VFX toy box: awesome_visuals made a cinematic wolf reveal, GlennHasABeard posted an artificial-gravity coffee test, and another GlennHasABeard test tried first-person teleportation.

The oddest practical use came from CommunicationFit3862, who called H3 a boon for making parody bumpers for a Plex server. Personal Sora is a little much, but local video models are now making personal media-server filler.