top of page

Tencent Releases Hy4 Flagship Open Weights

19 minutes ago
11 min read
Illustrative photograph. Photo: Bibek ghosh / Pexels.

Tencent released Hy4’s open weights on November 20, 2026, giving developers access to a flagship model with a 770-billion-parameter language backbone. The Tencent Hy4 open weights release lets outside teams download its learned parameters, the numerical values that determine model behavior. It also brings a practical tension: access expands, while infrastructure requirements and a custom commercial license shape who can deploy it.

Tencent describes Hy4 as natively multimodal, meaning it processes text, images, and video within its model architecture. Its mixture-of-experts design, which routes each token through selected neural networks, activates 49 billion language parameters per token. Tencent lists a context capacity of 1,048,576 tokens, the text and visual units a model processes.

The immediate contest is between downloadable model control and the convenience of hosted services. Tencent’s materials compare Hy4 with DeepSeek models and acknowledge remaining gaps against leading proprietary systems. For developers and enterprise buyers, the release creates another model to evaluate directly. It does not establish that operating it beats renting access.

What Tencent Hy4 open weights actually change

The November 20 event expands access to Hy4’s flagship weights, rather than introducing the Hy4 name for the first time.

Tencent’s open weights announcement presents the release alongside a system card, safety evaluation materials, and download routes. That distinction matters because earlier previews, hosted availability, and related models can blur the timeline. This article concerns the flagship weights release.

The release package includes Hy4’s instruction-tuned model, an FP8 version, and a pretrained base model. Instruction tuning adapts a pretrained model to follow requests. FP8 represents model values using eight-bit floating-point numbers, reducing their storage requirements compared with higher-precision formats.

These downloads serve different audiences. The instruction-tuned versions target interactive applications and evaluation. The base model gives researchers a starting point for further training, but Tencent explicitly says it is not an instruction-tuned chat model.

That qualification prevents a misleading comparison. A base model should not be judged as though it were a finished assistant. Conversely, strong base-model benchmark results do not establish the performance of a deployed assistant with tools, retrieval, and application permissions.

Tencent’s parameter headline also needs its boundaries preserved. The 770 billion figure describes the language backbone, excluding the vision encoder, adapter, and DFly2 drafting component. The vision encoder has 1.23 billion parameters, and DFly2 adds 3.3 billion.

The adapter converts visual features into units the language model can process. DFly2 supports speculative decoding, a technique that proposes candidate tokens for the main model to check. Those components explain why a headline parameter count does not describe every part of the system.

The company links GitHub materials, Hugging Face weights, and a compressed GGUF download. GGUF is a model file format used by compatible inference software. Its availability broadens the formats developers can investigate, without establishing a particular hardware requirement or speed.

Tencent also advertised a team question-and-answer session on r/LocalLLaMA for November 20, from 8–10 AM Pacific Time. That was an announced discussion window, not evidence that every deployment question received an answer. It should not be presented as an upcoming event after that date.

The practical change is reproducibility of access. Outside teams can inspect the distributed artifacts and run their own evaluations under the license. They no longer need to base every assessment on a hosted endpoint or vendor demonstration.

That access does not independently verify Tencent’s capability claims. It creates the conditions for verification, including tests that disagree with the company’s results. The difference between those outcomes is central to understanding the release.

Hosted convenience faces a control test

Hy4 puts pressure on hosted services where customers value deployment control enough to accept operating responsibility.

For a hosted model, the provider handles the underlying serving infrastructure. Customers integrate an interface and evaluate the resulting service. Downloadable weights shift more responsibility toward the operator, including capacity planning, model configuration, monitoring, and upgrades.

That shift matters most for organizations with specific deployment constraints. A team evaluating internal documents can test the model within infrastructure it controls. Whether that arrangement meets its requirements still depends on the surrounding system, access rules, and operational practices.

Downloading a model does not automatically make an application private. An application can still send information through external search tools, logging services, or connected software. Control becomes useful when the organization governs those additional paths.

