Named Attributes in Blender Geometry Nodes: A Step-by-Step Guide

What you’ll learn in this guide

Geometry in Geometry Nodes consists of more than points, edges, and faces; data associated with these elements can also be carried through a node graph. This data is generally called an attribute. A named attribute is an attribute stored on geometry under a name. In this guide, you’ll learn about attributes, choosing a data type and domain, and storing and reading data. You’ll also see how to inspect the data and when the Named Attribute List add-on featured on the Blender Extensions page might be useful.

For architectural visualization, this approach provides a foundation for reusing values associated with different parts of a model in node groups and materials. For example, you can store color or density data associated with faces on the geometry and read it at a later stage. The goal here isn’t to build a ready-made façade system, but to understand where data is stored and which nodes read and write it.

Requirements

This guide is based on the Geometry Nodes and attribute documentation in the Blender 5.2 LTS manual. The manual lists the node names and their behavior under this version heading. The sources don’t specify a requirement for a Blender account or paid license, so no such requirement is assumed here.

The Named Attribute List add-on is optional. The Blender Extensions page says it can be used in Geometry Nodes and Shader Nodes, and is intended to list existing named attributes as well as vertex groups, UV maps, color attributes, and object attributes. The page lists 12 July 2026 for version 2.11.0. Since the source doesn’t explain which Blender versions the add-on is compatible with, check compatibility separately before installing it. You can also use Blender’s built-in nodes to work with named attributes without the add-on.

How to use named attributes step by step

1. First, decide what the data will represent. You can store a value, color, direction, UV coordinate, or label. For example, you might use Color for color data associated with faces, or Float for a single density value. The Blender manual lists types such as Float, Boolean, Integer, Vector, Color, and String. Choose a type based on the data you want to store. If a wide color range or linear color workflow matters, consider the difference between Color and Byte Color. According to the manual, Color stores 32-bit floating-point RGBA values in linear color space, while Byte Color stores 8-bit integers in sRGB space.

2. Decide which elements the attribute belongs to. This is called the domain. Point is associated with points, Edge with edges, Face with faces, Face Corner with face corners, Spline with curve control points, and Instance with instances of copied geometry. A UV map is one documented example of the Face Corner domain. For a façade model, decide upfront whether the value should be associated with faces or points. The domain affects how the data is interpreted by later nodes and how it is interpolated when transferred to different elements.

3. Store the data under a name in the geometry flow. Store Named Attribute is one of the nodes listed for writing named attributes in Geometry Nodes. Once you connect a value to the geometry and store it under a name, you can reuse it by that name later in the same geometry flow. In some cases, nodes may automatically handle data type and domain conversions; however, automatic conversion doesn’t make the initial choice unimportant. Carefully select the type of information you want to store and the elements it belongs to.

4. Read the same data by name when needed. The Named Attribute node is used to read named data from geometry. When entering a name or choosing from existing attributes, make sure you have the right one. The manual says that in the modifier panel, you can click the icon next to the value button to select a named attribute input. The search that opens shows the attribute’s domain, name, and data type. This is especially useful when working with data of different types that share the same name.

5. Use the result in other areas as well. Named attributes don’t have to stay within Geometry Nodes; the Blender manual explains that they can also be used in other areas, such as shaders, painting, and UV mapping. This lets you use data stored on geometry in later visual workflows. Don’t confuse an anonymous attribute carried through a node link with a named attribute: anonymous data has no name and can’t be directly connected to independently created geometry. To transfer data between separate geometries, you can use sampling nodes such as Sample Index or Sample Nearest Surface.

6. Inspect the domain and the result. The Spreadsheet Editor can be used to inspect attribute domains. If you can’t find the data you expect, first check the attribute’s name, type, and domain. For example, data stored on points instead of faces may produce different results in the nodes you use and subsequent transfer steps. Remember that as geometry changes, data may be automatically transferred to other domains; this transfer is usually based on averaging values. Boolean data, however, follows special rules when converted between domains.

Common mistakes

Using the same name for multiple data types: Special data such as vertex groups, UV maps, and color attributes can be accessed in Geometry Nodes by name. If names collide, only one of the attributes may be accessible. Use clear, distinct names throughout your file.

Treating color types as interchangeable: Color stores 32-bit floating-point RGBA in linear color space, while Byte Color uses 8-bit values in sRGB. Choose the one that suits your color workflow.

Trying to transfer anonymous data to separate geometry: Anonymous attributes can be carried through node links and are generally interpolated as geometry changes, but they can’t be transferred directly to independently created geometry from a different source. If you need to do this, consider the documented sampling nodes.

Assuming the add-on will always open: The Named Attribute List page notes that its context menu may sometimes not appear, which can be related to the active object selection. If the menu doesn’t open, check the active object selection and continue with Blender’s built-in nodes rather than making the core workflow depend on the add-on.

Next steps: adapting the workflow for architecture and visualization

Start by testing a single attribute type and domain on a small test geometry. Then read the same data with the Named Attribute node and inspect it in the Spreadsheet Editor. This helps you verify the relationship between name, type, and domain before moving on to a complex façade or interior scene. The workflow may be useful for architectural teams reusing surface or point data on a parametric model, as well as visualization artists who want to pass geometry data to the shader stage.

The sources don’t explain hardware requirements or whether the add-on is paid. So evaluate the workflow by validating it in a small scene, rather than relying on performance claims. Check that the add-on is compatible with your Blender version before using it; in production files, keep attribute names and data types consistent across your team. Once you’re comfortable with these fundamentals, you can expand the data flow by reviewing documentation for related nodes listed in the Blender manual, such as Capture Attribute, Transfer Attributes, and Sample Index.

Sources and license

The Attributes, Attribute Nodes, and Geometry Nodes documentation in the Blender 5.2 LTS Manual is licensed under CC BY-SA 4.0; the content has been adapted into Turkish. Information about the Named Attribute List add-on is summarized from its listing on Blender Extensions.