System requirements
QwenWorkSystem requirements for 2.1.0
The published floors are advisory; these are the numbers that people actually hit problems below. Anything under 8 GB of RAM will install and then stutter on long documents.
| Item | Minimum | Comfortable | Notes |
|---|---|---|---|
| Windows | 10 (1903+) / 11 | 11 23H2+ | Server editions untested, WebView2 required |
| macOS | 14 Sonoma | 15 Sequoia | Rosetta 2 only needed for Intel builds on Apple silicon |
| Linux | Debian 11 class | Debian 12 / Ubuntu 24.04 | glibc 2.31+, X11 or Wayland |
| CPU | 4 cores | 8 cores | No AVX-512 requirement |
| RAM | 8 GB | 16 GB | 16 GB recommended for spreadsheets over 50k rows |
| Disk | 2 GB free | 10 GB free | Cache grows with local file history |
| Display | 1366×768 | 1920×1080 | Scaling above 150% works but the preview shrinks |
| Network | 5 Mbps | 20 Mbps | Latency matters more than bandwidth |
Why the RAM floor matters more than it looks
The heavy work happens in the cloud, so the client itself is light — until you open a long document or a large sheet. Rendering happens locally, and the preview keeps an undo history in memory. On an 8 GB machine with a browser open, a 200-page document can push the client into swap and the UI freezes for seconds at a time. That reads as a bug but is not one.
Domains that must be reachable
Corporate firewalls break the client in ways that look like login bugs. These are the outbound destinations it needs:
- API and model endpoints — sign-in, generation, file sync.
- The asset CDN used for downloads and update checks.
- The object storage host used for file upload and preview.
A TLS-inspecting proxy will produce certificate errors rather than blocking messages. Allow-list by domain instead of intercepting.
Platforms that are not supported
- Windows 7, 8 and 8.1 — the client uses WebView2, which no longer ships for these.
- macOS 13 and earlier — the app is built against the 14 SDK.
- 32-bit Windows — no build exists, and none is planned.
- ChromeOS, WSL-only setups and ARM Linux without a desktop environment — the client is a GUI app.
Virtual machines and remote desktops
It runs inside VMware, Parallels and Hyper-V, but GPU-accelerated preview falls back to software rendering and feels sluggish. On a remote desktop session, file dialogs may open on the host instead of the guest; the workaround is to disable drive redirection for the session.