Ino Int To Float

Every ComfyUI regular knows the feeling: you compute an integer - a batch count, a width, a step number - and the node you're feeding refuses it because it wants a float. Ino Int To Float is the one-node answer: an integer goes in, the same value as a float comes out. That's the whole node, and honestly that's all it needs to be.

It's part of the Ino Nodes pack from nobandegani, built on ComfyUI's newer V3 schema. It's the quiet sibling of Ino Float To Int in the pack's casting family, and it exists because ComfyUI's type system is pickier than your patience.

What it does

One input, input_int (an INT, default 0). One output, float (a FLOAT). The conversion is exact - 7 becomes 7.0 - no rounding, no surprises, no options to configure. If you need the reverse trip with control over rounding, that's the separate Ino Float To Int node with its round/floor/ceil methods; this one is pure and simple.

When you'd use it

The realistic triggers: a node upstream computes a dimension or count as an INT, and a downstream node's widget only accepts FLOAT. Or you're feeding an integer through a math node that expects floats on both inputs. It's also handy as a type-normalizer: if you're mixing values from several sources into one path, converting everything to float first keeps the types consistent so a single path handles all of them.

It's the kind of node you might install a whole pack for and use once a month - and when that month comes, you'll be glad it's there instead of reaching for a cast-any node that drags a giant UI along for a one-value job.

Installing it

It ships with the whole Ino Nodes pack. ComfyUI Manager: search "ComfyUI Ino Nodes", install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/nobandegani/ComfyUI-InoNodes.git
cd comfyui_ino_nodes
pip install -r requirements.txt

Restart after. Pack-wide caveats apply: it's built on ComfyUI's V3 schema (README wants v0.18.1+), and requirements.txt installs inopyutils, the helper library every node imports.

Common issues

There's genuinely little that can go wrong here - it's a lossless type conversion. One thing to keep in mind: if you feed it a value that's already a float (via loose typing), treat the output as authoritative, since some graph setups smuggle floats into INT ports. And if a downstream node still complains about types after this, the problem is elsewhere in your wire, not here. Search "Ino Int To Float" in the node menu (grouped under InoIntHelper).