How to work through it
The official repository lists H3-Base-FL2VA for text-to-audio-video and first-or-last-frame-to-audio-video work. With zero images it can run text-to-video; with one image it uses a first or last frame; with two it uses both endpoints. H3-Base-Ref2VA accepts text with image, video, and audio references. Download only the checkpoint family and framework format required by the test, then record the exact revision and files used.
A local H3-Base path produces the repository's documented 768p base result. MiniMax states that H3-Context-IR is a hosted interpretation layer and H3-Regenerate-2K is a separate module not yet included in the released package. Describing a local base run as the complete official 2K workflow would erase important system dependencies. Report which modules were local, which were called through an API, and which were absent.
The official repository links a MiniMax H3 Community License Agreement and sets out safety obligations. Teams should read the current license itself, document who approved the intended use, and avoid replacing that review with labels such as open source. The repository also notes that automated moderation cannot eliminate false positives or false negatives and does not replace a licensee's lawful-use and rights responsibilities.
Pin the repository revision, checkpoint, framework, precision, serving configuration, hardware, seed behavior, prompt processor, input hashes, and output hashes. Run the provider's reproducible examples before custom material, then add a rights-cleared representative brief. Compare local output only against a dated, equivalent hosted path when durations, references, prompt transformation, and regeneration stages are actually comparable.
The exact repository query is “MiniMax H3 open weights.” Its declared reader intent is evaluate; its taxonomy job is model orientation and fit review. No keyword-source attribution is attached to this retained manual entry; its visible page fields and references, when present, are the complete repository record used here. It combines a short possible entity label with one or more qualifiers; those qualifiers describe the reader's question, not documented product properties. The material qualifiers detected here are local, open-source, or deployment wording. The supporting topics recorded for this entry are “MiniMax H3 local deployment”, “H3 Base checkpoints”, and “MiniMax H3 Community License”. Those fields describe why the page exists and what the reader is asking; they are not product documentation. The attached repository profile names “MiniMax H3 Open Weights” and provider “MiniMax,” with status “Checkpoint and license scope verified.” The wording overlaps the attached official label, but facts still remain limited to the cited release and date. Keep the literal query, any possible entity name, every qualifier, and the desired decision separate until the provider-controlled identity record supports joining them.
Evidence class: source-backed. Evidence boundary — checked August 15, 2026: checkpoint scope, module availability, framework examples, and license link come from the official MiniMax repository. Hardware fit, operating cost, throughput, security, and legal suitability require separate verification. This is a deployment-scoping guide, not legal advice, a hosted inference service, or proof that a local run matches MiniMax's complete API workflow. 1 dated reference is attached from MiniMax. Their presence supports only their stated claim scopes. “MiniMax H3” by MiniMax, checked 2026-08-15, supports only this scope: Official checkpoint families, precision, supported tasks, framework examples, hosted module boundaries, safety statements, and Community License link. The attached profile states: MiniMax publishes two H3-Base checkpoint families for text or keyframe audio-video generation and multimodal reference audio-video generation under the MiniMax H3 Community License. Hosted Context-IR and the 2K regeneration module remain outside the initial weight release. Its separate boundary is: This page reports the official release scope checked August 15, 2026. It is not legal advice and does not establish hardware suitability, operating cost, security, support, SEELE integration, or equivalence with MiniMax's complete hosted system. The recorded evidence dates are 2026-08-15. They identify when the attached material was checked and do not make a name, plan, interface, or specification permanently current. Treat every reference by its written claim scope. Identity evidence cannot establish quality; an input document cannot establish price; a provider page cannot establish SEELE access; and an observation from one account cannot establish behavior in another region, version, mode, or host. If a source and the current product surface conflict, retain both records and leave the disputed field unresolved.
“MiniMax H3 local deployment” is a workflow decision; document the intended handoff, dependencies, owner, failure condition, and reason to proceed or stop. “H3 Base checkpoints” remains an editorial question until a claim-scoped source or authorized observation supplies an answer. “MiniMax H3 Community License” requires a current account, terms, or license record; the requested entitlement stays unverified without one. The page organizes the query through The repository section “Choose the checkpoint by task family” says: The official repository lists H3-Base-FL2VA for text-to-audio-video and first-or-last-frame-to-audio-video work. With zero images it can run text-to-video; with one image it uses a first or last frame; with two it uses both endpoints. H3-Base-Ref2VA accepts text with image, video, and audio references. Download only the checkpoint family and framework format required by the test, then record the exact revision and files used., The repository section “Do not collapse base and complete-system claims” says: A local H3-Base path produces the repository's documented 768p base result. MiniMax states that H3-Context-IR is a hosted interpretation layer and H3-Regenerate-2K is a separate module not yet included in the released package. Describing a local base run as the complete official 2K workflow would erase important system dependencies. Report which modules were local, which were called through an API, and which were absent., The repository section “Treat the release as licensed weights” says: The official repository links a MiniMax H3 Community License Agreement and sets out safety obligations. Teams should read the current license itself, document who approved the intended use, and avoid replacing that review with labels such as open source. The repository also notes that automated moderation cannot eliminate false positives or false negatives and does not replace a licensee's lawful-use and rights responsibilities., and The repository section “Build a reproducible deployment record” says: Pin the repository revision, checkpoint, framework, precision, serving configuration, hardware, seed behavior, prompt processor, input hashes, and output hashes. Run the provider's reproducible examples before custom material, then add a rights-cleared representative brief. Compare local output only against a dated, equivalent hosted path when durations, references, prompt transformation, and regeneration stages are actually comparable. Its FAQs narrow the reader's likely follow-up questions. For “Which MiniMax H3 weights are available?”, the recorded answer is: MiniMax's repository provides H3-Base-FL2VA and H3-Base-Ref2VA checkpoints, with the components required for their respective text, keyframe, and reference-to-audio-video tasks. For “Are H3-Context-IR and 2K regeneration open with H3-Base?”, the recorded answer is: No. The official repository says Context-IR is hosted and H3-Regenerate-2K is not included in the initial release, though APIs are documented for the complete workflow. For “Is MiniMax H3 open source?”, the recorded answer is: Use the precise term open weights and read the linked MiniMax H3 Community License. This page does not provide legal advice or reinterpret the license for a specific deployment. This is the complete page-specific editorial record available in the repository for “MiniMax H3 open weights.” It may define questions, cautions, or a review method, but it does not become external product evidence through repetition. Where one of these fields asks for a provider, model label, plan, capability, result, right, policy, or availability fact that no attached reference supplies, the only supported status is Unknown / not verified.
For “MiniMax H3 open weights,” the model orientation and fit review must identify whether the reader needs provider identity, a model family, an accepted input, a controllable behavior, an output constraint, an access surface, or a production-fit decision. The repository's intended workflow is to resolve identity, collect a bounded fact ledger, and use a representative authorized brief only for the workflow question documentation cannot settle. Capture exact label, provider, version, surface, region, date, inputs, controls, outputs, stated limits, failures, judgment, and unresolved questions. Apply that requirement only to the recorded topics “MiniMax H3 local deployment”, “H3 Base checkpoints”, and “MiniMax H3 Community License”. Recognition, search demand, a showcase, or one successful result cannot establish current access, affiliation, quality, consistency, licensing, or SEELE support. Documented facts, direct observations, editorial judgments, and unknowns belong in separate fields: a fact retains a URL, publisher, claim scope, and date; an observation retains the exact product label, account surface, region, inputs, controls, failures, result, and observation date. A conclusion is bounded to the decision stated by this entry, not to every product that shares part of its wording. Refresh whenever the provider, version, inventory, interface, inputs, controls, output rules, plan, license, policy, or delivery requirement changes.
The wording triggers local, open-source, or deployment wording. Deployment wording creates separate questions about code, weights, identity, licenses, dependencies, hardware, and hosted-service parity. Require a provider-controlled repository or model card, pin the revision and checkpoint, map applicable licenses, record the runtime, and reproduce a bounded official example before a custom test. A mirror or successful local run cannot prove hosted feature parity, support, security, commercial permission, throughput, or production readiness. Read these qualifiers together with “MiniMax H3 local deployment”, “H3 Base checkpoints”, and “MiniMax H3 Community License” and the model orientation and fit review; detaching one would answer a different query. A requested qualifier is not proof. Until a current claim-scoped source or authorized observation resolves it for the same provider, identity, version, surface, account, region, and date, record the result as Unknown / not verified and name the field that still needs checking.
The attached MiniMax H3 Open Weights profile lists these inputs: FL2VA: text with zero, one, or two keyframe images, Ref2VA: text with image, video, and audio references, Repository processor and tokenizer files, and Framework-specific serving configuration. It records these documented capabilities: Local text-to-audio-video, Local first-or-last-frame-to-audio-video, Local reference-to-audio-video, Provider examples for SGLang, vLLM, diffusers, and ComfyUI, and Checkpoint-specific reproducible cases. Its output notes are Released checkpoints use BF16, The repository describes the released checkpoints as CFG-distilled, Local H3-Base is the documented 768p path, and Context-IR and Regenerate-2K require separate hosted modules in the complete workflow. These facts are bounded to MiniMax, the attached references, and their evidence dates; they are not an independent benchmark, a statement about an uncited version, or a promise of access in SEELE, every region, or every account. The profile's bounded workflow use is: Use the open weights when deployment control, reproducibility, or fine-tuning investigation matters and the team can own infrastructure, security, license review, prompt processing, moderation, output review, and the difference from the complete hosted path. Before relying on a listed input, capability, or output, connect it to the particular attached reference whose claim scope covers it and to the same release or service surface. If the reference does not state the fact, or the current interface cannot be reconciled with that source, leave the field Unknown / not verified and keep it out of the test assumption. The profile's repository test briefs are “Provider example reproduction”: Pin a repository revision and reproduce the official task-family example before introducing custom assets. Save environment, framework, checkpoint files, configuration, request, logs, and output hashes., “Local versus hosted boundary”: Run a comparable authorized brief through local H3-Base and the complete hosted path only when input transformation and regeneration stages are documented. Report configurations separately rather than pooling results., and “Operational readiness”: Exercise model loading, request isolation, failure recovery, storage, logging, moderation, rights review, and asset deletion. Treat a successful demo output as only one part of a production deployment decision. Its recorded review checklist is “Repository revision, checkpoint family, framework, precision, and configuration are pinned”, “The current Community License is reviewed for the intended use”, “Context-IR and 2K regeneration are not implied when absent”, “Security, moderation, provenance, storage, and deletion controls are documented”, and “Hardware fit, throughput, cost, and support are measured in the team's own environment”. These are evaluation instructions, not results; this page contains no completed run, output, selection rate, reviewer verdict, or production approval unless one is explicitly attached elsewhere. For “MiniMax H3 open weights,” test only the part of the recorded decision that documentation cannot settle. Use authorized material and preserve the literal input, instructions, visible controls, selected label, interface, account and region, attempt count, failures, output, and observation date. Derive acceptance criteria from “MiniMax H3 local deployment”, “H3 Base checkpoints”, and “MiniMax H3 Community License”, not from a universal score. A result supports only that captured setup; it cannot establish permanent quality, general access, provider affiliation, licensing, safety, or behavior in another version, mode, host, or service.
An answer to “MiniMax H3 open weights” should state the requested decision, exact identity status, accepted and rejected evidence, evidence date, access context, any authorized observation, and every unresolved field. A proceed decision is limited to the documented provider, version, surface, account, region, inputs, controls, attempt allowance, and delivery target. A stop decision must identify its actual blocker: unresolved identity, absent source, unverified access, missing rights, unsupported input, failed output, policy risk, or poor workflow fit. Refresh whenever the provider, version, inventory, interface, inputs, controls, output rules, plan, license, policy, or delivery requirement changes. Also reopen the record when a cited page disappears, an identifier no longer matches the interface, a reference changes scope, or delivery creates a new rights, safety, disclosure, or technical condition. Until evidence supplies the missing fact, Unknown / not verified is more accurate than either a positive promise or a negative capability claim.