Tencent positions Hy4 for finance, office work, software development, scientific research, and assistant tasks spanning extended interactions. These are company-described use cases. They identify intended workloads without proving dependable performance across every organization’s documents, software, or operating conditions.

Consider an illustrative research workflow involving reports, chart images, meeting notes, and a presentation draft. A multimodal model can potentially interpret visual information alongside text. The useful outcome is an accurate, traceable synthesis that preserves disagreements and missing evidence.

A large input allowance helps only if the model uses that material correctly. Accepting a long report does not demonstrate that the model notices a crucial qualification. Producing a polished slide does not demonstrate that its underlying figures remain accurate.

This is where model access intersects with knowledge management. A searchable knowledge base helps teams organize the material an assistant needs. The Hy4 announcement does not establish a remio integration or support relationship.

Hosted competitors retain a clear advantage wherever customers prioritize simpler operation. Downloadable weights appeal where customization, inspectability, or infrastructure control justify the added work. Neither route wins merely because its access model sounds more open or more convenient.

The Tencent Hy4 deployment decision therefore begins with the organization’s actual constraint. A research lab might prioritize training access. An application team might prioritize response consistency, while an internal platform group might prioritize operating within existing infrastructure.

Tencent’s release requires hosted providers to compete against that option on measurable service value. Reliability, integration quality, and support become part of the comparison. For customers without the capacity to run Hy4, hosted access can remain the more practical choice.

The pressure runs in both directions. Tencent must show that its downloadable model produces useful results outside company demonstrations. Operators must show that their implementation preserves those results under real demand, tool permissions, and document complexity.

A 49B active model still carries a 770B backbone

Selective computation reduces the parameters used for each token, but it does not erase the model’s overall deployment footprint.

The 49 billion active figure describes computation through selected parts of the language backbone. It should not be read as the size of the complete downloadable model. Operators still need a deployment strategy for the full model and its supporting components.

Tencent’s architecture uses routed experts, specialized neural networks selected for each token, alongside shared processing. This design makes the distinction between total and active parameters useful. It also makes simple comparisons with smaller dense models incomplete.

A dense model uses its main parameter set for each token. An expert model selects portions of its network. Comparing their active counts alone leaves out storage, memory movement, serving software, and the communication needed across hardware.

Tencent’s model specifications describe a 78-layer backbone and additional mechanisms intended to support efficient operation. Those engineering choices deserve workload testing. Their presence in documentation does not establish a universal throughput or latency advantage.

The published serving examples use eight-way parallel configurations. Parallel serving divides model work across multiple accelerators, processors designed for intensive numerical computation. These examples indicate substantial infrastructure expectations, although they do not define every possible supported configuration.

There is no basis here to promise ordinary laptop operation. A compressed download can reduce storage requirements, but the usable configuration depends on its precision and runtime support. Quality, responsiveness, and available memory remain separate questions.

Tencent’s GGUF model files offer another route for testing compressed versions. The company describes this version as intended for end-to-end testing. Availability of that format should not become an unsupported claim about consumer hardware compatibility.

Quantization, which stores model values at reduced numerical precision, creates its own evaluation requirement. A smaller representation needs testing on the tasks that matter. Results from a different representation should not automatically carry over.

The same caution applies to the million-token context specification. Context capacity describes how much input a configuration supports. It does not guarantee equal accuracy at every position, every document length, or every combination of text and images.

Long inputs also affect operation beyond the model’s weight files. Serving software maintains intermediate information while processing requests. Request length, simultaneous users, and output behavior influence the resources an operator needs.

Tencent says its DFly2 drafter reuses information from the main model to support speculative decoding. That is an architectural claim about reducing duplicated work. Actual benefits depend on the deployment and workload, including whether proposed tokens are accepted.

For Tencent Hy4 deployment, the relevant question is how the complete system behaves. Operators need results that identify hardware, model version, numerical precision, and serving settings. Without that context, a speed claim offers little basis for comparison.

The architecture supports a plausible operating strategy for a very large model. It does not settle the decision between operating Hy4 and using a hosted service. That decision requires measured quality and operating performance together.

Downloadable weights come with a custom license

