Hunyuan3D and TRELLIS Licenses: What the Output Terms Allow

Hunyuan3D 2.1 (Tencent)

The LICENSE file in the Hunyuan3D-2.1 repository is titled “TENCENT HUNYUAN 3D 2.1 COMMUNITY LICENSE AGREEMENT”, release date June 13, 2025. GitHub shows its license as “Other / NOASSERTION”, and Hugging Face tags it tencent-hunyuan-community. Quotes below are from the raw LICENSE file.

Territory. The Territory is “the worldwide territory, excluding the territory of the European Union, United Kingdom and South Korea.” The header states that it “DOES NOT APPLY IN THE EUROPEAN UNION, UNITED KINGDOM AND SOUTH KOREA”, and the grant is “for the Territory only”. Section 5(c) is the clause that matters for shipping: “You must not use, reproduce, modify, distribute, or display the Tencent Hunyuan 3D 2.1 Works, Output or results of the Tencent Hunyuan 3D 2.1 Works outside the Territory.” Use outside it “is unlicensed and unauthorized under this Agreement.” The Acceptable Use Policy repeats the point.

So the limit reaches generated meshes, not just the weights. If you are in those places, this license as written does not cover you. A game on a worldwide store raises the harder version of the same question: “display” of Output outside the Territory is named, and whether a store selling to UK players puts you there is something the license does not spell out and this page cannot settle.

User threshold. Section 4 (“Additional Commercial Terms”): “If, on the Tencent Hunyuan 3D 2.1 version release date, the monthly active users of all products or services made available by or for Licensee is greater than 1 million monthly active users in the preceding calendar month, You must request a license from Tencent”. The test, as written, looks at the version release date, June 13, 2025, not your numbers today. Tencent “may grant” that license “in its sole discretion”. This is the only place the word “commercial” appears in the operative text; the Section 2 grant does not use it.

Output. Section 6(d): “Tencent claims no rights in Outputs You generate. You and Your users are solely responsible for Outputs and their subsequent uses.” Section 5(b) says you must not use the Works “or any Output or results” “to improve any other AI model (other than Tencent Hunyuan 3D 2.1 or Model Derivatives thereof)”. Section 1(g) adds that “Outputs by themselves are not deemed Model Derivatives”, which is what keeps a shipped mesh outside the distribution conditions below.

Clauses that are easy to miss.

• Section 3 sets conditions for distributing the “Works” (weights, code, Model Derivatives): give recipients a copy of the Agreement, mark modified files, and include a “Notice” text file with the stated wording. Section 3(c) only encourages a “Powered by Tencent Hunyuan” mark.
• Section 3(e) applies if you use the Works “in whole or in part, to provide, enable, or support any service, product, or functionality to third parties”. You must disclose the actual provider’s legal name and “expressly and conspicuously state that Tencent is not affiliated” with it. How far “support any … product” reaches for a game that only contains generated meshes is unclear.
• Acceptable Use Policy item 12 bars placing generated information in “any public context” without “expressly and conspicuously identifying that the information and/or content is machine generated”. Its examples are images, code, posts and articles, and 3D meshes are not named. A Steam AI disclosure plus a credits line is a sensible way to be on the safe side of it, in our reading. The policy also bars use “For military purposes” and was last modified November 5, 2024.
• Section 6(c) terminates your license if you bring a claim alleging the Materials or Output infringe your rights, and requires you to “defend, indemnify and hold harmless” Tencent from third-party claims arising from your use. Section 7(b) disclaims non-infringement warranties for Output. Section 9 selects Hong Kong law and courts.

Version coverage. The 2.0 license (release date January 21, 2025) has the same Territory, Section 3(e), Section 4, Section 5 and output wording when compared line by line with 2.1; the visible differences are the date, version name, repository link and one added item in the Section 4 request form. Hunyuan3D-Omni has its own “TENCENT HUNYUAN 3D Omni COMMUNITY LICENSE AGREEMENT” (release date September 26, 2025), filed as License.txt in its Hugging Face repository. Compared line by line with 2.1, its Territory, Section 4, Section 5 and output wording match; the visible differences are the date, version name, repository link and a footnote about a former Tencent entity. The README of 2.1 has no license section; the LICENSE file is the source.

