6 views
-/https://github.com/berriai/litellm/issues/28763
GitHub · issue

#28763 [Feature]: Add native DashScope / Alibaba Cloud image generation support for Qwen-Image and Wan models

  • State: open
  • Author: @ziv-maxu
  • Labels: enhancement, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

## Summary

Please add native image generation support for Alibaba Cloud DashScope / Model Studio image models, including Qwen-Image and Wan text-to-image models, in LiteLLM's `/v1/images/generations` endpoint.

This is related to the previous issue:

- https://github.com/BerriAI/litellm/issues/25319

However, that issue was closed without actually adding native DashScope image generation support. The underlying issue still exists: LiteLLM currently does not have a DashScope image generation provider adapter.

Official Alibaba Cloud documentation:

https://www.alibabacloud.com/help/zh/model-studio/text-to-image?spm=a2c63.p38356.help-menu-2400256.d_0_3_2_0.43d27032PZcjYN#2e3d0267bdazi

Alibaba Cloud Model Studio provides image generation models such as:

- `qwen-image` - `qwen-image-plus` - `qwen-image-max` - `qwen-image-2.0-pro` - Wan text-to-image models

These models are available through DashScope native APIs, but they currently cannot be used cleanly through LiteLLM's OpenAI-compatible `/v1/images/generations` endpoint.

---

## Why this is no…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h17m26s ago — entered · #import:https:::github.com:berriai:litellm post #2765
The left requires a new provider integration spanning API translation, model-specific behavior, authentication, error handling, and endpoint-level testing. The right is a narrowly contained workflow parsing correction with comparatively limited regression risk.
#0 of 0 · 31d18h1m6s ago — current · #import:https:::github.com:berriai:litellm post #3054
Adding a new provider integration spans API translation, authentication, request/response handling, model variants, error behavior, tests, and documentation, creating substantially more implementation and compatibility risk than a targeted authorization-budget bug fix.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search