Blender 5.0 introduces a redesign of the socket shapes used in Geometry Nodes, a change announced on August 8 2025 by the Blender development team. The previous system relied on three shapes – circle, diamond, and diamond‑with‑dot – to convey whether a socket held a single value, a field, or a field‑compatible value. While functional for earlier use‑cases, the design proved limiting for upcoming data structures such as lists and volume grids.
New shape semantics
- Vertical bar: Represents a single value input or output that never changes type.
- Diamond: Indicates a field‑type input or output.
- Circle: A flexible shape that can accept or produce single values, fields, lists, or other structures depending on the node’s context.
- Grid/list shapes: Experimental shapes (still in development) that will behave like the diamond for fields, enabling future support for volume grids and lists.
The redesign removes the dynamic shape‑changing behavior that previously occurred when sockets were linked. The only exceptions are group input and output nodes, which may still infer shapes automatically, though authors can override them when needed.
Impact on existing nodes
- The Math node now uses circle sockets, signalling that it can work with any supported data structure.
- The Triangulate node’s selection input is a field, while its other inputs remain single values.
- The Set Position node’s field inputs now share the same diamond shape, eliminating the previous visual distinction between “expects a field” and “currently a field”.
- The Cube node outputs a field despite having only single‑value inputs.
Dashed links continue to indicate potential field propagation, providing an extra visual cue that complements the static socket shapes.
Why the change matters
The old socket system blocked the implementation of volume grids and list handling because there were no suitable visual representations. By redefining the shapes, Blender developers have cleared a major roadblock, allowing volume grid support to move forward and opening the path for list‑based workflows.
Beyond Geometry Nodes, the new shapes are expected to appear in other node tree types. Early experiments include using the circle shape in the compositor to differentiate single‑value inputs from image inputs, and discussions about bringing field support to compositor nodes.
While some legacy information (e.g., whether a socket originally contained a field) is no longer shown directly on the shape, the design team plans to surface it through tooltips and optional overlays if user feedback shows a need.
Overall, the socket shape redesign is a trade‑off: it sacrifices a few visual details to gain scalability for future features, a compromise the Blender team deemed necessary for continued growth of Geometry Nodes.