Using Attribute Nodes with the Blender Node Attribute List Add-on

What will you learn in this guide?

In Blender’s Geometry Nodes and Shader Nodes, attributes let you use geometry-related data across nodes. Finding the right entry and adding the appropriate node when using a named attribute can take time. The Node Attribute List add-on on Blender Extensions aims to streamline this workflow. Its Named Attribute List panel displays available attributes and lets you add the relevant nodes.

This guide explains what data the panel lists, how to add Named Attribute and Store Named Attribute nodes, and what Blender attribute types and domains mean. We’ll also cover the limits of transferring anonymous attributes to different geometry and the points to check in architectural visualization workflows.

Requirements

• A scene in Blender where you can work with Geometry Nodes or Shader Nodes.

• The add-on listed as “Node Attribute List” on Blender Extensions. The source page gives the date 12 July 2026 for the listed 2.11.0 version; this is reported as the listing information for that add-on version.

• According to the add-on page, no special permissions are required. The sources don’t provide information about the price, account requirements, or minimum supported Blender version.

The add-on page gives the panel location as “N-Panel-Node-Named Attribute List.” Named Attribute List is the add-on’s panel/menu; the add-on itself is called Node Attribute List. The page also notes that the menu may sometimes fail to open via the shortcut and that the active object selection can affect this. So if the shortcut doesn’t work, check the active object; the sources don’t guarantee compatibility with a specific Blender version.

Step-by-step guide

1. Identify what the attributes represent

The Blender manual uses attribute as a general term for data associated with elements in a geometry data block. A vertex can hold a number or vector, while a face’s material slot can be specified by an integer. Nodes in Geometry Nodes can read or modify these values.

Attributes can be named or anonymous. Named attributes can also be used in areas such as shaders, painting, and UV mapping. Anonymous attributes have no name; they’re carried through connections in a Geometry Nodes network. When using the Node Attribute List panel, distinguish between the named entries it lists and anonymous data within the network.

2. Open the Named Attribute List panel

According to the add-on description, the panel is in the Node section of the N-Panel and is called Named Attribute List. The add-on can be used in Geometry Nodes and Shader Nodes. The panel can display available named attributes, as well as vertex groups, UV maps, Color Attributes, and Object Attributes.

When selecting an entry, check not only its name but also its data type and the geometry element it’s associated with. Blender’s attribute search can show domain and data type information. The domain indicates which elements the data is associated with, such as points, edges, faces, or face corners. The data type indicates what kind of value is stored on those elements, such as a number, color, or vector.

3. Add a Named Attribute node

A regular click in the panel adds a Named Attribute node. This node can be used to read a named attribute for use in the network. Selecting a name from the list instead of typing it manually can reduce typos, especially with long or frequently reused names.

The add-on page lists the 2 and Shift+2 shortcuts for Named Attribute List. If the menu doesn’t open, check the active object selection; the developer says the issue may be related to object selection. The source doesn’t describe a definitive fix or a method that will produce the same result in every setup.

4. Add a Store Named Attribute node

Shift-clicking in the panel adds a Store Named Attribute node. This node is used in workflows that store named attributes on geometry. When choosing a name for the entry, also check for potential conflicts with existing names. According to the Blender manual, if attributes of different types share a name, only one of them may be accessible in Geometry Nodes.

The add-on also provides the Ctrl+2 shortcut to quickly add a Named Attribute node corresponding to the selected Store Named Attribute node in Geometry Nodes. Select the Store Named Attribute node first, then use the shortcut. This function is specified for Geometry Nodes; the source doesn’t explain whether the same shortcut behavior applies in Shader Nodes.

5. Verify the data type and domain

The Blender manual describes attribute types such as Float, Boolean, Integer, Vector, and Color. Domains include Point, Edge, Face, Face Corner, Spline, and Instance. For example, position is a vector attribute on the Point domain, while UV data may be associated with face corners.

Geometry Nodes can automatically convert some types and domains. According to the manual, when converting from Float to Vector, the same number is applied to each vector component; when converting from Vector to Float, the components are averaged. Boolean data uses specific selection rules when converted between domains. So if you get an unexpected result, check the type and domain as well as the node connection.

Use in architecture and visualization workflows

In architectural models, attributes can be part of workflows for evaluating values associated with geometry elements in procedural networks, reading named data on the shader side, or storing data on geometry. The Node Attribute List panel can help locate existing vertex groups, UV maps, and Color Attributes. Reducing the need to type frequently reused attribute names can be a practical convenience in complex node networks.

However, the add-on doesn’t guarantee that data is generated correctly or automatically transferred between different geometry. According to the Blender manual, anonymous attributes can be preserved and interpolated during geometry changes when their connections remain accessible, but they can’t be directly attached to independent geometry generated from a different source. Nodes such as Sample Index or Sample Nearest Surface can be used for this kind of transfer. When combining architectural assets, verify data transfer and the resulting materials separately.

Common mistakes

• Ignoring name conflicts: If different entries, such as a vertex group and a UV map, share a name, only one may be accessible in Geometry Nodes. Use distinctive names.

• Overlooking the domain: An attribute may be associated with points, faces, or face corners. Blender may apply a conversion when it’s used on another domain.

• Looking for an anonymous attribute in the list: Anonymous data has no name; it’s carried through connections within Geometry Nodes.

• Expecting direct transfer to separate geometry: Don’t assume anonymous attributes will automatically transfer between geometry from different sources. If needed, consider the sampling nodes mentioned in the manual.

• Assuming the shortcut will always work: The add-on page says the menu may sometimes fail to appear and that the active object selection can affect it.

Next steps

Start with a small test geometry: select an attribute from the panel and add a Named Attribute node to use it in the network. Then inspect the data’s domain in Blender’s Spreadsheet Editor; the manual recommends this editor for identifying domains. When you create a new entry with Store Named Attribute, check its name, data type, and domain as well.

For projects shared within a team, use consistent attribute names and preserve the geometry connections the node network depends on. The add-on page lists some ideas in its to-do list, such as changing the attribute names of selected nodes with a single click; don’t treat these as existing features. It’s also useful to test the add-on in the Blender setups used by your team and with the relevant shortcuts before including it in a production file.

Sources and license

The Node Attribute List add-on page on Blender Extensions (K2) was used for information about the panel’s use, location, and shortcuts. The Attributes section of the Blender User Manual (K1) was used for attribute types, domains, and transfer limits. K1 is adapted into Turkish from open content licensed under CC BY-SA 4.0.