Color Input (RMBG) 🎨

Color Input is the smallest node in the pack and it does exactly one thing: it outputs a color. You either pick from a list of named presets or type a value, and it hands a color code downstream to anything that takes one - most obviously the background_color input on all the RMBG and Segment nodes. It exists so you can define a background fill color once and feed it to several nodes, or drive it from the rest of your graph, instead of retyping a hex code into every remover separately.

That's the whole mechanism - no model, no processing, it's a value source. Think of it as a labeled constant for colors. The reason a dedicated node beats just typing #FFFFFF into each background_color field is reuse and control: wire one Color Input into three background removers and they all share a fill you can change in one place; or swap the color programmatically if you're batching outputs against different backgrounds.

The inputs: preset is a dropdown of 26 named colors - black, white, red, green, blue, yellow, cyan, magenta, gray, silver, maroon, olive, and more - for when you just want a standard color without hunting for its hex. color is a free-text field for a custom value when none of the presets fit; type your own code here. The single output is COLOR (a color code), which plugs into any background_color or color-typed input across this pack and beyond. It's a one-in, one-out convenience node.

Install rides along with the pack - there's no separate step and nothing to download: "Comfyui-RMBG" in ComfyUI Manager, or cd ComfyUI/custom_nodes && git clone https://github.com/1038lab/ComfyUI-RMBG, then pip install -r requirements.txt and restart.

Practical notes. Most of the background and segment nodes already have a background_color widget built in, so you don't need this node for a one-off - just type the color there. Color Input earns its place in two situations: when you want the same color shared across multiple nodes (define once, wire to all), and when you want a clean, named source in a graph you'll reuse or share, so the color is an obvious labeled node rather than a value buried in a widget. Between preset and color, use the preset for standard colors and the text field for a specific brand or custom shade. If both are set, treat the custom color field as your explicit override and leave it blank when you want the preset.

Where it fits: it's plumbing. Nobody installs the pack for this node - the near-zero search interest says as much - but in a tidy, reusable background-removal graph it's the little piece that keeps your fill colors consistent and adjustable from one spot. Pair it with the RMBG, BiRefNet, or Segment nodes by dragging its COLOR output into their background_color input, set background to Color on those nodes, and you've got a single dial controlling the backdrop for the whole workflow. Small node, real convenience once your graph gets big enough that repetition becomes a nuisance.