wan / v2.5 / fal / text-to-image

Wan 2.5 is where the open-source story ends and the cloud story begins. Alibaba shipped it as a cloud preview in September 2025 with an "open weights will release soon" disclaimer, never released the weights, and did the same with 2.6 and 2.7 after it. There is nothing to download, no checkpoint, no local run - the search results promising "Wan 2.5 open source guide" are content-farm spam with dead links. So this node is the only way Wan 2.5 enters your ComfyUI graph: as a cloud recipe on the fal engine behind Civitai's Orchestration API, billed in Buzz.

That flips the framing from the 2.2 nodes. There, you were paying for convenience; here, you're paying for access to a model that has no other door. The community reaction to the whole closed turn was "muted at best, hostile at worst," so don't expect this to be a fan favorite - but it does what it does.

Inputs and outputs

• prompt (required) - that's it for required.
• guidance_scale - 3.5 default, same as the 2.2 siblings.
• steps - no explicit default knob here (the 2.5 recipe controls steps server-side); what you get is image_size (preset string, square_hd), enable_prompt_expansion, enable_safety_checker, loras, negative_prompt, seed, quantity (up to 12), output_format, image_metadata.

The notable absence compared to the open 2.2 nodes: no shift, no acceleration, no step control. The closed-weight recipe hides the two-pass internals - you tune at the API's pace, not the model's. Outputs are the pack's standard images (IMAGE), errors, workflow_id, raw_json.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/civitai/civitai-comfy-nodes.git
pip install -r civitai-comfy-nodes/requirements.txt

Or ComfyUI Manager → "Civitai Comfy Nodes" → Install → restart. Authenticate (CIVITAI_API_TOKEN or the sidebar connect panel) - without it, nothing runs.

Gotchas

Set expectations from the community's own verdict: 2.5 was read as "an upgrade to 2.2," and the series after it got rougher reviews - 2.6 "looked like straight dog shit" and 2.7 worse, in the most-quoted take. These are still-image and video models where the closed turn left quality roughly flat while the price went up. So the practical question isn't "is 2.5 good" - it's "is 2.5 good enough to justify Buzz over running 2.2 free," and for most still-image work the answer is no. This node is the right tool if you specifically want 2.5 (newer recipes, ecosystem compatibility with other cloud Wan tools). It's the wrong default if you just want a Wan still - run 2.2 locally if you can, or use this pack's v2.2 nodes, and keep the Buzz.