SP_Name_StyleModel

A style model is a smaller companion file used to transfer the look and feel of a reference image into a generation - Flux Redux is the current name most people will recognize this from, part of the official "Flux Tools" suite. SP_Name_StyleModel doesn't apply one; it picks a filename from your style models folder and returns it as plain text, the same lightweight pattern as the rest of this pack's SP_Name_* family.

Why you'd want just the name

Style-transfer setups tend to get compared a lot - different style model checkpoints, or the same one at different strengths, applied to the same reference. If you're batching through a few variants, this node lets you record which style model actually produced a given output without the cost of loading it, or use the choice to drive other logic in the graph (a switch, a conditional branch, a log entry). It's a small convenience, but it's the difference between a batch of self-documenting outputs and a folder of images you have to reconstruct the settings for by memory.

Inputs and outputs that matter

• name - a dropdown populated from your style models folder.
• Output: STRING - the selected filename.

How to install it

Through ComfyUI Manager: search "SP-Nodes," install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/bananasss00/ComfyUI-SP-Nodes

Restart ComfyUI once it's cloned. No extra dependency for this node itself.

Common issues & troubleshooting

Dropdown is empty. Style models are a smaller, less commonly pre-installed category than checkpoints or LoRAs - if you haven't specifically downloaded one (Flux Redux being the obvious current example), there's nothing here to pick from yet. Download one into the folder ComfyUI expects for style models and restart.

File exists but isn't showing up. Same startup-scan behavior as the rest of this pack - anything added after ComfyUI launched needs a restart before it appears in the dropdown.

Mixing this up with the actual style-transfer pipeline. This node only ever returns a filename string - it never loads the style model and never touches conditioning. The real style-transfer chain (a Style Model Loader plus whatever apply node your workflow uses, feeding into conditioning alongside a CLIP Vision-encoded reference image) still has to exist separately in your graph if you want the effect itself, not just its name recorded somewhere.

Effect seems too strong or too weak and you're not sure if it's the style model's fault. Style models like Redux are typically applied at a strength you control on the apply node, not on this one - if results feel off, check that setting before swapping style-model files entirely; a strength tweak is usually the faster fix.