RedNode Studio Preset Load

RedNode Studio Preset Load does one small thing, and it's worth knowing about even though you'll use it less than the node it feeds. It hands you a Krea 2 settings bundle - the whole stack of knobs that controls how references behave - from a named preset, as a reusable object you can wire around. Think of it as a Primitive node that holds a recipe instead of a number.

The presets are the same seven you've seen on the main studio node: Balanced, Max identity, Style only, Outfit transfer, Pose transfer, Anime to real, Real to anime, plus anything you've saved yourself. Output is a single settings socket of type KREA2_SETTINGS. Where does it go? Into the studio node's settings input, after you set that node's preset to "custom (use settings)". That's the hand-off: the preset dropdown on the studio is the quick way, this node is the programmatic way. Wire it up and you can swap an entire identity/style configuration by changing one dropdown here instead of re-dialing a settings panel.

The mechanism is boring in the good way. The node looks up the name in the built-in preset table or in your saved presets, which live as JSON in the ComfyUI user directory, and emits the dict. It also prints the full value dump to the console when it runs, which the author clearly intended as a learning aid - run it once and you get a plain-English list of every setting the preset carries. Because it watches the saved-presets file's modification time, newly saved presets get picked up without restarting ComfyUI.

A couple of gotchas, both inherited from how the pack stores presets. A saved preset that shares a built-in's name is shadowed by the built-in - rename it via Preset Save. And a fresh save won't show up in the dropdown until you refresh node definitions (press r on the canvas). Neither is a bug, they're just the pack's refresh contract, and the tooltips say both out loud.

When should you reach for this over the studio's own dropdown? When the preset needs to come from somewhere else - driven by a Control Panel row, saved in a scene, or selected by another node. For a static workflow, the built-in dropdown is fewer clicks and less to trace. This node earns its place the moment your workflow starts deciding its own look.

Installation is just the pack. Search RedNode Studio in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/RedNodeAI/ComfyUI-RedNodeStudio.git

Restart ComfyUI and you're done - no pip dependencies. This node is part of the Krea 2 half of the pack, so it also needs a ComfyUI build with native Krea 2 support (0.26.0 or newer) plus the qwen3vl_4b text encoder loaded through a CLIPLoader with type krea2, and qwen_image_vae. If that stack is missing, the Krea 2 nodes simply don't register; the rest of the pack still loads.