Blender educator Andrew Price posted a short demo. He links to a pull request in Blender’s repository, suggesting a behind-the-scenes development is already underway.The post is sparking buzz in the community about templated workflows inside node systems.
The Pull Request: 145645
The repository for Blender includes PR 145645, which appears to correspond to this “preset” feature.That pull request is listed under the Blender project’s “pulls” section and is the link Price points to in his demo post. However, at the time of writing, the PR’s content is not fully clarified in external discussions or linked documentation. The exact scope, implementation detail, or whether it will be accepted are still open questions. The presence of this Pull request lends weight to Price’s teaser, but it does not serve as final confirmation of the feature’s inclusion or form.
Recent Node Work in Blender 4.x
Blender’s recent releases have already shown movement toward more unified and flexible node workflows. In the Compositor’s release notes for version 4.5, Blender added support for texture nodes like Noise, Voronoi, and Gradient, bringing parity with Shader and Geometry node systems. New nodes including Image Info, Image Coordinates, and Relative To Pixel were introduced into the compositing context. Some older nodes or options were deprecated in preparation for removals in 5.0. These changes reduce the gap between node domains (shader, geometry, compositor), which makes a “preset” system more plausible from an architectural standpoint.
What Node Presets Could Mean — And What Isn’t Yet Clear
If a built-in preset system for geometry and compositing nodes does arrive, users might be able to start from high-level templates—common node patterns, starting layouts, or macro combinations—rather than building everything from scratch each time. Such presets may encourage consistency across projects and for teams.
At present, key details remain unknown: whether presets will be defined as node groups, templates, macro nodes, or some new structure; how users will manage them; and how backward compatibility or migration paths will be handled for existing scenes.
