Skip to main content
MiniMax H3 is governed by the MiniMax H3 Community License Agreement. As of the license revision reviewed on August 26, 2026, the United States, European Union, United Kingdom, and South Korea are Excluded Territories and require a separate license. Review the current agreement before downloading, deploying, or offering a hosted service.
MiniMax H3-Base jointly generates 768p video and synchronized stereo audio. This page provides two distinct paths: a visual local workflow with ComfyUI and a self-hosted API service with SGLang on NVIDIA data-center GPUs.

Status and scope

The pinned commits make the commands repeatable, but this remains an experimental integration rather than a stable SGLang release contract. Revalidate the page before changing either revision.
The open release contains H3-Base FL2VA and Ref2VA. It does not contain H3-Context-IR or H3-Regenerate-2K. A self-hosted H3-Base service therefore does not reproduce the complete MiniMax Platform Context-IR and 2K workflow.

Choose a deployment path

Use ComfyUI when you want to create and adjust a workflow visually on a local workstation. Use SGLang when you need an HTTP service, repeatable server configuration, or application integration.

Run H3 locally with ComfyUI

ComfyUI natively provides MiniMax H3 nodes and example templates. It is the lower-friction path for trying T2V, I2V, and reference-driven workflows without operating an inference API.
The ComfyUI templates use pruned and quantized files from Comfy-Org/MiniMax-H3, including INT8/NVFP4 components. They are different artifacts from the official mixed BF16/FP32 H3 checkpoint used by the SGLang baseline. Output quality, memory use, and reproducibility can differ; do not mix benchmark claims between the two paths.

ComfyUI baseline

The version and revisions above record the documentation baseline reviewed on August 26, 2026. The Template Library can evolve after that date.

Quickstart in the Template Library

  1. Update ComfyUI to version 0.30.0 or later and start it normally.
  2. Open Template Library > Video.
  3. Select MiniMax H3 T2V, MiniMax H3 I2V, or MiniMax H3 R2V.
  4. Follow the model-scan pop-up to download the required files. Restart ComfyUI if the model list does not refresh.
  5. Set the prompt and any input image, video, or audio references.
  6. In Resolution Selector, use 0.98 megapixels with a multiple of 32, or set 1344 ร— 768 directly for a 16:9 native canvas. Do not use the 1.0 megapixel step: it resolves to 1376 ร— 768, above the H3-Base 768 ร— 1344 pixel-area limit.
  7. Queue the workflow. The result should be an MP4 containing a 24 FPS video stream and synchronized stereo audio.

Choose a workflow

T2V and I2V use the FL2VA diffusion model. R2V requires the separate Ref2VA diffusion model; the two files are not interchangeable. In an R2V prompt, refer to inputs in connection order with tags such as <Picture 1>, <Video 1>, and <Audio 1>, then state which reference controls identity, style, motion, camera, or voice.

Manual model placement

The Template Library download flow is recommended. For an offline or manually managed installation, download the files listed by the selected template from the Comfy-Org model repository and place them as follows: For a reproducible team workflow, export the workflow JSON and record the ComfyUI version plus every model-file revision. Do not silently replace the FL2VA model with Ref2VA weights or enable a Turbo LoRA without recording the quality change.

Resolution, duration, and Turbo mode

  • H3-Base uses a 768-pixel short edge and dimensions aligned to a multiple of 32; 1344 ร— 768 is the native 16:9 canvas.
  • Duration snaps to the modelโ€™s 17k + 5 frame grid at 24 FPS. A requested duration can therefore be adjusted to a valid frame count.
  • The example FL2VA workflow uses 20 steps by default. Its optional 8-step Turbo LoRA is faster but can reduce motion and audio quality.
  • The R2V workflow uses a separate optional 4-step Turbo LoRA. Record the LoRA name, strength, steps, seed, and all references when comparing results.
ComfyUI also exposes advanced H3 workflows such as arbitrary-frame guides through MiniMaxH3AddGuide, prompt embeddings, and latent noise masks for inpainting or extension. These features and optional Sage Attention acceleration evolve with ComfyUI; follow the official MiniMax H3 ComfyUI guide before using them in a pinned production workflow.

SGLang hardware and environment

The 8 ร— B200 topology below is a reference configuration, not a minimum-hardware claim. The current MiniMax model card demonstrates a four-GPU SGLang command but does not name the GPU model or publish peak VRAM, host RAM, disk, interconnect, driver, CUDA, or latency measurements for that command. Install git, curl, jq, ffmpeg, a compatible NVIDIA driver, and the CUDA runtime before continuing. Do not interpret an unpublished requirement as no requirement.

SGLang Quickstart

The following flow downloads only the FL2VA partition, starts a loopback-only service, waits for readiness, submits a job, polls it, downloads the MP4, and inspects its streams.

1. Install the pinned SGLang source

This commit pin replaces the mutable main, dev, or unversioned prerelease installation commonly used during early H3 support.

2. Download the pinned FL2VA checkpoint

Keep the repository root as --model-path; do not point SGLang at the FL2VA/ subdirectory. SGLang selects it through --model-variant fl2va.

3. Start the FL2VA service

Run this command from the SGLang repository with the virtual environment active:
Keep this process running. The first startup loads the model and performs warmup, so readiness can take several minutes.

4. Check readiness

In a second terminal:
A ready service returns:
/liveness only proves that the HTTP process is accepting requests. Use /health, which returns HTTP 503 until model warmup is complete.

5. Generate, poll, and download an MP4

The expected result is a non-empty MP4 with one H.264 video stream at 24 FPS and one AAC stereo audio stream at 32 kHz. The 16:9, 768-short-edge profile resolves to 1344 ร— 768 and approximately 5 seconds.

Capability and checkpoint matrix

H3-Base output is 4โ€“15 seconds, with a 768-pixel short edge, 24 FPS video, and 32 kHz stereo audio. Ref2VA accepts up to 9 images, up to 3 video clips, and up to 3 audio clips; see the model card for per-file and combined limits. To serve Ref2VA, download "Ref2VA/*" at the same pinned model revision and start a second service with --model-variant ref2va on another port. Do not reuse an FL2VA server for ref2va requests.

SGLang hardware and performance data

Only compare numbers collected with the same checkpoint, request shape, inference steps, flow shifts, and quality level. Consumer GPU, offload, quantization, AMD, and multi-node recipes evolve independently. Treat them as SGLang upstream configurations, not as MiniMax-verified hardware, until a MiniMax test matrix is published.

SGLang weights, cache, and offline deployment

  • The official Hugging Face repository is MiniMaxAI/MiniMax-H3. The default cache root is ~/.cache/huggingface; this page overrides it with HF_HOME.
  • The mainland China mirror is MiniMax/MiniMax-H3. Revision parity with the pinned Hugging Face commit has not been documented, so it is not used for the reproducible baseline.
  • For an air-gapped host, run the pinned hf download command on a connected machine, transfer the complete model directory, and verify that model_index.json plus the selected FL2VA/ or Ref2VA/ directory are present. Start SGLang with HF_HUB_OFFLINE=1.
  • Interrupted Hugging Face downloads are resumable. Re-run the same command with the same revision. If a cached file is corrupt, use hf download --force-download for that pinned revision rather than switching revisions silently.
  • Do not download both checkpoint partitions unless the deployment serves both; each partition is an independent service.

SGLang production and security

The Quickstart listens on 127.0.0.1 and provides no public ingress. To expose a service:
  • Put it behind an authenticated reverse proxy or API gateway; require an API key or equivalent identity control.
  • Terminate TLS at the ingress and restrict the backend port with a firewall, security group, or private network.
  • Apply request quotas, concurrent-job limits, output retention, audit logging, and abuse controls required by the H3 license.
  • Mount server-local reference media read-only and allow only dedicated directories. Do not expose arbitrary filesystem paths.
  • If an ingress downloads remote image, video, or audio URLs, enforce a domain allowlist, redirect limit, connection/read timeout, maximum bytes, decoded image dimensions, and media duration before passing a local file to SGLang.
Only after those controls are in place should you change the server to --host 0.0.0.0. SGLang support does not itself provide the safeguards required by the model license.

SGLang troubleshooting

License and system boundary

The MiniMax H3 Community License Agreement contains territory, commercial-use, distribution, attribution, hosted-service safeguard, and Acceptable Use Policy terms. The license can change; the linked text is authoritative. For the model card, reproducible examples, prompt guidance, and license Q&A, see the MiniMaxAI/MiniMax-H3 repository. For advanced hardware, precision, placement, and performance options, see the SGLang MiniMax-H3 Cookbook.