MiniMax H3 - INT4 ConvRot Edition
This is a complete INT4 ConvRot conversion of the original MiniMax H3 model files. The conversion preserves the original model architecture and capabilities while storing its weights at substantially lower precision, making the model easier to run on systems with limited GPU memory.
INT4 ConvRot model
Much smaller model weights
Lower RAM and VRAM usage
Reduced memory-transfer requirements
May load and run faster on compatible hardware
Can introduce small quality differences compared with the original full-precision model
Hugging Face (mirror) - https://huggingface.co/Merserk/MiniMax-H3-INT4-ConvRot
Patreon (support): https://www.patreon.com/mm744
Description
FAQ
Comments (17)
Anyone know if this is safe?
It's safetensors, there is literally nothing that it can execute by itself. At worst, it's not the model that it claims to be and that is fairly simple to ascertain in one run (assuming comfy also supports int4 natively, I don't recall).
This site is more dangerous than a safetensors: https://github.com/civitai/civitai/issues/3434
The file sizes don't match the Comfy-Org models. I would grab it from the HF instead. https://huggingface.co/Comfy-Org/MiniMax-H3/tree/main/diffusion_models
These are INT4 ConvRot models, converted for faster performance and lower VRAM usage.
@MM744 Fair enough.
Safe it is , but I would not expect quality. Better to grab from https://huggingface.co/Comfy-Org/MiniMax-H3/tree/main/diffusion_models even if it does not fit your VRAM, get the INT8 pruned version. Only get INT4 or NVFP4 if you prepare yourself for disappointment first.
@MM744 I think he meant to ask if it's safe for work, is nsfw! hahah
Can somebody create a minimax h3 workflow for 12gb +16gb ram lowvram specs
its not the workflow the model its self is to big. may use purge vram v2 use it before and after the sampler
it doesn't work for me, it gave me a messy blurry broken video result.
If used, the generated video looks like a Van Gogh work
sorry, tried out t2v, i2v, different resolutions and it looks like s**t like have already said. There might be a separate workflow, but without information: save yourself the download.
there is no way you're gonna get any quality out of these, far too quantized.
Poor quality (too noisy outputs), as always from you
12GB VRAM + 32 RAM = normal at int8 checkpoint)
In fact, H3 needs RAM more than VRAM. The int8 version can even generate 0.5MP, 24fps, 5s in 5 minutes on my setup with 8GB VRAM + 32GB RAM (4060M + DDR5). However, it requires some effort—for example, running it on a Linux environment with no other software open to free up memory. Windows is too bloated. It roughly needs 28GB RAM and 6GB VRAM. My recommended sweet spot parameters are 0.35MP, which can be completed in 3 minutes.
So, go ahead and try int 8! Even at 0.5MP, pushing it up to 10s won't cause OOM, and RAM and VRAM remain basically unchanged, but the time expands to 15 minutes.
Same device reference, wan2.2 at 0.5MP, 20FPS, 4s requires 10 minutes of generation time, and the jelly effect is severe. Open source is so wonderful!
By the way, H3 doesn't need to stack various LoRAs to perform conventional NSFW actions well (I can't think of any unconventional ones). It's both fast and effective.