Hy4’s weights use the Tencent Hy License, Version 1.0, which explicitly states that it is not Apache License 2.0.

That distinction belongs near the center of any commercial evaluation. The license says it derives from Apache License 2.0 with modifications. Describing the weights simply as Apache-licensed removes terms that can matter to potential operators.

The commercial license terms include additional conditions for certain large model-as-a-service businesses. Model-as-a-service means providing third parties remote access to model inference or training customization. The document defines the relevant scope and exclusions.

Its additional requirements depend on specified business-revenue or service-audience thresholds. Those are licensing triggers, rather than a universal prohibition on commercial use. A company should assess the actual definitions instead of inferring permission from a download button.

The license distinguishes general model access from end-user products restricted to particular features or workflows. It also addresses merely relaying requests to an independently operated third-party service. Those distinctions make the business model relevant to the analysis.

An internal-use exception appears in the additional commercial terms. Its conditions include restrictions involving third-party availability of the model, derivatives, and outputs. Calling a deployment “internal” does not itself establish that the exception applies.

The license also identifies modified model weights as derivative works, including quantized, fine-tuned, distilled, merged, or pruned versions. Fine-tuning means further training an existing model. Downloading a community conversion therefore does not automatically remove obligations attached to the underlying weights.

This structure creates a different proposition for different users. Researchers gain access to model artifacts under stated conditions. Application developers must examine their distribution and service arrangements. Large general-purpose serving businesses face an additional licensing question.

The important reporting conclusion is narrower than declaring Hy4 commercially unrestricted or commercially unusable. Neither description captures the document. The release combines downloadable weights with conditions that vary according to the defined activity and scale.

That structure also affects the competition with hosted services. Independent hosts can add value through operations and integration, but their licensing position needs examination. The same is true of organizations planning to offer general-purpose access through their own interface.

Tencent Hy4 open weights consequently describe an access change, not a complete statement about downstream rights. Technical feasibility and permission are separate parts of a deployment decision. Both need resolution before a business commits to a service architecture.

For buyers, careful license handling is also an operational signal. A prospective provider should be able to identify the model and terms behind its service. Vague references to an “open-source model” leave too much uncertainty about the actual arrangement.

The appropriate next step is to read the applicable license against the intended use. This article describes its structure and does not determine any organization’s legal position. The published text remains the source for those conditions.

Tencent’s own results leave room for skepticism

The release makes independent testing possible, while Tencent’s benchmark claims remain vendor-reported evidence.

Tencent’s documentation presents comparisons covering knowledge, reasoning, coding, visual understanding, and specialized work. Those results explain the company’s positioning. They do not establish that Hy4 is the strongest model overall or the best choice for every application.

Its base-model comparisons include DeepSeek-V4-Pro-Base and DeepSeek-V4-flash-Base. Other evaluations include Kimi and GLM models. These references locate Hy4 within a competitive field, but the evaluation conditions determine what each comparison supports.

A base-model result answers a different question from an assistant evaluation. Tool selection, application state, document handling, and recovery behavior can change the outcome. A model with strong knowledge scores can still fail an extended software task.

Tencent also discloses a formatting caveat in its base-model evaluations. It says synthetic instruction data during training sometimes causes unexpected answer formatting. According to the company, that behavior can distort scores in tests using example-based prompts.

That disclosure limits easy interpretation in either direction. An answer-format mismatch can affect a score without identifying the complete cause. Independent evaluation needs to distinguish knowledge errors from formatting failures and report both.

The documentation also acknowledges gaps against leading proprietary models. Tencent identifies difficult research mathematics, extended coding, model self-improvement, and advanced visual question answering among remaining limitations. Those admissions should remain alongside the company’s favorable results.

They are particularly relevant to the self-hosting argument. Infrastructure control does not compensate for an inability to complete the required task. Buyers need evidence that the downloadable model meets their quality requirements before control becomes a decisive advantage.

Tencent describes internal evaluations showing reduced hallucinations, meaning generated claims unsupported by the relevant evidence. Such results depend on the test material and scoring rules. They should not become a universal error rate for every Hy4 application.

