MiniMax H3 Regenerate to 2K

MiniMax H3 will happily generate straight to 2K, but 2K is the pricey end of its pricing. A smart workflow is to rough out your idea at 768P - cheaper, faster, and if the shot's wrong you've wasted less - and only commit to the high-res pass once you've got a keeper. That's exactly what this node is for. You feed it the 768P output you like and it re-renders that specific video at 2K on MiniMax's servers, instead of making you regenerate from scratch and hope the dice roll the same way.

The mechanism matters, so let's be precise about it: this is not an upscaler. Nothing is running on your GPU. Comfy uploads your source video (tagged as the base_video), together with the exact prompt that produced it, to the H3 regeneration endpoint, polls the job, and downloads the result. The model uses your original clip as the base and re-renders it at 2K, which is why you'll get the same content, sharper - not a fresh random generation.

The inputs that matter

• model → prompt - the exact prompt used to generate the source video. This one's required and not a suggestion. Drift here and the re-render can wander.
• model → resolution - locked to 2K. That's the whole point.
• model → reference_images / reference_videos / reference_audios - re-attach whatever media the original generation used, in the same order, if it used any.
• video - the unmodified 768P output from a MiniMax H3 video node.
• first_frame / last_frame - the same frames from the original run, if you used them. Mutually exclusive with reference media.
• watermark - whether to stamp an AIGC watermark on the 2K output. Defaults to off.

The trap: the source has to be untouched

This node validates your source harder than most, because it has to be a genuine H3 768P output for the re-render to work. Specifically: 24 FPS, dimensions divisible by 32 and at most 1,032,192 pixels (that's the ~1344×768 that 768P actually outputs), and a frame count of 107 to 362 in steps of 17 - i.e. 4 to 15 seconds at 24 FPS.

What that means in practice:

• Don't re-encode, re-cut, or run it through any video processing node first. Even a benign trim shifts the frame count off the allowed steps and the node rejects it.
• Don't try to feed a 2K output back in - the node explicitly refuses. It's a one-way door from 768P.
• Frames vs. reference media is an either/or, same as elsewhere in the H3 family.

These checks are friendly errors that tell you exactly what's wrong, but they're also a hint about how this whole category of node works: the source of truth is MiniMax's API contract, and Comfy is just the wrapper that polices it.

Getting it and the honest take

It ships with ComfyUI core - no install, no Manager, no git clone. It's part of the H3 node family that landed mid-2026, so update ComfyUI if you don't see it. It's an API node, so you'll be signed into your Comfy account with credits; pricing is per second of output, billed through Comfy, so a 15-second 2K re-render costs meaningfully more than the 768P original.

Is it worth it? For a clip you're actually going to use - yes. The alternative, regenerating at 2K from scratch, burns credits and gives you a different video. This gets you the same shot at higher resolution, which for anything client-facing or destined for a montage is exactly what you want. Just keep the source pipeline clean.