FL Color Picker

Sometimes you just need to pick a color and hand its hex code to another node - a background fill, a text overlay, a padding color, a gradient stop. Typing #3A7BD5 from memory is nobody's idea of fun. FL_ColorPicker gives you a visual swatch to click, and outputs the hex string you chose. That's the whole node, and that's the whole appeal.

It's a small convenience utility, sitting in the pack's experiments category. No cleverness, no processing - just a nicer way to choose a color than guessing hex values, and a clean string output that plugs into anything expecting a color. In practice you'll wire it into things like a text-overlay node's color field, a blank-canvas or padding color, or a gradient stop - anywhere a node reads a color as a hex string and you'd rather see the color than type its code.

How it works

The node presents a color widget. You pick a color, it stores the hex value, and it passes that hex string straight through to its output. Input equals output - it's a pass-through whose real job is the picker UI, not any transformation.

The inputs and outputs

• selected_color - the chosen color, a hex string (default #FF0000, i.e. red). This is what the picker widget sets.

Output is a single STRING - the hex value - ready to wire into any node that takes a color as a string.

How to install it

Part of filliptm's Fill-Nodes pack. ComfyUI Manager → search ComfyUI_Fill-Nodes → Install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/filliptm/ComfyUI_Fill-Nodes
pip install -r ComfyUI_Fill-Nodes/requirements.txt

Nothing extra - it's a UI widget plus a string.

Common issues & troubleshooting

The downstream node doesn't accept it. The output is a hex string. That's perfect for nodes that want a color as text (many overlay, background, and gradient nodes do), but some nodes want separate R/G/B integer inputs, or a different color format entirely. If the connection won't take or the color comes out wrong, check what format the receiving node actually expects - this node speaks hex strings and nothing else.

My node wants a color but has no string input. Then it's not designed to take a piped color, and this picker can't help - it can only feed nodes that accept a color value on a string input. Plenty do; some don't.

It's genuinely trivial - and that's fine. Don't overthink this one. It's a swatch that emits a hex code so you don't have to type one. If your workflow never needs to hand a color to another node, you'll never need it; when it does, it's a two-second quality-of-life win.