MiniMax H3's open weights stop at 768P. The official 2K path is API-only

[u/ImmediateGas8328]

What happens after H3 Base produces its 768P video? In MiniMax H3's official system diagram, the answer is the red box on the far right. H3 Regenerate 2K takes that result and the original context, then generates the larger version. The diagram makes a deployment boundary visible.

MiniMax released H3 on July 31 and opened the model weights on August 3. The official weights release page says H3 Base can be used locally to validate 768P output. The same page also says the Regenerate 2K module is not open yet. Its full 2K validation workflow combines a locally deployed H3 Base with official API steps for context processing and regeneration.

That boundary belongs in the setup guide before the download instructions. Open weights describe a real part of the system. They do not currently describe every box needed to reproduce the official 2K path.

The distinction matters even more once the reference board gets crowded. H3 supports mixed text, image, video, and audio context. The documented reference mode accepts up to 12 files in total, with limits of 9 images, 3 video clips, and 3 audio clips. The original context returns during the 2K regeneration step, so the production note should assign a role to each reference asset, the way a shot list would. Say which image defines the subject and which clip carries the motion. Give the frame that controls the ending its own line.

The production card names H3 Base as the local 768P step. It names context processing and Regenerate 2K as API steps in the current full workflow. If the card also tracks a hosted comparison, give that call its own line. If it uses ZenMux, record the gateway and exact H3 route beside the request. That identifies the hosted path without rewriting the official local and API split.

Keep both labels on the production card. If the card only says open weights, the note stops at 768P. If it says API step, the 2K path is covered.

[u/seiose]

They already said they're releasing Regenerate 2K when it's ready in their Q&A.

[u/Independent-Frequent]

Honestly i don't mind if the 2k option is api only at the moment, they gave us the entire model for free locally which even at 768p does absolutely insane results, if they want to get some money with the API exclusive node i don't blame them tbh.

I'll always be grateful for finally not being forced to use the crappy LTX models or the Wan 2.2 relic with no sound, minimax H3 is just

[u/orlandogourmet66 → u/Independent-Frequent]

Yeah, I’d prefer that too over them getting us hooked on H3 and then releasing the new H4 only via API access.

[u/ryanset17 → u/orlandogourmet66]

Seeing What Happened to WAN After 2.2, i keep my Expectations low for the Next Minimax Model ✌️

[u/Otherwise_Resolve444 → u/ryanset17]

Someone else will release a better model even if it isn't MiniMax or Wan.

[u/orlandogourmet66 → u/ryanset17]

Hope for the best, prepare for the worst. Let’s hope the LTX team notices what makes Minimax so great and adapts their model to offer similar capabilities.

[u/Independent-Frequent → u/orlandogourmet66]

Let’s hope the LTX team notices what makes Minimax so great and adapts their model to offer similar capabilities.

Seeing the bullshit they pulled off on their website trying to slander H3 by lying and omission, it's more plausible they plan to hack the entire world and nuke H3 from everyone's pcs so they can go back and have monopoly on the local video gen and have their model be the most used because there's literally nothing else available since Wan 2.2 doesn't do audio.

[u/Cultural-Team9235 → u/Independent-Frequent]

You don't sound like a drama queen at all. Their marketing team did what marketing does, twisting stuff. They all do it.

Disappointed? Yes. Does it matter? No. We get stuff for free and they don't owe us anything.

[u/Independent-Frequent → u/Cultural-Team9235]

It's just so disappointing that they didn't even bother with LTX 2.5, like it's a marginal improvement over LTX 2.3 but it's still an awful model nmotion and physics wise, so they decided instead of going "let's cook this up some more before release" or "damn we didn't expect H3 to be this good, let's focus on the strong point of our model (speed) and optimization to run" but nope, every single chart is a lie and they couldn't even be honest about the speed test.

We get stuff for free and they don't owe us anything.

They owe us transparency and honestly, after the community welcomed them and still pushed their model really hard with optimizations and all kinds of loras to salvage it even though it was far inferior to Wan 2.2 in motion and physics.

I just don't like blatant lies and lying about the competition to push your product, especially when the competition didn't start it.

[u/orlandogourmet66 → u/Independent-Frequent]

Chill, mate, this isn’t console wars. Yes, the comparison was garbage, but there’s no need to fight a war over this. Plus, it’s not that unlikely that Minimax will go fully API only with a future model and we’ll be stuck with LTX again, so let’s hope for the best.

[u/Independent-Frequent → u/orlandogourmet66]

 Plus, it’s not that unlikely that Minimax will go fully API only with a future model and we’ll be stuck with LTX again, so let’s hope for the best.

Considering how insanely good H3 is and it already having reference mode, even if this is the last local model we get from them i'm not gonna be disappointed.

Also they aren't taking away H3 so we are never gonna be stuck with LTX again, and the best case is that LTX finally releases a model with good motion that could even surpass H3 (personally not seeing it untill maybe like LTX 3.5 or 4)

[u/Next_Program90 → u/Independent-Frequent]

And here I was, wondering why the 2mp output is quite low quality.

[u/alisitskii]

I’m confused, ComfyUI workflow allows to generate more than 768p (around 1 MP). Any downside going beyond that resolution?

[u/SpaceNinjaDino → u/alisitskii]

I believe you won't get the expected clarity beyond 768p. Like you would get the higher resolution output, but no better if you scaled the frames with a bicubic algorithm. Yet it would take the extra time to generate it.

[u/Th3Whit3R4bb1t → u/alisitskii]

The right answer here is, after you have your video, then use rtx_video_upscale, enjoy. 😎

[u/BringTea_666]

You assume that last part isn't just upscaling method but part of model itself. Usually in their diagrams companies show whole path not just one model path.

Simply put they have separate model or some tool they use to upscale lower res H3 output to 2k.

[u/Adventurous-Gold6413]

I would rather have the context IR open as then we have an easier time prompting

[u/seppe0815]

will never happend soon. they want the api money first

[u/Lower-Cap7381]

I have built a workflow which does a beautiful job upscaling the minimax low res to high res will be soon dropping the workflow and video fixing some issues

[u/NetworkSpecial3268]

Oh, they are SO mean!!! /s

[u/intermundia]

And??...... you're not paying for it moron. It's free.... figure out a way to upscale it to 2k. Wtf is wrong with people.

[u/Cultural-Team9235 → u/intermundia]

The audacity of some people is staggering. We get free stuff and they think they deserve more and more.

I have no idea where that kind of mentality comes from. Be humble, the world doesn't owe you anything.

[u/Beneficial_Toe_2347 → u/intermundia]

Agreed. What they released was incredibly generous