Nodes/ComfyUI/Recraft Style - Infinite Style Library
ComfyUI Node Runs on cloud

Recraft Style - Infinite Style Library

The niche node for brand consistency

By Comfy-Org·Created 4 years ago·Updated about 20 hours ago· 130,493
Recraft Style - Infinite Style Library
    • recraft_style
    style_id

    Most Recraft style nodes give you a dropdown of curated substyles. This one gives you a text box and expects a UUID. That's because it plugs into Recraft's Infinite Style Library - a repository of community- and brand-created styles that each carry a stable ID. If you've found a style on recraft.ai that you want to reuse across a whole batch of generations, this node is how you point your ComfyUI workflow at it.

    The workflow goes: find a style you like in Recraft's library, copy its style UUID, paste it into style_id, and the node emits a RECRAFT_V3_STYLE object carrying that ID. Wire that into the recraft_style input of any Recraft V3 generation node and you've locked in that exact style - including styles other people created, which is the real draw. Brand style libraries, consistent illustration looks, a designer's shared house style: this is the node that makes them reproducible inside ComfyUI.

    Inputs and outputs

    The whole schema:

    • style_id - string, the UUID from the Infinite Style Library
    • recraft_style out - the RECRAFT_V3_STYLE object for downstream nodes

    That's everything. No substyle dropdown, no style family selector - the UUID carries it all.

    Gotchas

    • Empty input throws. If style_id is blank, the node raises an error rather than silently defaulting. You must paste a real ID.
    • It's only as good as your ID. A mistyped or stale UUID means a style that isn't what you thought. There's no validation in the node itself - the error surfaces at generation time.
    • V3 pipeline only, again. The RECRAFT_V3_STYLE wire only feeds the V3 generation nodes. V4 generation (RecraftV4TextToImageNode) doesn't accept a style object at all.

    Is it worth using?

    If you're a solo tinkerer, probably not - you'd get more mileage from the curated substyle dropdowns. Where this earns its place is any pipeline where a fixed, external style definition needs to be stable across runs and across collaborators. It's also the quiet answer to "how do I get the exact same look every time in Recraft": the UUID is the deterministic part, even though the generated pixels never are.

    Ships with ComfyUI core, no install, no model files, no API call until you connect it downstream. A one-input utility node with a surprisingly specific and useful job.

    Categorypartner/image/Recraft

    Inputs (1)

    NameTypeDefaultDescription
    style_idSTRINGUUID of style from Infinite Style Library.

    Outputs (1)

    NameTypeDescription
    recraft_styleRECRAFT_V3_STYLE