Number to Float

WAS's number nodes - Number Operation, Constant Number, Number PI, Random Number and the rest - mostly pass around a generic NUMBER type that's loosely int-or-float depending on what produced it. That's convenient inside WAS's own ecosystem, but plenty of nodes outside it, including some of ComfyUI's own native widgets and other packs' inputs, are strict about wanting an actual FLOAT socket, not WAS's looser generic type. Number to Float is the explicit converter that closes that gap: feed it a NUMBER, get back a proper FLOAT.

Why the conversion has to be explicit

ComfyUI generally doesn't do silent type coercion across genuinely distinct socket types - if a node declares it wants FLOAT and you try to plug in something typed differently, you get a connection that won't wire up rather than a friendly auto-cast. That's true across the ecosystem, not just WAS. So the moment you've computed a value inside a WAS Number Operation chain and want to hand it to something that specifically demands FLOAT - a denoise strength, a CFG scale, a strength slider on a LoRA or ControlNet node - Number to Float is what bridges the gap rather than leaving you stuck with an invalid connection.

How it works

It's a straight type conversion: takes the NUMBER input and outputs the same value as a FLOAT. No math, no scaling, no clamping - the value itself doesn't change, only the socket type it's wrapped in.

The inputs and outputs that matter

A NUMBER in, a FLOAT out. Its sibling, Number to Int, does the same job in the opposite direction for nodes that specifically want a whole number. Between the two, they cover the two type demands you'll actually run into downstream of a WAS number chain.

Installing it

ComfyUI Manager: search "WAS Node Suite," install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui

install requirements.txt against your ComfyUI Python, restart. No model, no dependency specific to this node.

Common issues & troubleshooting

The downstream node still won't accept the value. Double-check it actually wants FLOAT and not INT - plugging a converted float into a strictly integer socket fails the same way an unconverted NUMBER would. This node fixes one specific type mismatch, not every possible one.

Precision looks off. If you're chaining several Number Operation steps before converting, small floating-point rounding can accumulate the way it does in any numeric pipeline. If a value downstream looks slightly wrong, print it with a console/debug node right before and after the conversion rather than assuming the bug is here - it's usually upstream in the math, not in the type cast itself.

Nothing shows up in node search. That's almost certainly the whole pack, not this node specifically. WAS Node Suite has been unmaintained since the author marked it retired in December 2023, and the recurring failure since is the entire suite throwing "Import Failed" after a ComfyUI update because a pinned shared dependency got bumped underneath it. Reinstall requirements.txt against the correct, embedded Python interpreter and restart - this node has nothing of its own to break.