Any License Question Ask here!
Q&A About License
Why is MiniMax-H3's open-weight license currently limited to the EU, UK, South Korea, and US?
MiniMax-H3 was built with the goal of global availability. The current territory scope is not about excluding specific countries or regions, but about recognizing that video generation models are facing a more complex and rapidly evolving regulatory environment compared with text or code models.
Regions such as the EU, UK, South Korea, and the US are currently developing or enforcing AI-related regulations that may have specific implications for generative video models, especially around areas such as likeness generation, copyright, content safety, and responsible deployment.
The EU AI Act has started enforcement, while practical requirements for models capable of generating video and likeness-related content are still evolving.
Similar regulatory uncertainties exist in the UK and South Korea regarding AI-generated content and video generation.
In the US, AI regulation remains a rapidly changing landscape, and MiniMax is also involved in ongoing copyright-related legal proceedings specifically concerning generative video AI.
For open-weight models, once the weights are released, developers can deploy and modify them independently. This creates different compliance challenges compared with hosted services.
We had two options:
Wait until every jurisdiction reaches complete regulatory clarity before releasing open weights, which could take a long time while AI technology continues to evolve.
Release the model now with a transparent license scope, while continuing to evaluate and expand availability.
We chose the second approach. The current limitation means "not yet", not "not ever."
Why can MiniMax-H3 API be used globally if open weights are restricted in some regions?
The difference is the distribution model.
The main concern is not the existence of MiniMax-H3 itself, but the ability to control compliance after open weights leave our infrastructure.
For API access, MiniMax operates the serving infrastructure and can enforce appropriate safeguards, including:
Protection against misuse involving minors.
Copyright-related compliance measures.
Content safety controls.
Compliance with applicable laws and regulations.
With open weights, users can independently deploy, modify, and distribute the model, which makes it much harder to ensure the same level of compliance.
Therefore, the API and open-weight release follow different approaches:
API: Globally available with built-in safeguards and responsible-use controls.
Open weights: Temporarily limited in certain regions until the regulatory and compliance framework becomes clearer.
Can organizations in restricted regions still use MiniMax-H3?
Yes.
Organizations in these regions can apply for a formal license. After reviewing the deployment scenario and confirming that appropriate compliance controls and safeguards are implemented, MiniMax may authorize usage.
Application form >> https://platform.minimax.io/h3-license
Through authorized deployments, MiniMax can ensure that MiniMax-H3 is used responsibly while meeting local legal and regulatory requirements.
Will MiniMax expand open-weight availability in the future?
Yes. We will continue monitoring legal developments and reassessing the territory scope.
Our commitments:
Continuously review regulations and compliance requirements across regions.
Keep MiniMax-H3 API available globally, so users can continue accessing the model.
Clearly communicate any future license changes instead of making silent updates.
Listen to feedback from developers, researchers, and organizations affected by these restrictions.
Our goal remains the same: bringing intelligence to everyone with responsible AI use.
The current license scope reflects today's regulatory reality, not our long-term vision.
This regional carve-out stems from our ongoing generative video copyright litigation with major Hollywood studios.
We aim to deliver our AI tools globally to all users responsibly. US-based persons looking to deploy MiniMax-H3 may submit formal licensing requests. Licenses will be issued to applicants who commit to implementing robust compliance controls and guardrails fully aligned with US legal, compliance and regulatory requirements.
for the EU, UK, and South Korea. This regional carve-out is driven by ongoing regulatory evolution surrounding AI-generated video content across these regions. Unlike hosted services, open-weight model releases allow developers to independently deploy and modify model weights, introducing unique compliance challenges amid the current regulatory uncertainties in these regions. We will continuously monitor and assess evolving local regulations to adjust our access policies. In the meantime, persons based in these regions seeking to deploy MiniMax-H3 may submit formal licensing requests. Licenses will be granted to applicants that commit to implementing robust compliance controls and guardrails fully aligned with local legal and regulatory standards.
Incredible work. Am I reading this right that users in excluded territories need a formal license just to post research outputs? Also why is the application hosted on a thrid-party Feishu link instead of Hugging Face or a MiniMax domain?
Hello. I am the creator of Sulpur 2, an uncensored finetune of LTX 2.3. I'm wondering if it would be within regulation to finetune h3 with the same manner of content, and then take a step further and host it on a website. There would of course be filters for legality.
Incredible work. Am I reading this right that users in excluded territories need a formal license just to post research outputs? Also why is the application hosted on a thrid-party Feishu link instead of Hugging Face or a MiniMax domain?
will use MiniMax domain very soon
Too bad I can't read
Licenses will be granted to applicants that commit to implementing robust compliance controls and guardrails fully aligned with local legal and regulatory standards.
how would they verify they wouldn't "misuse" it? nothing actually stops users in the sanctioned countries from downloading it, only companies will comply not to risk it
I believe giving back to the community matters, and crediting the creators should always be encouraged as a genuine expression of appreciation.
I have been using other models and avoided MiniMax H3 mainly because the attribution requirements seem unclear. If users are allowed to use the output, publish it on platforms like YouTube, and earn money from their own creativity through scripting, editing, and production, attribution should ideally be an appreciation, not a burden.
There is also a practical concern for small or new YouTube channels. At the beginning, creators are trying to build a clear identity and avoid making their descriptions look like promotional or marketing content. Being required to repeatedly mention a specific AI brand could potentially affect how the content is perceived and undermine the creator's efforts to build their own channel identity.
Could MiniMax please clarify whether attribution for H3 is mandatory, or simply appreciated/recommended?
I would very much like you to clarify the reasons for not releasing it. which is the better choice between "H3-Regenerate-2K" and "H3-Max" in terms of overall cost-performance for inference?
I would very much like you to clarify the reasons for not releasing it. which is the better choice between "H3-Regenerate-2K" and "H3-Max" in terms of overall cost-performance for inference? When release?
Hello MiniMax team,
Thank you for making MiniMax H3 available to the community.
I am an individual learner based in China, exploring how to create 2D game assets. I do not have a company, and I have not earned any revenue from these assets so far.
I use the open-weight MiniMax H3 model locally through ComfyUI to generate short animation clips. I then extract the frames and manually edit, clean up, and arrange them into character sprite sheets, effects, and other finished game assets. I would only be selling these finished assets—not model weights or access to a generation service.
Before offering anything for sale, I would sincerely appreciate your clarification on three questions:
- May I commercially sell these finished game assets?
Does the Community License allow an individual in China to sell H3-generated outputs that have been processed into game assets? Would I need any additional paid license or written permission before starting, even though I currently have no revenue? - May I sell these assets to customers worldwide, including in the Excluded Territories?
I understand that Section V.4 refers to Outputs as well as the model, so I do not want to assume that creating the assets in China makes worldwide distribution permissible.
Could you please clarify whether I may sell the finished assets to buyers in the United States, EU, UK, or South Korea? If separate authorization is required, is there an application route available to an individual creator like me? - May buyers use these assets in their own commercial games?
May I give buyers permission to edit these assets, incorporate them into commercial games, and release those games worldwide? Would the buyers need their own MiniMax authorization, or would any territorial restrictions still apply to their games?
I am still learning about model licensing and want to understand the requirements before selling anything or promising commercial-use rights to buyers. A written clarification or a link to the relevant official guidance would be very helpful.
Thank you for your time and patience.
I would very much like you to clarify the reasons for not releasing it. which is the better choice between "H3-Regenerate-2K" and "H3-Max" in terms of overall cost-performance for inference? When release?
I'm a freelance video creator who delivers finished video files to clients; I don't run a hosted app or service. A few things I'd love clarity on:
If a client refuses to include any "Powered by MiniMax H3" mention on their published content, is that a compliance issue for me (the person who generated the video), given I'm not the one publishing or operating any product/service?
Separately — if I instruct my client to add an AI-generated disclosure per the Acceptable Use Policy, but they don't after I deliver the video, does that responsibility fall on me or on them, since they're not a party to this license?
If none of this can be resolved for client-delivery workflows where the client won't agree to any branding or disclosure at all, would you recommend using MiniMax H3 for that kind of work, or switching to a different model?
Would really appreciate clarification for freelance/client-delivery workflows like this. Thanks!
"H3-Regenerate-2K" and "H3-Max" when release?