Display float

Half of ComfyUI debugging is the same question: "what value is actually on this wire right now?" Numbers are the worst offenders because they all look identical - a 0.5 from a midpoint, a 0.45 from a noise-strength calculation, and a stale default you forgot to change are visually indistinguishable. LF_DisplayFloat answers the question for floats: it takes a float, shows it on the node body, and passes it through untouched.

It's the float entry in the LF Nodes display trio (with LF_DisplayBoolean and LF_DisplayJSON), and like them it's an output node - you put it at the end of a branch to read the value, not to process it. Wire in any FLOAT source - a math result, a CFG value, a strength that's being driven by an animation schedule - and the number renders right on the canvas after the run.

Why it's worth having

Floats sneak into workflows from more places than you think: samplers, schedulers, LLM JSON outputs (via LF_GetValueFromJSON's float output), and LF filter nodes like LF_Blend's opacity or LF_Brightness's strength. When a render comes out unexpectedly dark or a blend looks wrong, the fastest check is "what did that value actually compute to?" This node is that check - no console spelunking, no mentally replaying the math chain.

It also passes the value through, so it doubles as an intentional waypoint: you can tap it off the side of a wire to observe without interrupting the flow, or inline it if you want to be certain the node between two stages is printing what it receives.

What it's not

It doesn't round, format, or convert to text. If you want the float rendered into a filename or a UI note, that's a string-conversion job elsewhere. And like its siblings, it only shows the value after a run - an unexecuted node body is empty, not broken.

Installing it

Part of the LF Nodes pack:

cd ComfyUI/custom_nodes
git clone https://github.com/lucafoscili/comfyui-lf

or ComfyUI Manager → LF Nodes → install → restart. No dependencies, no models. The pack is the frozen legacy repo (development moved to lf-nodes), so this is stable, finished code.

Where people get burned

• Routing a whole pipeline through it out of habit. It's a pass-through, so it works, but you're adding a display hop where a side-tap would do. Learn the tap.
• Expecting precision control. This is a readout, not a math node - for clamping or rounding you need an actual operator.
• Mistaking an empty node body pre-run for a broken connection. Queue once, then read.

Small, dull, and exactly what you reach for when a number is wrong and you can't see it.