📊 Slider 1

There's nothing clever going on here, and that's the point. Slider 1 is a bare float widget clamped to 0–1, wrapped as its own node so you can drop a slider handle into your graph instead of typing decimals into a tiny box. If you've ever fat-fingered a denoise strength or a LoRA weight because the default widget makes you click-and-type instead of drag, this is the fix.

It comes from the SDVN Comfy Node pack's "Creative" grab-bag, alongside a matching integer version (Slider 100, covered separately) and, per the pack's own README, a couple of unnamed "custom int/float slider" variants for ranges outside 0–1 and 0–100. Think of Slider 1 and Slider 100 as the two pre-built, ready-to-drag versions for the two ranges people ask for most.

How it works

There's no computation - the node holds one number, you drag it, it outputs that number. The whole value proposition is the UI: a horizontal slider handle is faster to nudge to "about 0.4" than typing 0.4 and hoping you didn't hit an extra zero. That matters more than it sounds when you're iterating fast, or when you've built a workflow for someone else to tweak and don't want them typing raw floats.

Inputs and outputs

• num (FLOAT, required, range 0–1, step 0.05) - the only control. Drag it, or click and type if you need precision the slider can't give you.
• The output socket carries the FLOAT value - a small naming quirk worth flagging so it doesn't confuse you: on the graph it's labeled int, which is almost certainly copy-pasted from Slider 100's code rather than a real type change. Don't let the label fool you; what comes out is a float, and it'll wire cleanly into any FLOAT input (denoise, LoRA/ControlNet strength, blend amount).

Where you'd actually use it

Anything that naturally lives on a 0–1 scale: denoise strength, style/IPAdapter weight, opacity or blend factors, a probability-style toggle you're sweeping by hand. It's a UI convenience, not a functional one - swap it in wherever a plain FLOAT widget is getting fiddly to control precisely.

Common issues

The step size caps your precision. At step: 0.05, you can land on 0.35 or 0.40 but not 0.33 exactly by dragging - you'd have to click into the field and type it. If your workflow genuinely needs finer-grained values, this node's slider convenience works against you; use a plain FLOAT primitive instead.

It's a UI node, not a computation node. There's no failure mode here beyond "wrong range for what I needed" - if you need values outside 0–1, this isn't the one; reach for Slider 100 (0–100 integers) or a standard widget instead of trying to make this one stretch past its clamp.