Blender Link, Append and Library Overrides: An Asset-Sharing Guide

Blender’s official user manual describes Link, Append, and Library Overrides as different ways to reuse assets from other blend files in projects. Link and Append are available in the File Browser, while Library Overrides are used with the properties of linked data. This guide is based on the current “latest” pages in Blender’s official manual; because the sources do not specify a particular Blender version number, none is listed here.

1. Link or Append?

The choice depends on whether you want the asset to stay connected to its source file. Link creates references to data blocks in an external file. Changes made to the source can be applied to linked data when the current file is reloaded. Linked items are marked with a chain icon in the Outliner; you can also inspect the source file path in the Outliner’s Blender File display mode.

Linked data blocks cannot be edited directly at first. Object location, rotation, and scale values also remain tied to those in the source file. However, a collection linked with Instance Collections enabled can be represented by a single object in the scene, and that object can be transformed. When Instance Collections is disabled, the collection’s contents appear directly in the Outliner. Instance Object Data creates an object for directly linked object data; when this option is disabled, the object data does not appear in the scene by itself. You can, for example, create an object by dragging it from the Outliner into the 3D Viewport.

Append copies the selected data blocks into the current blend file. You can work on this local copy, but later changes to the source file are not applied to it. Appending data that was previously linked does not always create an independent copy, either: Blender may leave those items linked and uneditable to preserve their relationships with other linked data.

2. Adding assets to a file and managing links

1. First, decide which data blocks you need and whether they should stay up to date with the source. To track source changes, use File › Link…; to work on an independent copy, use File › Append…. You can also start a Link or Append operation by dragging and dropping a blend file into the Blender window.

2. Find the source blend file in the File Browser and select the data blocks you want to use. Relative Path in the right-hand panel saves the source file path as a relative path rather than an absolute one. Select selects newly added objects.

3. When Active Collection is enabled, objects and collections are added to the active collection of the active view layer. When it is disabled, Blender creates a new collection called Linked Data for Link or Appended Data for Append.

4. If you want the collection to be represented by an object, consider enabling Instance Collections. When this option is disabled, the collection’s contents are visible directly in the Outliner; this setup can also be used to create Library Overrides. Appended collection instances can be duplicated with Add › Collection Instance; use Make Instances Real to unpack an instance’s contents into the scene.

5. When the linked file is updated, switch the Outliner to Blender File display mode. Right-click the library and choose Reload to load its contents again. If the file has moved or been renamed, use Relocate to point the link to the correct file.

If a file path changes, Blender may display temporary placeholder data for items in a library it cannot access. Rather than deleting the references at this stage, use Relocate in the Outliner to specify the source’s new location and make the linked data available again. There is also an ID Data › Relocate option for changing a single linked data block, but it is limited to items that are directly linked and are not dependencies of another linked data block.

3. Local editing with Library Overrides

Library Overrides are designed to let you change some properties of linked data in the local file without copying the data in its entirety. Properties that have not been changed locally can still update when the source changes. You can create multiple independent overrides of the same linked data, add new modifiers and constraints, and chain override hierarchies.

1. Select the linked item and use Object › Library Override › Make in the 3D Viewport. You can also start the operation from Library Override › Make in the Outliner’s context menu.

2. Blender may also create overrides for the data blocks needed to establish a valid hierarchy. The selected items are marked as editable. In the Outliner, Selected & Content makes both the selected items and their contents editable.

3. Edit the resulting override like a normal local data block. Changed properties may be marked with a turquoise-blue indicator in the interface. Use Add Override(s) to change every element of an array, or Add Single Override to change only the selected element.

4. If you need to revert changes to the source data, Reset restores the original values without deleting the override. Clear removes the override and returns to the source data where possible without breaking the hierarchy; if that is not possible, the override may remain but become uneditable.

5. Check the override hierarchy if the relationships in the source data change. Blender automatically resynchronizes when a file is opened if needed; if the issue persists, try manual resynchronization via Library Override › Troubleshoot › Resync in the Outliner.

Keep in mind that overrides do not support every type of editing: Edit Mode is not available for overrides. If animation is defined in the source, the ability to change existing keyframes is limited. When the source contains no animation data, new drivers can be added and edited. Assigning a local Action does not extend linked keyframe animation; it replaces it.

4. Considerations for architecture, interiors, and archviz workflows

Teams that use shared furniture, decor, or scene collections across multiple projects can consider Link when source updates need to carry through to those projects. Append is a better starting point when project-specific, independent editing is needed. Library Overrides are useful when an asset needs to remain linked to its source but only some of its properties need to change. Making this decision at the start of a project clarifies which file will be used to manage revisions.

For overrides to work smoothly, it is recommended that the collections an asset needs be organized under a root collection. If the source file is moved, you can update the links to its new location in the Outliner. The Blender manual also states that data cannot be linked or appended from blend files that are much newer.

Using a single item from a compressed blend file can require memory for the entire file during the initial load. As a result, loading a small item into the scene does not guarantee low memory use at startup. After loading, memory use reaches the same level, as the manual notes. Creating two-way dependencies between files also carries risks: reciprocal references can result in missing links. In addition, linking objects does not bring along scene-level settings such as Rigid Body World; the manual presents linking the entire scene as a background scene as an alternative in such cases.

Common mistakes

• Treating Link as an independent copy and Append as a live connection to the source.

• Assuming that you can directly edit the transforms of a linked object.

• Expecting Append to always break the link when the item was previously linked.

• Assuming that loading only a few items from a compressed file will use little memory during loading.

• Failing to organize the necessary collections under a root collection when setting up an override hierarchy.

• Creating blend files that reference each other, introducing the risk of circular dependencies.