FLOAT

A decimal number, with a widget to set it. That's the whole node - the reason it exists as its own thing rather than "just use ComfyUI's built-in float" is that it belongs to the same family as JNComfy's array, math, and conversion nodes, all of which share the pack's own generic-typing and multi-input patches. Wire this into JN_MathOperationArray, JN_FirstActive, or any of the To* conversion nodes and it just works, because it's built for exactly that ecosystem.

JNComfy (jn-jairo/jn_comfyui) is a one-person pack that spans audio, face restoration, sampling tweaks, and this family of small primitives. There's no real community footprint for it anywhere - it's a personal toolkit that happens to be public, so what's here and in the README is the whole story, not the tip of a bigger conversation.

How it works

Set value and the node outputs it as a FLOAT, unchanged. It defaults to 0, steps by 0.01 in the UI widget, and the min/max bounds are enormous - roughly ±1.8 × 10¹⁹, which is to say effectively unbounded for anything you'd actually generate with. Don't spend time worrying about the ceiling; you're not going to hit it.

Where this differs from typing a number directly into a sampler's own widget is that it's a standalone, wireable value - set it once and fan it out to several downstream nodes (a resize target used in two places, a denoise strength shared by two samplers) instead of typing the same number twice and having them drift out of sync when you tweak one and forget the other.

The inputs and outputs that matter

• value (required, FLOAT, default 0) - the number.
• Output: FLOAT - the same value, passed out.

Installing it

ComfyUI Manager: search "JNComfy". Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/jn-jairo/jn_comfyui

Restart ComfyUI. No models, no dependencies - it's a number widget.

Common issues & troubleshooting

You need it clamped to a specific range (CFG scale, denoise strength, whatever). This node's own min/max are effectively unlimited - it won't stop you typing in a nonsense value. Whatever node actually consumes the output (your sampler, your scheduler) enforces its own tighter range on its side; this node isn't where that validation happens.

The 0.01 step feels too coarse or too fine. That's a UI convenience for dragging the widget, not a hard constraint on the value itself - if you're driving this node's value from another node's output rather than typing it by hand, the step setting doesn't apply at all.

You're not sure whether to use this or ComfyUI's own FLOAT primitive. Functionally they're close to interchangeable for a bare number. Reach for this one specifically when it's feeding other JNComfy nodes in the same graph - the payoff is consistency within the pack's own ecosystem, not some hidden extra capability in the widget itself.