The same boundary applies to finance and scientific-workflow claims. Expert participation and specialized tasks can make an evaluation informative. They do not guarantee that another organization will see the same performance on different documents or procedures.

Tencent links a system card containing safety evaluation materials. Publishing that document creates a basis for scrutiny. Its existence alone does not establish that all risks are resolved or that a deployment needs no additional safeguards.

Computer use makes that distinction concrete. A model that interprets an interface still needs software that controls its permissions and actions. An incorrect visual judgment can become consequential when connected to file changes, account settings, or external communications.

An illustrative document assistant should therefore face more than fluent-answer testing. Evaluators should check whether it distinguishes a proposal from an approved decision. They should also examine whether it flags conflicting sources and leaves unsupported conclusions unresolved.

Those tests pressure the claim that broader context produces dependable work. The model must select relevant evidence and preserve its meaning, not simply accept more material. Independent results on that behavior would be more useful than another unqualified ranking.

Tencent Hy4 explained through benchmark headlines alone would miss this central uncertainty. The release provides artifacts and company evaluations. It leaves outside researchers and operators to establish how well those results transfer.

Three signals will show whether access becomes adoption

The next evidence should connect independent quality, deployment performance, and sustained use in that order.

The first signal is independent evaluation of the released artifacts. Researchers should identify the exact model version and distinguish the base, instruction-tuned, and compressed variants. That makes it possible to understand whether results describe the same system.

Useful evaluations will include visual tasks and extended work alongside short benchmark questions. They should examine source fidelity, failure recovery, and performance across long inputs. Published limitations matter as much as favorable averages.

If outside results broadly support Tencent’s claims, the case for evaluating Hy4 as a hosted-service alternative strengthens. If major gaps appear, its audience becomes more specific. Either outcome improves the decision beyond relying on release-day positioning.

The second signal is reproducible deployment evidence. Operators need reports that connect usable output quality with hardware and serving configuration. A successful launch command demonstrates that a model starts, while sustained operation answers a broader question.

Those reports should explain the model representation, input lengths, and simultaneous request conditions. They should also distinguish demonstrations from production workloads. Otherwise, an appealing performance figure can conceal assumptions that another organization cannot reproduce.

Stronger Tencent Hy4 deployment evidence would make the operating tradeoff easier to evaluate. Teams could identify which workloads justify running their own infrastructure. Weak or inconsistent results would preserve the convenience advantage of hosted services.

Compression deserves particular attention within that signal. A compressed variant becomes more useful when its behavior remains acceptable on the intended task. Smaller files alone do not establish a better application.

The third signal is sustained use accompanied by clear licensing and operating practices. Announcements from providers or application teams will matter more when they identify the deployed artifact. Continued use after evaluation offers stronger evidence than a download count.

For research organizations, published adaptations would show that access supports work beyond the original model. For businesses, documented service behavior would show whether teams can turn the release into a dependable offering. Neither outcome should be assumed from availability.

These signals also test Tencent’s distribution strategy. The release gives outside developers more room to experiment while retaining defined commercial conditions. Its practical reach will depend on how many teams find that combination workable.

Over the following months, the most informative evidence will come from deployments that disclose both successes and failures. Transparent results help separate model limitations from serving problems. They also reveal where additional engineering changes the outcome.

For developers considering the Tencent Hy4 open weights, begin with a representative task and a clear definition of success. Compare the downloadable model with the hosted service you would otherwise use. Include difficult documents, conflicting evidence, visual details, and failures that require recovery. Ask what operating control solves for your team, then measure whether Hy4 delivers acceptable results within that arrangement. Review the license against the actual service you intend to build. Keep the deployment configuration attached to every evaluation result so later changes remain comparable. The release gives you something concrete to test; make that test specific enough to support a real decision.

Get your work moving in remio

See what needs your attention and take the next step in Workspace.

remio currently supports Windows 10+ (x64) and Macs with Apple silicon.

Your AI Partner at Work
Get more done with remio

Plan. Create. Deliver.
All in one place.

bottom of page