LightVAE accelerates the video autoencoder stage of MiniMax H3. It supplies smaller encoder and decoder components that retain the corresponding latent interface. It does not replace the main video diffusion model, and it does not compress H3's separate audio VAE.
The LightX2V announcement on October 14, 2026 points to open code, weights and ComfyUI workflows. On October 15, ComfyUI PR #17049 merged native recognition of H3 LightVAE components and separate encoder/decoder loading. This guide follows the published setup; we have not installed the workflows or benchmarked the models. H3Vid does not expose a LightVAE backend switch.
What changes in the H3 pipeline
An encoder turns reference pictures or footage into latent representations. A decoder turns generated video latents back into frames. Sampling the main video model sits between those stages. Faster decoding therefore helps most when decoding takes a meaningful share of your job.
The LightVAE paper describes temporal compression and quality recovery across supported video autoencoders. The released H3 Lite components use independent block pruning. Wan's Pro and Lite naming should not be copied onto H3 as if every backbone had the same available variants.
Keep checkpoints matched to their backbone. A file trained for Wan is not an H3 component merely because both repositories discuss video VAEs. The published H3 workflows also keep the original audio VAE, so sound decoding and video decoding remain separate choices.
Choose FL2V or reference-video wiring first
| Workflow | Encoder path | Decoder path |
|---|---|---|
| FL2V, including first/last pictures | Original H3 VAE | H3 Lite decoder |
| Ref2V with pictures | Original or H3 Lite encoder | Original or H3 Lite decoder |
| Ref2V with video and soundtrack | Original or H3 Lite encoder | Original or H3 Lite decoder; original audio VAE |
These are the author's supported graph distinctions. In the first/last-frame example, the original VAE feeds keyframe encoding directly. Replacing it everywhere because a smaller encoder exists would depart from that documented setup.
For reference inputs, changing encoder and decoder together changes two stages at once. Start with original encoding and Lite decoding, then evaluate the optional encoder separately. This makes it easier to locate a change in reference fidelity or reconstruction detail.
Install the documented adapter route
The ComfyUI installation guide provides an explicit installer. Use ComfyUI's own Python environment, and start from a version with native H3 support.
cd /path/to/ComfyUI
git clone https://github.com/ModelTC/LightVAE.git LightVAE
python LightVAE/comfyui/install.py --comfy-root .
python -m pip install huggingface_hub
hf download lightx2v/LightVAE \
lightvae-lite-h3-decoder.safetensors \
lightvae-lite-h3-encoder.safetensors \
--local-dir models/vae/LightVAE
The installer creates the custom-node adapter. Do not clone the complete LightVAE repository directly into custom_nodes. Retain the original H3 video VAE as the adapter's base component; its documented download is vae/minimax_h3_video_vae_fp16.safetensors from Comfy-Org/MiniMax-H3.
Restart ComfyUI. Connect the standard Load VAE output to Load H3 LightVAE.base_vae, then select the desired Lite components in the LightVAE node. In this adapter, none retains the corresponding original component. For FL2V, leave the encoder selection at none and keep original keyframe encoding wired as the example shows.
The newly merged native support changes what ComfyUI can recognize; it does not prove an older stable installation already has those changes. The installer workflow above is the documented adapter route, with its own node and wiring. Avoid mixing instructions for a native partial component loader with instructions that expect a complete base VAE.
Import a matching example
The author supplies separate first/last-frame, image-reference and video-reference graphs. Select your actual model files and upload your own inputs after importing one.
Their default examples use 1344×768, 124 frames at 24 fps, and twenty base-model steps. They are not four-step or eight-step Turbo recipes. First validate the provided model family and graph, then assess whether a separate accelerated sampler recipe remains compatible. A successful file load alone does not establish that an arbitrary combined optimization is correct.
Add the optional ConvRot-INT8 decoder
The model card lists lightvae-lite-h3-decoder-int8-convrot.safetensors. Update the adapter checkout, rerun its installer, download the file into the LightVAE VAE directory, and select it as the decoder. Keep the base VAE connected and preserve your existing encoder and audio paths.
This particular INT8 file is documented for ComfyUI. Use standard non-INT8 checkpoints with the standalone infer.py and benchmark.py programs. Native NVIDIA acceleration requires a CUDA 13.0-or-newer PyTorch build and a compatible driver; older builds may fall back to other operations. The checkpoint's smaller storage footprint does not establish a matching percentage reduction in job time or peak memory.
If an INT8 run is unexpectedly slow, record the actual PyTorch build and backend before changing the sampler. If reference appearance changes, compare original encoding with Lite decoding first. If audio changes, inspect the audio path: LightVAE's documented replacement is the video component.
Measure the stage you intend to improve
The repository's comparison protocol uses an H200, BF16, three 124-frame clips and warmup before timing. Reconstruction quality is measured before MP4 compression. Those conditions describe the authors' experiment, not a result on your GPU.
Keep sampling settings, reference inputs and output encoding fixed for your own evaluation. Record encoding, sampling, video decoding and total wall-clock time separately. Inspect fine texture, moving edges and reference identity as well as playback. An optional compact component is useful when it improves the stage that limits your workflow while retaining acceptable output.
For broader local setup, use the H3 ComfyUI guide. For an attention optimization, see Veda sparse attention. These affect different parts of the pipeline and need separate compatibility checks.
The cover is an AI-generated concept illustration, not a LightVAE reconstruction, software screenshot or MiniMax H3 test result.