Node Group Presets
What is NodeGroupPresets?
NodeGroupPresets is an addon that saves the current values of a given nodegroup into a applyable/editable/copyable preset. Quite useful when building a verstaile node library taking away the bothersome workflow of either copy/pasting multiple values from different instances of a nodegroup or "hardcoding" presets into it's own nodegroups.
Features
The main features of this addon are:
- Save/Apply presets
- Update presets with current status
- Edit presets, add/removing sockets or changing its name/value
- Copy/Past presets from different nodes or files
Save/Apply Preset
Saves supported sockets values/subtype/max&min limits.
Single click: Full saveShiift + Click: Partial save
Update Preset
Update values with the node's current values If socket order changes, you can update the preset order with it
Edit Preset
Change values
Change socket values, name from the active preset
Add/Remove sockets
Add or remove sockets from the active preset. Adding has the same Non-shift`Shift` behaviour when saving presets
Copy/Paste Preset to/from clipboard
You can copy/paste presets from different nodegroups, even if they are in different files! Under the hood it copies a JSON dictionary to the clipboard.
Caveats
Unique Path [panel name + socket name]
It will only work properly if all socket paths (panel name + socket name) are unique. Meaning, sockets can have the same name as long as they are not in the same panel (base level included).
Same socket type
If socket name changes to a non convertable type, it will ignore it. To make it work again, remove said socket and add it back (update not resolving it automatically seems like a safer option)
Supported Sockets:
- Bool
- Color
- Float
- Int
- Rotation
- String
- Vector
What's New
0.8.0 January 16th, 2026
Commit History: https://codeberg.org/juaum/bpy_nodegroup_presets/compare/0.7.1...0.8.1
Notable Changes:
- Add support for Vector2D and Vector4D sockets
Simply awesome!!! Is it possible to apply a preset to multiple node groups at once? When multiple node groups selected, the preset only applies to an active node group.
I really like this extension and it adds a feature to Blender, which I think should be integrated by default! I'd like to suggest adding the option to save presets in another way than inside the data-block. Maybe even saving them as a separate .txt/.xml-file or whatever. Because in my case: I provide a library of node-groups using Blenders Asset Browser. This extension fundamentally works well with this, as the list of presets will load when adding the node-groups. So it is great from a creator-perspective! But as the perspective of an user, who wants to create and manage their own custom presets, there is currently no flawless solution to save them, as the asset browser will by default just append them and not write changes into the file. Of course the asset browser can be set to link assets instead of appending them, or users could create them in the .blend of the asset library source. But when updating an asset library, the .blend-file will usually be overwritten, which would then also overwrite all custom presets made by the user, even if the update doesn't affect all node-groups.