Reference
QwenWorkReference numbers and endpoints
Facts you look up rather than read. Everything here is either a published rule or a measured value, and the page says which is which.
Input formats
| Type | Accepted | Ceiling | Notes |
|---|---|---|---|
| Documents | docx, pdf, txt, md | ~200 pages | Scanned PDFs need OCR; without it you get an empty summary |
| Spreadsheets | xlsx, xls, csv | ~50k rows | xlsm is read as data; macros never execute |
| Slides | pptx | ~100 slides | Rendered as images for analysis, text extraction is lossy |
| Images | png, jpg, webp | 20 MB each | Text in images is read; charts are described, not measured |
| Archives | Not accepted | — | Unpack before uploading |
Output formats
docx, xlsx, pptx, pdf, md, html. The office formats are real files with editable structure, not images wrapped in a container. A generated pptx keeps its master and can be restyled wholesale; a generated xlsx keeps formulas as formulas.
Rate limits
| Limit | Value | Applies to |
|---|---|---|
| Automation runs | 200 per hour | Per workspace |
| Active tasks on free tier | 10 | Per workspace |
| Concurrent generations | Task-dependent | Per member |
| File upload size | Task-dependent | Per file |
Values in this table are observed behaviour on 2.1.0, not a published contract. The vendor can change them without a release note, which is why automation designs should degrade gracefully rather than assume a ceiling.
Platform matrix
| Platform | Desktop client | Web client | Mobile app |
|---|---|---|---|
| Windows 10/11 | Yes, x64 + ARM64 | Yes | — |
| macOS 14+ | Yes, arm64 + x64 | Yes | — |
| Debian-like Linux | Yes, amd64 + arm64 | Yes | — |
| iOS 14+ | — | Yes | Yes |
| Android 10+ | — | Yes | Yes |
| HarmonyOS 7.0+ | — | Yes | Yes |
API status — the honest version
The vendor does not publish an open developer API for third-party applications. There is no documented REST endpoint, no API key console, and no SDK on a public package registry. What exists internally powers the client and the web app; it is not a supported integration surface.
Update channel behaviour
Desktop builds resolve through a /release/latest/ path, so the file behind a fixed URL changes with each release. There is no long-term archive. For reproducible environments, record version, date and hash together, and expect to store the package yourself.