Blender linked libraries: link, append and overrides

You recolor the chair in the library file, open your scene, and the chair is still grey. Or you move the folder up one level and the project opens without textures. Blender linked libraries fail this way when you mix up three verbs: link, append and override.

What Blender Actually Does When You Link a File

Linking copies nothing: it creates a reference to data in the source file. If that data changes over there, your file picks it up the next time you reload the library. In the Outliner those blocks carry a chain icon, and the Blender File view shows which .blend each item comes from: the real map of the project once you work with collections and the Outliner.

What surprises people the first time: linked data is not editable, and that includes location, rotation and scale. If you try to move the object and it will not budge, that is not a bug, it is the contract. To get around it, link with Instance Collections, which creates an object of your own at the 3D cursor, or move into Library Overrides.

The Four Checkboxes in the Sidebar

The sidebar of File - Link or File - Append decides whether the project survives:

• Relative Path: stores the reference relative to the current .blend instead of absolute. It defines whether the project survives being moved.
• Select: keeps the newly added objects selected.
• Active Collection: when disabled, Blender creates a new collection, Linked Data or Appended Data.
• Instance Collections / Object Data: with instancing off, the collection comes in as-is and you see its contents in the Outliner, which is what you need to create overrides later.

A limit nobody mentions: you cannot link or append from .blend files much newer than your Blender version.

Link or Append: Deciding in Thirty Seconds

Appending is the opposite: it copies the data into your file with no reference to the original. You edit your copy freely, but improvements in the source never reach you. The confusion comes from both living in the same menu and looking identical in the file browser.

• The asset will change and I want the improvements: link plus override.
• The asset is finished and I want to touch it without depending on anyone: append.
• I need it forty times in the scene and I need to move it: instance the collection.
• I am delivering the project: append or pack resources.

Append has two checkboxes of its own that matter: Fake User, which protects appended data from being purged for lack of use, and Localize All, which also copies data linked indirectly. That second one is the difference between getting the whole character and half a character. And the manual's trap: if you append data you already have linked, Blender adds the objects but keeps them linked and uneditable.

Building an Asset Folder That Does Not Break

This is the part with real value and it is not in the manual: a project with shared assets breaks because of folder structure, not Blender. What works for me is one .blend per asset or family, with a root collection grouping objects, data, materials, textures and rig; stable names, with the root collection named after the file; and versioning by folder (assets_v01, assets_v02) instead of overwriting the library the scene already uses. Heavy files, textures, EXRs and HDRIs, live in a sibling folder with relative paths.

If you are building a modular set, this pairs well with modular assets and trim sheets, with the polygon budget and with keeping the library tidy in the Asset Browser.

Relative Paths: The Double Slash Rule

When you pick an external file, relative is the default: the path is evaluated against the folder of the .blend referencing it and, typed by hand, starts with a double slash (//). You can change it in Preferences - File Paths, but I would not. Two details: there are no relative paths in a file that has never been saved, so save before you link; and to move the .blend, use Save As with Remap Relative.

To Pack or Not to Pack

Pack Resources puts external files inside the .blend: a single file to hand over instead of a ZIP with dependencies. It is recognisable by the gift box icon next to the path. Mind this: the option only marks the files, the actual packing happens on save. And heavy external files cannot be packed, such as Sequencer videos: the classic mistake when delivering a project that uses the VSE. My rule: pack to deliver, never pack a shared library, because it duplicates textures in every scene.

Library Overrides: Editing What Is Linked

A Library Override lets you edit linked data without losing sync: what you do not touch keeps updating when the source changes. It replaced the old proxies, deprecated in Blender 3.0 and removed in 3.2. It supports several independent overrides of the same data, adding modifiers and constraints anywhere in the stack, and chaining overrides from other libraries.

Hierarchy Comes First

A real asset is not a data-block, it is a tree: armature, geometry, rig controllers, materials and textures. You link the root of that tree, almost always a collection. Hence the manual's insistence that the collections the asset needs hang from that root: if they sit loose or nest oddly, part of the data is not overridden.

Create, Edit, Reset and Clear an Override

Create one with Object - Library Override - Make, by right-clicking in the Outliner or with Shift+click on the ID widget link button. From the Outliner, pick Selected and Content so everything new is editable. An overridden property shows a teal border. Reset returns to the source values and stays editable; Clear resets and removes the override if it can, otherwise leaves it non-editable; Troubleshoot - Delete reverts the whole Make. Two limits: you cannot enter Edit Mode on an override, and if the data already has animation you can at most mute a curve, not edit keys or add curves. The NLA editor does let you move strips and add local ones.

When the Library Changes: Resyncing

If the relationships between data-blocks change in the source, overrides fall out of date and Blender resyncs when opening the file. But Resync can delete edited overrides: the manual warns how many it removed and lets you undo before saving, so read that warning. Resync Enforce rebuilds from the reference and forces the hierarchy to match; it is meant for old files with broken overrides.

When the File Breaks: Relocate, Reload, Make Local

If Blender cannot find a library on load, it creates placeholder data-blocks: relocate the library and the content comes back on its own. That is the difference between "the work is gone" and "one click fixes it".

• Relocate Library: right-click in Blender File mode. Fixes a broken link and also switches to a variation of the same content.
• Relocate linked data: only for directly linked blocks that are not a dependency of another.
• Reload Library: refreshes without closing the file.
• Make Local: cuts the link and leaves everything editable. From the viewport, Type localises data and materials too, the checkbox that keeps the asset textured.

Three limits: circular dependencies produce missing links; scene-level settings such as the Rigid Body World are not copied when you link objects; and compressed .blend files demand a lot of memory. Once the asset leaves Blender, the problem reappears in USD and glTF.

Five Failures I See in Class (and How to Fix Them)

• "I move the linked object and it will not move": instance the collection or create an override.
• "It will not let me edit the mesh": an override does not allow Edit Mode; edit in the library or Make Local.
• "I moved the folder and it opened without textures": absolute paths. Relocate and redo the relative ones.
• "I deleted the override by accident": resync; the warning offers undo before saving.
• "A linked block disappeared": linked data cannot take a Fake User; use a custom property.

With rigged characters the same problem shows up in rigging in Blender and in Maya, and it bites harder once mocap enters the pipeline.

Conclusion

Linking is a relationship, not a copy. The criterion in three lines: shared library, link with an override; delivery, append or pack; an asset that never changes again, append.

On the platform you have the anchor video for this topic, Everything you need to know about linking and library overrides in Blender, by Pierrick Picaut, and his curated channel with twenty-four videos. The open movie assets are a good test bench, and if you come from Maya, the logic of collections and instances will feel familiar; linking between files will not.