Download
1 variant available
This checkpoint includes a config file, download and place it along side the checkpoint.
5500 1 2 3 4 5 6 7 8 90 1 2 3 4 5 6 7 8 90 1 2 3 4 5 6 7 8 9
(40)
Sep 2, 2026
MiniMax H3

300 1 2 3 4 5 6 7 8 90 1 2 3 4 5 6 7 8 9
970 1 2 3 4 5 6 7 8 90 1 2 3 4 5 6 7 8 9
MiniMax H3 is licensed by MiniMax under the MiniMax H3 Community License Agreement. That agreement’s Applicable Territory excludes the European Union, the United Kingdom, the Republic of Korea and the United States of America. Your use of H3 and of any H3 derivative is subject to that agreement and its Acceptable Use Policy.
MiniMax H3
Endless MiniMax H3 (with Endless LipSync) v1.0
When MiniMax H3 came out, I was badly missing the Endless Wan 2.2 I2V (SVI 2 Pro) features, so at first I look at other options, but most of them included an AIO node that could do everything, and I couldn't use most of my workflow, because they did everything inside that huge node. The only exception to this, was ComfyUI-H3-Motion-Context, which I could easily integrate into my setup. Its big shortcoming though, was that it just created single videos. No way to concatenate them without the lossy step of decoding and re-encoding in a video editor. So, I created a custom node that could do just that, and voila..
Endless MiniMax H3 (with Endless LipSync) v1.0 A simple workflow to create MiniMax H3 videos of unlimited duration, using ComfyUI-H3-Motion-Context and H3 Motion Context Clip Stitcher. I can easily create a 1:30 lip-synced video myself, with a RTX 3060 12GB at around 2 hours (with retries).
It can use both FL2AV and Ref2AV, and can also create normal MiniMax H3 videos. The extra parts though, are the saving/loading of the latent from every generation we do, and the stitching of all (or some) of them, whenever we want a full video. Nothing visible at the connections, no indication that there were more than one video. We can try and re-try every generation, looking for the best one, and then proceed to the next. We can re-do any previous generation if we like too, but we will not be able to use the clips after it (previous clips are not affected), because they are in a way, "fused" with the replaced one.
Controls
The RED nodes Enable/Disable parts of the workflow.
Generation Mode (select only one)
T2V / I2V (FL2VA)
REF2VA
Optimizations (select as many as you want, but only 1 Attention and/or only 1 Cache) This panel controls the nodes that are inside the
Optimizations/LoRAsubgraph.Reference Items (select as many as you want) Special usage for the
Audio 1 Forced/Multi, more for them later.Setup (select as many as you want depending on the goal)
Generate starts a generation. You don't need this if you just stitching clips
Preview enables the main video preview that can show you where the generation is going before it finishes, so you can stop bad generations
Use previous clip, uses the last part of the previous generation to start the current one, continuing the video. Enable it if you want the current generation to be stitched with the previous video
Stitch clips, stitches all the clips (depending on the Stitcher's settings) from the
h3_contextfolder (this is the default folder that the H3 Motion Context node uses to save the latents)Stitch last only, stitches only the last video with the current
Save Video just saves the generated video
The GREEN nodes are various settings nodes that must be setup. Apart from the Prompt, Seed and LoRA nodes, the most important are these:
Configuration It contains all the settings for the video. The most important setting for the clip stitching, is the Save to clip Index number. This specifies the clip file's number, that the latent of the current generation will be saved to (overwriting any previous existing file). This number also tells us who is the previous clip file that we use to start our current video clip.
Setup multiple Forced Audio clips This is used if we use our own audio for the video, and we want to also stitch many clips together. More about it in the Usage section.
Usage
Most of the settings are self explanatory (like Optimizations or enabling Reference items). Here, I will just list the main goals of the workflow
Create a normal video
Select Generation Mode
Enable Generate, Preview and Save Video
Save to clip Index to 1
You get a video and that's it.
Create a lip-synced video
Select Generation Mode
Enable Generate, Preview and Save Video
Enable <Audio 1> and load an audio file
Enable <Audio 1> Forced
You get a video that is lip-synced with the provided audio
Create an Endless video
Create a normal video
Enable Use previous clip
Save to clip Index to 2 and generate
Save to clip Index to 3 and generate
Save to clip Index to 4 and generate
...
You get many small videos, each one of them starts with the ending of the previous one. At a later time, you will use the Stitcher, to stitch them all together to one full video.
Create an Endless video, stitched
Enable Stitch clips With every generation, the Stitcher will stitch all the previous clips with the currently generated one. This way you always get the full video to check.
If you also enable Stitch last only, only the previous and the current videos are stitched together, so you can check the connection without waiting for the full video to be created. You can always stitch them all together at the end.
You get a full video every time, or just the last 2 videos connected, for previewing the connection.
Create an Endless lip-synced video, stitched
Create an Endless video
Enable <Audio 1> Forced and <Audio 1> Forced Multi
At the Setup multiple Forced Audio clips panel there are some settings.
Start offset: At the 1st gen, you put here the initial offset that you want for the song (e.g. where the lyrics start). After every successful generation (when you advance the Save to clip Index number), you must copy here the value that is in the
Copy to Next Start offsetbox.Frame offset (ignore if 1st clip): Never mind at 1st generation. After every successful generation (when you advance the Save to clip Index number), you must copy here the value that is in the
Copy to Next Frame offsetbox.context_length must be the same value everywhere (here, at the
Motion Context, and at theH3 Motion Context Clip Stitcher). It's the number of common frames the 2 video clips use to blend together.
You get a full lip-synced video every time, or just the last 2 videos connected, depending on the Stitch clips and Stitch last only settings.
Just stitch the clips together You just have to enable the Stitch clips and the Save Video All (or some of them depending on the settings), of the clips in the
h3_contextfolder, will be concatenated to a single full video.
Notes:
All generated clips that need to be stitched, must have the same dimensions.
You can organize past generations in folders inside the
h3_contextfolder, since all the nodes look only in the root of this folder for clips.context_length must have the same value everywhere: at the
Motion Context, at theH3 Motion Context Clip Stitcherand at theSetup multiple Forced Audio clips(if you are using it). It can can have only the values of 5, 22, 39, and 56.You can stitch together clips that are generated from either fl2va or ref2va.
In this workflow, I don't use the normal ref2va model in the
Reference to Videonode, but rather the fl2va with theref_lora_layer20-49adalnLoRA that has better quality. You can check some LoRAs with different weights here, or totally bypass the LoRA and use the normal ref2va model.
Models used:
Custom Nodes used:

