MiniMax H3 Hugging Face:Official Repository Guide

Repository sizes can change as files and formats are updated. The total repository size is not the amount every user needs to download.

The canonical Hugging Face repository for MiniMax H3 is:

MiniMaxAI/MiniMax-H3

There is unusually strong primary-source evidence for this.

MiniMax's H3 Community License defines MiniMax H3 as the model and related materials publicly released by MiniMax at the MiniMaxAI/MiniMax-H3 Hugging Face repository. MiniMax also announced the H3 open release on August 3, 2026 and links its public model resources from official documentation.

The official repository contains the H3 model families plus shared components, documentation and framework resources.

MiniMaxAI/MiniMax-H3
├── FL2VA/
├── Ref2VA/
├── assets/
├── docs/
├── scripts/
├── processor/
├── scheduler/
├── audio_scheduler/
├── text_encoder/
├── tokenizer/
├── transformer/
├── transformer_ref/
├── vae/
├── audio_vae/
├── LICENSE
├── README.md
├── model_index.json
└── modular_model_index.json

This is a repository snapshot rather than a permanent file manifest. Always check the live Hugging Face repository before scripting downloads against individual paths.

MiniMax publishes two task-specialized H3-Base checkpoint families.

FL2VA and Ref2VA are separate task-specialized H3-Base checkpoint families, not simply two settings inside one identical checkpoint.

No. Most users should not download the entire MiniMax H3 Hugging Face repository.

The repository currently shows roughly 498 GB of hosted files, while the original FL2VA and Ref2VA task-family directories are each roughly 144 GB.

That does not mean every local H3 installation requires 498 GB.

The repository contains multiple model families, supporting components and framework-oriented representations. MiniMax's official README recommends scoping downloads to the task family and components required by your framework.

• • a user who only needs FL2VA does not necessarily need Ref2VA;
• • framework-specific workflows may need only a subset of the repository;
• • Diffusers can load required components through its supported model-loading workflow instead of manually mirroring every file.

498 GB repository size ≠ 498 GB required for every MiniMax H3 user.

Searching Hugging Face for “MiniMax H3” returns more than the original MiniMax repository. Some repositories repackage the model for another framework. Others quantize it, finetune it or distribute derivative files.

That does not make those projects invalid. It simply means they should not be described as the original MiniMax release.

Important distinction: Community model does not mean unsafe, fake or low quality. It means the repository is not the original MiniMax-published base release.

A Hugging Face repository containing “MiniMax H3” in its name is not automatically an official MiniMax release. Verify the publisher, MiniMax primary-source links and the repository's model relationship.

MiniMax H3 is distributed under the MiniMax H3 Community License Agreement, not a standard Apache 2.0 or MIT license.

The license includes conditions covering applicable territory, redistribution, acceptable use, commercial deployment and model derivatives.

MiniMax provides a separate licensing process for cases outside the standard license scope. This page is not a substitute for reviewing the current agreement before deployment.

This summary is informational and is not legal advice.

No—not as a fully local open-weight stack today.

The Hugging Face open release gives developers the public H3-Base FL2VA and Ref2VA checkpoints. MiniMax currently describes H3-Context-IR as a hosted preprocessing and orchestration system and H3-Regenerate-2K as not yet open-sourced. Its documented full 2K validation workflow combines locally deployed H3-Base with hosted MiniMax API stages.

Downloading MiniMax H3 from Hugging Face does not currently give you every component of MiniMax's complete official 2K pipeline.

For machine-readable research and model provenance, this page maintains a repository registry covering the official MiniMax H3 release and notable derivative repositories.

The registry records repository ID, publisher, official or community status, relationship to the original model, model family, format, primary use, base model, license and verification date. It excludes volatile download and like counts.

This guide prioritizes the original repository, MiniMax license documentation and the official release announcement when determining model provenance.

Verification method: We separate original publisher releases from community repacks, conversions, quantizations and finetuned derivatives. The community repositories named above were checked as provenance evidence but remain plain text to reduce unnecessary exit paths.

Published: August 30, 2026 · Last verified: August 30, 2026