Using Link and Append in Blender: A Guide to Shared Assets

Blender’s official manual explains how to reuse objects, materials, and other data blocks from another .blend file using Link and Append, as well as how to work with linked data using the Library Overrides system. In architectural visualization projects, these options determine how shared assets are distributed across files and edited when needed. The menu paths here are taken from the current Blender Manual pages; the sources do not specify a particular Blender version.

1. Decide first: Link or Append?

File › Link… creates a reference to data in another blend file. Changes made in the source file are reflected in the linked data when the current file is reloaded. This approach works well when a shared asset is maintained in a source file and multiple projects need to receive its updates.

Linked data blocks cannot be edited by default; this restriction also applies to the location, rotation, and scale of linked objects. Linked items are marked with a chain icon in the Outliner. To see the source file and its linked items, view the Outliner in Blender File display mode.

File › Append…, on the other hand, copies the selected data into the current blend file without retaining a reference to the source file. This makes it easier to work freely on a local copy, but later changes to the source file are not transferred to that copy. Appending data that was previously linked may add new items to the scene while preserving existing links, so Append does not always localize linked data.

2. Add files and work with collections

1. Open the source .blend file using File › Link… or File › Append…. In the File Browser, select the data blocks you want to reuse. According to the manual, you can also start a Link or Append operation by dragging and dropping files into the Blender window.

2. Consider the Relative Path option in the File Browser’s right-hand panel. This keeps the external file path relative rather than absolute. If project folders may be moved or opened on different computers, choose a path setting that fits the team’s file organization.

3. With Active Collection enabled, added objects and collections go into the active collection of the active view layer. When disabled, a new collection named Linked Data is created for Link, or Appended Data for Append. Choose the setting based on how you want to organize the scene hierarchy.

4. When Instance Collections is enabled, each collection is represented in the scene as a collection instance with a single object. These instances can be duplicated through Add › Collection Instance, and converted into the collection’s contents using Make Instances Real. When the option is disabled, the collection items appear in the Outliner with their contents.

Instance Object Data also affects how data is displayed and edited: when enabled, an object is created for the directly selected object data; when disabled, the data remains invisible until an object is created separately to make it visible in the scene. For Append, Fake User marks added data blocks to keep them. Localize All also copies indirectly linked data, localizing it instead of maintaining the links.

3. Editing linked assets: Library Overrides

If linked data needs to be edited while retaining its connection to the source, you can use Library Overrides. The system allows properties of linked data to be edited in the local file, while unchanged properties can still receive updates from the source library. After selecting an item, use 3D Viewport › Header › Object › Library Override › Make or the Outliner context menu path Library Override › Make. Blender also creates overrides for associated data blocks required to establish a valid hierarchy.

Override editability can depend on where the operation is started and what is selected. In the Outliner, choosing Selected & Content is one practical way to make newly created overrides editable by the user. If an override cannot be edited, use Make Editable first. Edited properties work like regular local data, but Edit Mode is not available for overrides.

To restore a value from the source data, use Library Override › Reset; this restores the original value without deleting the override. Clear removes the override, when possible, and returns to the linked reference data. To change the override status of a property, use its context menu to select Add Override(s), Add Single Override, Remove Override(s), or Remove Single Override. For array properties, the single-item options differ from those that apply to all items.

4. Updates, broken links, and common mistakes

To update linked data, switch the Outliner to Blender File display mode, right-click the linked blend file, and select Reload. If the source file has been moved or renamed, use Relocate in the same context menu to point to a different file. For missing libraries, Blender may create placeholder data blocks to prevent links from being lost; locating the correct library file again can restore the data.

Common mistakes include trying to edit a linked item as if it were a local copy, assuming Append always breaks existing links, and confusing a collection’s contents with a collection instance. For a more reliable override hierarchy, group the required collections under a clearly defined root collection. If relationships in the hierarchy change, the overrides may need to be resynchronized. Blender syncs them automatically when the file opens, and you can also use Library Override › Troubleshoot › Resync in the Outliner when needed.

In architecture, interior design, and archviz workflows, Link can suit teams that want shared scene assets to stay current from a source file, while Append is an option when an independently editable copy is needed. Referencing compressed blend files can result in high memory use because the entire file is loaded into memory even if only a small part is used. Circular dependencies—where the source also links back to the current file—can also result in broken links. For this reason, check file paths, library access, and the scene hierarchy before delivery.