Recraft Controls
The free local node that wires palettes into Recraft generation
- colors
- background_color
- recraft_controls
Recraft Controls is another one of those ComfyUI nodes where the name oversells the node itself: it doesn't call Recraft's API, doesn't cost credits, and doesn't generate anything. It's a local aggregator that takes color values and packages them into a RECRAFT_CONTROLS object - the thing Recraft's actual generation nodes read to apply a palette to your image. Think of it as the adapter between "colors I picked" and "colors the model must respect."
It ships with ComfyUI core like the rest of the partner family, but it's the free plumbing, not the paid machinery. The paid part happens downstream, when the controls you built here get sent along with a generation request.
How it works
Two optional inputs, both typed RECRAFT_COLOR - which is exactly what Recraft Color RGB produces:
- colors - the palette to apply to the generated image.
- background_color - the specific color for the background.
Everything runs locally and instantly, and it just wraps the two into one RECRAFT_CONTROLS output.
The wiring that matters
The recraft_controls output plugs into the recraft_controls input found on the Recraft generation nodes - most usefully Recraft V3 Text to Image (whose tooltip says it plainly: "Optional additional controls over the generation via the Recraft Controls node"). So the standard chain is:
Recraft Color RGB (×n) → Recraft Controls → Recraft V3 Text to Image
Feed multiple Recraft Color RGB nodes into the colors input to build a multi-color palette, then control the background separately.
Where people get burned
- No inputs = no effect. Both inputs are optional, and an empty Controls node does nothing. The node isn't broken; you just haven't given it anything to carry.
- Type mismatch. It only accepts
RECRAFT_COLORinputs. A plain color as an IMAGE or a hex string won't connect - build colors with Recraft Color RGB first. - Free here, paid downstream. Because this node itself never bills, it's easy to forget the generation node it feeds absolutely does. Building the controls costs nothing; running the generation it's attached to costs real credits.
- Controls aren't a prompt override. The palette steers the model; it doesn't guarantee pixel-perfect adherence. Recraft will tend toward the colors, not obey them like a constraint solver.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| colorsopt | RECRAFT_COLOR | — | |
| background_coloropt | RECRAFT_COLOR | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| recraft_controls | RECRAFT_CONTROLS | — |