Color Convert (Legacy)

Every pack in the ecosystem wants colors in a different shape. One node's "color" input is a #RRGGBB string, the next wants a single integer like 16711680, and a third wants 255, 0, 0. Color Convert (Legacy) is the glue: you give it a color once, and it hands you all three formats so you never convert by hand again.

Mechanically it's about as simple as a node gets. You pick a color in the picker (or type it in one of three formats), and it validates and converts internally, emitting the hex string, the 0–16777215 integer (which is the RGB bytes packed as 0xRRGGBB), and the comma-separated r, g, b string. Pure CPU math, no model, runs in microseconds.

The inputs that matter

• from_mode - auto plus three explicit modes: Manual Hex #FFFFFF, Int 0-16777215, and Comma separated 255,255,255. In auto, the node uses whatever manual input is actually filled in, falling back to the color picker if nothing (or too many things) is valid. The explicit modes force their field and raise a clear error if you feed it garbage.
• color_hex - the color picker. This is what you'll use 90% of the time: auto mode plus a picker click.
• manual_hex / color_int / comma_separated - the three manual alternatives, all optional. Use these when the color is coming from somewhere else in your graph - a value node, a prompt preset, a saved workflow - rather than from your eyeballs on a swatch.

The outputs

Hex (#FF00FF), Int (e.g. 16711935), and RGB (255, 0, 255). The pair you actually care about depends on what's downstream. Text-overlay, background-fill, and gradient nodes usually take the hex string; some color-math or palette nodes take the integer; anything with three separate channel inputs wants the RGB string split up.

Installing it

Ships in silveroxides/ComfyUI-UtilsCollection. ComfyUI Manager → search ComfyUI-UtilsCollection → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/silveroxides/ComfyUI-UtilsCollection

Then restart. Dependencies are just opencv-python and typing-extensions, both near-universal already. The "(Legacy)" tag means it's a compat alias for the pack's newer UC_ColorConvertNode - old workflows load under this id, and the newer name is what shows up in the menu for fresh graphs.

Where people get burned

Two things. First, color_int defaults to -1, which the node treats as "not filled in" - so if you convert a widget to an input and leave it disconnected, it silently ignores it and falls back to the picker. That's intentional, but it means a stray 0 is not ignored: 0 is a valid color (pure black), and it will win over the picker in auto mode. Second, the integer format is 0xRRGGBB order, so 16711680 is red, not blue - the exact thing everyone gets wrong once. If a downstream node gives you an int that "looks wrong," suspect byte order before you suspect the node.