FIELD GUIDE

Tencent HunyuanVideo: Open-Weight Production and a Material Territorial License Restriction

Version: HunyuanVideo base / HunyuanVideo-1.5 | Documented or relevant tier: Self-hosted; territory restrictions | Verification date: 2026-10-25 | Coverage cut-off: 2026-10-25 | Editorial status: REVIEW — open verification issues.

A publicly downloadable generative video checkpoint is not automatically an unrestricted open-source product. Tencent’s original HunyuanVideo repository is a particularly important example because its community license explicitly excludes the European Union, United Kingdom and South Korea from the licensed territory. Teams building a global site or an international production pipeline must inspect license geography before recommending self-hosted deployment.

The dated model family

Tencent’s official repository records its first HunyuanVideo weights and inference-code release on 3 December 2024. Later updates include image-to-video material in March 2025 and HunyuanVideo-1.5 in November 2025. Those are distinct checkpoints with potentially different requirements. The repository also lists audio-driven avatar and customization research branches; merely finding one of those names does not establish a turnkey service or a permissive corporate license.

Read the specific rights document

The original HunyuanVideo license is titled ‘Tencent Hunyuan Community License Agreement’ and explicitly says it does not apply in the EU, UK or South Korea. That provision is materially different from an ordinary permissive code license. Operators should have counsel verify the full definition of territory, allowed use, derivative distribution and acceptable-use policy for the exact weights and variant they intend to run. Do not reason that a web download succeeding proves legal authorization in that region.

For a multinational team, a server’s location and the users’ locations may both be relevant to legal review. If the intended deployment touches an excluded jurisdiction, suspend the proposal until terms are reviewed and an authorized alternative is selected. This article is educational, not legal advice or a substitute for the full agreement.

Engineering checkpoint

Where authorized, record checkpoint checksum, source version, output settings, local hardware and dependency versions. Start with a short fictional scene rather than sensitive footage. Test video for flicker, subject drift, unnatural hands and unwanted text; write actual compute measurements only when the hardware has been measured. Preserve a bill of materials for any third-party nodes, codecs and enhancement plugins.

Editorial conclusion

HunyuanVideo is historically significant and technically relevant, but it should not be flattened into the phrase ‘free commercial model’. The corpus labels current plan, maximum runtime, frame rate and deployable territory on variants as unresolved unless supported by exact terms. This case also illustrates why AI 11 owns the general legal framework while AI 04 retains the video-specific implementation warning.

Worked production example

An international production agency is offered a self-hosted HunyuanVideo workflow for its offices in London, Seoul and Paris. The team should stop at license screening before buying GPUs because the original agreement excludes the UK, South Korea and EU. It must not assume that routing jobs through a server elsewhere automatically solves the problem. Counsel should identify which exact model agreement, users and territories are covered. If the planned usage is not authorized, choose another cleared technology and preserve the rejected plan as a documented rights decision.

Relevant alternatives and trade-offs

If regional terms block use, choose a model with verified local licensing such as an appropriately licensed Wan checkpoint, or a contractually cleared hosted service.

Sources & Further Reading

CONTINUE EXPLORINGExplore related files ↗