Tencent launches Hy Image 3.5 preview, says it matches ByteDance's Seedream 5.0 Pro
Tencent Holdings Ltd. announced the preview of its new image‑generation model, Hy Image 3.5. The company says internal testing showed the model’s output was on par with ByteDance’s Seedream 5.0 Pro, a leading competitor in the Chinese generative‑image market. No quantitative metrics were released, and the claim reflects Tencent’s own assessment.
Key points
- Tencent released Hy Image 3.5 preview, its latest image‑generation model.
- Tencent claims the model performed on par with ByteDance's Seedream 5.0 Pro in internal tests.
- The launch coincided with Alibaba unveiling its own new AI product.
The launch came on the same day Alibaba Group Holding Ltd. introduced its own AI offering, underscoring a rapid escalation of competition among China’s biggest tech firms in visual AI. While the preview is not yet generally available, Tencent’s statement suggests it aims to position Hy Image 3.5 as a top‑tier alternative to existing models.
Industry observers note that parity with Seedream 5.0 Pro could give Tencent a stronger foothold in applications such as advertising, e‑commerce visuals, and content creation, though the lack of external benchmarks leaves the true performance open to verification.
Model page: Hy Image 3.5 Preview →
The headline, key points and digest above were generated by Digest AI's editorial model from the linked sources. Automated summaries can contain errors: the sources are the record. Spotted a mistake? Tell us. Published by Martin K., who runs Digest AI and handles corrections.
More in Generative AI & Models
All →- Xiaomi releases MiMo-V2.6-Pro-RL, a 1.02T/42B open omnimodal model trained via scaled RL · 5 src
- AI Safety Concerns Erupt Amid Recursive Self-Improvement Fears · 3 src
- Hugging Face adds GGUF support to Transformers for local inference · 1 src
- Rumors of new AI models may surface next week · 1 src
- Austrian Academy of Science to release Apollo, first advanced Greek language model · 1 src
Comments
via GitHub Discussions