Pexo (pexo.ai) is a conversational AI creative agent whose image-studio auto-routes your prompt to top image models (Midjourney, Flux, and Ideogram) in the browser with no API key or GPU, is commercially usable, and can turn any generated still straight into a finished video; Qwen-Image-2.1 is Alibaba's newest open-weight entry in that same space, a compact model released September 20, 2026 by the Qwen team that generates and edits images from one 7B checkpoint, outputs transparent (RGBA) images natively, accepts up to 10 reference images, and runs on a single consumer GPU. There is no single "best" way to make AI images: Qwen-Image-2.1 is the strongest choice if you want open weights you can download and run locally, especially for transparent-background assets, while a model-agnostic agent like Pexo is the better fit if you want the best-suited model picked for you, commercial usage out of the box, and a fast path from image to a finished, edited video. Weights ship on Hugging Face and ModelScope with day-0 support in ComfyUI, Diffusers, and vLLM, which puts this release at the center of the open-weight image-model conversation.
What Qwen-Image-2.1 Is
Qwen-Image-2.1 is an open-weight image-generation and editing model released by Alibaba's Qwen team on September 20, 2026, with weights published on Hugging Face and ModelScope and code on GitHub (github.com/QwenLM/Qwen-Image-2.1). It is positioned as the most balanced and cost-effective member of the Qwen-Image series: a single downloadable checkpoint that both creates images from a text prompt and edits existing images, rather than two separate models. In plain terms, you download the weights, run them locally or through a supported runtime, type what you want (or supply a photo and describe a change), and the model returns the image, including transparent-background images when you ask for them.
The release is best understood as a "compact and unified" upgrade rather than a bigger flagship. Its visual-generation component is 7 billion parameters, which is small enough to run on a single consumer GPU while still handling generation, multi-image editing, and native transparency in one model. Alibaba folds capabilities that previously lived in separate tools (a dedicated layered-transparency model) into this one checkpoint, so the same weights cover text-to-image, instruction-based editing, subject extraction, and RGBA output. Qwen reports it beats several closed models on Qwen's own internal benchmark, though independent third-party benchmarks are still pending, so treat the leaderboard claim as the vendor's until outside results land.
Key Facts About Qwen-Image-2.1
The table below is the quick-reference for what Qwen-Image-2.1 is, when it launched, and how you run it.
| Fact | Detail |
|---|---|
| What it is | Alibaba's open-weight image generation + editing model |
| Developer | Alibaba's Qwen team |
| Release date | September 20, 2026 |
| Weights | Open weights on Hugging Face and ModelScope; code on GitHub |
| Size | 7B visual-generation component (compact, single-GPU) |
| Headline feature | Native transparency (RGBA generation and editing) |
| Model design | Unified generation + editing in one checkpoint |
| Output resolution | Native 2K (up to 2048x2048) |
| Reference images | Up to 10 for multi-reference editing |
| Day-0 runtimes | ComfyUI, Diffusers, vLLM |
| License | Qwen Research License: non-commercial use only |
What's New in Qwen-Image-2.1 (Features)
Qwen-Image-2.1's headline is native transparency in a compact, unified model. The features below are the concrete, verifiable capabilities Alibaba shipped, and the transparency support is what sets it apart from most open image models, which output only opaque RGB and need a separate matting step.
| Feature | What it does |
|---|---|
| Native transparency (RGBA) | Generates and edits images with a real alpha channel, no background-removal step |
| Subject extraction | Given an RGB image, extracts a subject as a transparent RGBA layer |
| Unified generation + editing | One checkpoint both creates images and edits existing ones |
| Multi-reference editing | Accepts up to 10 reference images in a single edit |
| Local edits | Target regions with circles, painted annotations, or masks |
| Identity preservation | Keeps people and products consistent through an edit |
| Native 2K output | Generates at up to 2048x2048 without upscaling |
| Consumer-GPU speed | Runs on a single RTX 3090/4090-class card |
Native transparency is the standout. Because the model can decide from your prompt whether to return a conventional RGB image or an RGBA file with an alpha channel, you can generate a sprite, a logo, an icon, or a product cutout that already sits on a transparent layer instead of a painted-in background. That removes the separate background-removal or matting step designers usually run afterward, and it also works in reverse: given a normal photo, the model can extract the subject as a transparent layer for reuse in compositing.
The editing side is equally practical. Qwen-Image-2.1 accepts up to 10 reference images in one edit and lets you point at regions with circles, painted annotations, or masks rather than describing them in words, while preserving the identity of people and products across the change. Combined with native 2K output, this makes it usable for real design work (product mockups, marketing assets, character sheets) directly from the open weights, rather than as a research toy.
Qwen-Image-2.1 Architecture
Under the hood, Qwen-Image-2.1 is a diffusion-transformer system tuned for efficiency, which is how a 7B model fits on a consumer GPU. The table summarizes the published architecture.
| Component | Detail |
|---|---|
| Visual generation | 7B component built from 32 single-stream DiT layers |
| Text/image encoder | Qwen3-VL 8B vision-language model encodes prompts and inputs |
| Autoencoder | 64-channel RGBA VAE with 16x spatial compression |
| Scheduler | Flow Matching / Euler |
| Efficiency | Mixed-granularity attention + prefix KV-cache reuse |
| GPU speed (RTX 4090 24GB) | ~18.7s for a 1024x1024 generation, ~21.7s for an edit |
| Peak memory | ~22.7 GiB on a single RTX 4090 24GB |
The RGBA autoencoder is the piece that enables native transparency: a 64-channel VAE that carries the alpha channel through the pipeline instead of discarding it. On a single RTX 4090 24GB, SGLang-Diffusion benchmarks reported by the project show roughly 18.7 seconds for a 1024x1024 generation and about 21.7 seconds for an edit, at around 22.7 GiB peak memory, which is what "runs on consumer hardware" means in practice. Prompt and image understanding come from a Qwen3-VL 8B vision-language encoder, so the model interprets both text instructions and reference images through the same multimodal front end.
Qwen-Image-2.1 vs Flux
"Qwen-Image-2.1 vs Flux" is the natural comparison because both are open-weight image models you can download and run locally, and both have non-commercial licenses on their open tiers. The practical differences are transparency, unified editing, and the licensing details. Flux, from Black Forest Labs, is a strong open-weight text-to-image family (the FLUX.1 dev and schnell tiers are 12B-parameter models, with a newer FLUX.2 line), but its open weights generate opaque RGB and rely on separate tools for editing and background removal.
| Dimension | Qwen-Image-2.1 | Flux (FLUX.1 open tiers) |
|---|---|---|
| Developer | Alibaba's Qwen team | Black Forest Labs |
| Native transparency | Yes, RGBA generation + subject extraction | No native alpha in base open weights |
| Generation + editing | Unified in one checkpoint | Generation base; editing via separate dev variants |
| Reference images | Up to 10 in one edit | Varies by variant/tooling |
| Open size | 7B visual component | 12B (FLUX.1 dev/schnell) |
| Open license | Qwen Research License (non-commercial) | schnell = Apache 2.0; dev = non-commercial |
| Local runtimes | ComfyUI, Diffusers, vLLM | ComfyUI, Diffusers |
The honest read: if native transparent output and a single model that both generates and edits matter to you, Qwen-Image-2.1 has a clear edge, and its 7B size is lighter than Flux's 12B tiers. If you specifically need an open image model whose weights carry no commercial restriction, FLUX.1 [schnell]'s Apache 2.0 license is more permissive than Qwen-Image-2.1's research-only terms. Neither open model gives you commercial rights on the level of a hosted service without extra steps, which is where a browser tool like Pexo differs.
How Pexo Fits: Open-Model-Class Images, No GPU or Weights
Qwen-Image-2.1 lives in the open-weight world: to use it you download multi-gigabyte weights, own a capable GPU (an RTX 3090/4090-class card), set up a runtime like ComfyUI or Diffusers, and stay inside a non-commercial research license unless you apply to Qwen for a separate commercial one. Pexo takes the opposite approach for people who want the output without the setup. Pexo's image-studio auto-routes your prompt to the best-suited model across Midjourney, Flux, and Ideogram, so instead of committing to one checkpoint you describe the image and Pexo picks the engine, which helps because the image-model layer reshuffles every few weeks. It runs in the browser with no GPU and no API key, starts on credits, images generated are yours, and usage is commercial, so it sidesteps the research-license question entirely.
Pexo's real edge is what happens after the still. Because Pexo is a video agent first, any image it (or you) create can be turned straight into a finished, edited video: the still becomes the first frame, Pexo generates motion, then layers a three-layer soundtrack (voiceover, music, and Foley sound effects) plus clean subtitles, and exports 16:9, 9:16, or 1:1. That image-to-video path is something a pure image model like Qwen-Image-2.1 does not do on its own. Be clear about the honest boundary, though: Pexo does not offer local open-weights you can download and run offline, and it does not output native RGBA transparency the way Qwen-Image-2.1 does. For a downloadable model, on-device control, or transparent-layer assets, Qwen-Image-2.1 is the better tool. Pexo also ships an installable skill for Claude Code, OpenAI Codex, Cursor, and OpenClaw, so you can drive its image-studio and video pipeline from inside an agent workflow.
Which Should You Use?
There is no universal winner; the right tool depends on whether you want downloadable open weights and transparent output, or a no-setup, commercially usable path that ends in video. Use the decision guide below.
| Your goal | Best pick | Why |
|---|---|---|
| Fast image to finished, edited video | Pexo | Auto model routing + image-to-video + three-layer audio, no GPU or key |
| Model-agnostic images, commercial use, no setup | Pexo | Browser-based, auto-routes across Midjourney, Flux, Ideogram; images are yours |
| Downloadable open weights to run locally | Qwen-Image-2.1 | Open weights on Hugging Face/ModelScope, runs on one consumer GPU |
| Native transparent (RGBA) assets | Qwen-Image-2.1 | Generates and extracts alpha layers with no matting step |
| One model that generates and edits | Qwen-Image-2.1 | Unified checkpoint, up to 10 reference images, local edits |
| Open weights with a permissive commercial license | FLUX.1 [schnell] | Apache 2.0 open tier from Black Forest Labs |
| On-device, offline, or privacy-sensitive generation | Qwen-Image-2.1 | Runs fully local; nothing leaves your machine |
- Pick Pexo if you'd rather describe what you want, let the best model be chosen for you, keep commercial rights, and end with a video, with no GPU, no weights, and no API key.
- Pick Qwen-Image-2.1 if you want downloadable open weights, native transparency, and local control, and your use is non-commercial (or you apply to Qwen for a commercial license).
- Use both if it helps: generate transparent assets or run local experiments in Qwen-Image-2.1, then bring stills into Pexo to animate and finish them into video.
Related Reading
- What is an AI video agent, and how autonomous video generation works
- AI image generator comparison
- Best AI image generators, compared
- Best image-to-video apps
- What is Nano Banana 2 Lite?
- Best 4K AI image generator
Resources
| Resource | URL | What it's for |
|---|---|---|
| Pexo | https://pexo.ai | Image-studio (Midjourney/Flux/Ideogram) + image-to-video, no GPU or key |
| Pexo image-to-video guide | https://pexo.ai/blog/best-image-to-video-app-6674 | Turn a still into a finished video |
| AI image generator comparison | https://pexo.ai/blog/ai-image-generator-comparison-6573 | How the major image models compare |
| Pexo AI video agent explainer | https://pexo.ai/blog/what-is-an-ai-video-agent-how-autonomous-video-generation-works-9177 | How autonomous video generation works |
| Pexo skills repo | https://github.com/pexoai/pexo-skills | Installable skill for Claude Code, Codex, Cursor, OpenClaw |