Hosted use is different, with one catch. Tencent’s hosted API (Tencent HY 3D Global) runs under Tencent Cloud’s service terms, not the open-weight license. We did not read those terms and make no statement about them. Hosted versions 3.0 and 3.1 exist; we found no open weights for them. The catch runs the other way: the 2.1 license header covers use “including via any Hosted Service”, so a third party serving the open 2.1 weights does not obviously take you outside it.

What the Hunyuan text means for a real job

Our reading of the clauses above, by situation:

TRELLIS (Microsoft, v1)

The README: “TRELLIS models and the majority of the code are licensed under the MIT License.” Some submodules (diffoctreerast, Modified Flexicubes) “may have different licenses.” The LICENSE file reads “MIT License”, “Copyright (c) Microsoft Corporation.” The Modified Flexicubes link leads to a license that reads Apache 2.0 on the upstream repository. The diffoctreerast license is a research license: the software may be used “non-commercially”, defined as “for research and/or evaluation purposes only”, and its disclaimer bars use “FOR COMMERCIAL PURPOSES WITHOUT PRIOR AND EXPLICIT CONSENT OF LICENSORS”. The README’s setup script offers --diffoctreerast and --nvdiffrast install options, so the dependency question in the next section reaches v1 too. The README states a hardware requirement of an NVIDIA GPU with at least 16GB; its Linux-only testing note is paraphrased here (Windows setup is referenced in an issue but is not fully tested, per the README).

TRELLIS.2 (Microsoft)

The README: “This model and code are released under the MIT License”, and it continues that “certain dependencies operate under separate license terms”. It names nvdiffrast, “Utilized for rendering generated 3D assets”, and nvdiffrec, which “Implements the split-sum renderer for PBR materials”. The Hugging Face metadata shows license:mit. The README requires an NVIDIA GPU with at least 24GB of memory and says it is tested only on Linux. The model card notes raw meshes “may occasionally contain small holes or minor topological discontinuities”.

The dependency problem. The nvdiffrast license file is titled “Nvidia Source Code License (1-Way Commercial)”. Section 3.3 reads: “The Work and any derivative works thereof only may be used or intended for use non-commercially”, with “non-commercially” defined as “for research or evaluation purposes only and not for any direct or indirect monetary gain”. nvdiffrec’s license has the same use limitation, defined more briefly as “for research or evaluation purposes only”. Commercial use is reserved to NVIDIA and its affiliates in the nvdiffrast text.

MIT on the model does not change that dependency’s terms. What neither license states is whether a mesh rendered through such a dependency is itself restricted. The limit is written about the software’s use, not about outputs. Still, using a dependency to produce assets for a paid game is plausibly “direct or indirect monetary gain”. If you intend to sell what you make, treat this as an open question to resolve with NVIDIA or a lawyer before relying on “it’s MIT”.

Reading the difference

MIT’s notice condition attaches to “the Software”, so it matters if you redistribute the code or weights, and the license text does not address generated meshes. Silence is not a warranty.

Licenses also do not clear training data. The TRELLIS README describes TRELLIS-500K as curated from Objaverse(XL), ABO, 3D-FUTURE, HSSD and Toys4k, and the TRELLIS.2 README’s training example uses Objaverse-XL. Neither file says what the licenses of those collections mean for generated meshes, and the TRELLIS.2 model card states that outputs “reflect the distribution of the training data”. Hunyuan’s license disclaims non-infringement instead of addressing the point.

Practical notes

• Check the repository again before each release. Weights, licenses and submodules change between versions, and this page covers the versions listed.
• Third-party ComfyUI wrappers and forks carry their own licenses; read each one separately.
• If your audience includes the excluded regions, the Hunyuan license gives you no grant there; TRELLIS.2 is the simpler case on territory, with a hardware cost and the dependency question above.
• Save a dated copy of the LICENSE file with your project. A repository can change the file after you generate, and you will want to show what applied at the time.
• For the store and plan side of shipping, use the selling-a-game checklist.

For running them, see open-source generators, the Hunyuan3D review, the TRELLIS.2 review and the head-to-head comparison. For hosted tools’ terms see commercial use.

More in the licensing hub.