Nodes/ComfyUI_StarNodes/⭐ Star Save Sampler Settings
ComfyUI Node

⭐ Star Save Sampler Settings

Star Save Sampler Settings — make your best sampler configs reusable

By Starnodes2024·Created 2 years ago·Updated 2 days ago· 106
⭐ Star Save Sampler Settings
  • sdstar_settings
  • fluxstar_settings
  • message
settings_nameMy Settings

You spent an afternoon dialing in the perfect sampler config for a character - the scheduler, the CFG, the steps, the LoRA stack - and then you rebuilt a workflow and had to type it all back in from memory. Star Save Sampler Settings exists so you never do that again. It takes a settings bundle from the StarNodes sampler family, gives it a name, and stores it as a named preset you can reload later with Star Load Sampler Settings or delete with Star Delete Sampler Settings.

How it fits the ecosystem

This is one of those nodes that looks pointless in isolation and only makes sense once you see its friends. The StarNodes pack ships a family of "start" nodes - Star SD(XL) Start(t) Settings, Star FLUX Start(t) Settings, Star Qwen Image Start(t) Settings - plus the big StarSampler (Unified) node. Those nodes carry a bundle of settings around with them (SDSTAR_SETTINGS for the SD/XL family, FLUXSTAR_SETTINGS for the Flux family). This node's job is to capture that bundle and persist it.

So the workflow is: dial in your config on a StarSD settings node, wire its settings output into Star Save Sampler Settings, give it a name, and run once. From then on, Star Load Sampler Settings can resurrect that exact config in any workflow. It's presets for the settings nodes, in the same way ComfyUI workflows themselves are JSON files you can archive.

Inputs and outputs

  • settings_name - the name of the preset, default "My Settings". This is the key under which it's saved.
  • sdstar_settings (optional) - the settings bundle from the SD/XL start nodes or StarSampler.
  • fluxstar_settings (optional) - the Flux-family bundle.
  • message (STRING, output) - what happened: a success message, a serialization error, or "No settings provided to save" if you connected nothing.

The node saves whichever bundle you connected - it handles both types, one per run. The Flux path notably JSON-serializes any non-primitive values before storing, so weird nested settings don't blow up the save.

Installing

Part of the StarNodes pack:

cd ComfyUI/custom_nodes
git clone https://github.com/Starnodes2024/ComfyUI_StarNodes
cd ComfyUI_StarNodes
pip install -r requirements.txt

Restart, search star under ⭐StarNodes/Settings. ComfyUI Manager users can search "Starnodes".

Gotchas

The trap is the same one as every settings-saver: it saves whatever you hand it, so if you connect a bundle after tweaking values on a node that hasn't recomputed, the saved config may be stale. Re-run the source node once after your final tweak before saving. Also note it saves a single settings bundle type at a time - if you want both an SD and a Flux preset, run it twice with different names. And the message output is plain text, so it's not a data pipe; you're using it to read, not to wire onward.

Category⭐StarNodes/Settings

Inputs (3)

NameTypeDefaultDescription
settings_nameSTRINGMy Settings
sdstar_settingsoptSDSTAR_SETTINGS
fluxstar_settingsoptFLUXSTAR_SETTINGS

Outputs (1)

NameTypeDescription
messageSTRING