Qwen-Image-3.0-Pro

Qwen-Image-3.0-Pro is the sibling you pick when the base Qwen-Image-3.0 output isn't quite holding up - Alibaba's step-up tier of the same text-to-image model, served the same way: your prompt goes to Runware's cloud, a bigger model does the work, and a native ComfyUI IMAGE comes back. If you already understand the base node, you understand this one, because the widget set is deliberately identical. The difference is entirely behind the API.

That sameness is the feature, honestly. Cloud model tiers like this exist to let you A/B the same workflow against two price points without rebuilding anything. You build your graph once, wire this node or its non-Pro sibling in, queue the same seed and prompt, and compare. When one gives you the composition and the other doesn't, you learn something real about where the model's quality budget went - and you get to decide whether the Pro per-call rate is worth it for your subject matter, which is the only test that matters.

Everything in the base article's input list applies unchanged: the required positivePrompt (write sentences; Qwen's encoder is an LLM, not a tag matcher), referenceImages for subject or style reference, a genuine negativePrompt, width/height at a 1024 default, seed, numberResults for variations, and the watermark and safety groups underneath advancedFeatures. providerSettings.alibaba.promptExtend is on by default and rewrites your prompt through an LLM to beef it up - the tooltip is upfront that it "affects reproducibility," so turn it off when you're iterating on a seed and it won't hold still. The one output is image, straight into Preview Image or Save Image.

Install

Same pack, same one-time setup as every Runware node: search Runware in ComfyUI Manager and install, or git clone https://github.com/Runware/ComfyUI-Runware into ComfyUI/custom_nodes and pip install -r ComfyUI-Runware/requirements.txt. Restart, then give the pack your key from the Runware dashboard - ComfyUI Settings → Runware API key, a RUNWARE_API_KEY env var, or runware auth login once. There are no checkpoints to download; the only real dependency is the runware-sdk.

The practical read

Don't overthink tier choice. Run the base node first; it's cheaper and often close enough for drafts and iteration. Reach for Pro when a hero image has to carry the job - client work, a thumbnail that needs to sell, something you'll look at for weeks - and the base version comes back with a tell you can name: wrong anatomy, muddled text, a composition that just misses. Because the node reports per-run cost on its title bar, you'll get immediate feedback on what the upgrade actually costs you. Two reminders: your prompt and reference images leave the machine and pass through Runware's moderation (there's no local fallback for this model - it doesn't have open weights), and if a queue fails, check the API key before you blame the model.