Blender Library Overrides: Link Once, Edit Locally

The problem: shared assets that need shot‑specific tweaks

In a production pipeline you often keep a master rig, prop, or environment in a single .blend file and link it into many shot files. The classic workflow (pre‑2.80) used proxies, which required a full copy of the armature and made it easy to accidentally diverge from the source. When the master rig gets a bug‑fix or a new control, every shot must be updated manually — a time‑sink that grows with the number of shots.

How Library Overrides solve it

Starting with Blender 2.80, Library Overrides let you link a collection or object from an external file and then create a lightweight local override data‑block that stores only the properties you change (transform, material slots, shader nodes, etc.). The link stays intact, so any update to the source — geometry, rig controls, shading networks — propagates automatically, while your shot‑specific edits remain untouched.

• Override data‑blocks live in the Outliner under the linked collection, marked with a small “override” icon.
• Only the overridden properties are duplicated; everything else continues to reference the original data‑block, keeping file size low.
• You can override multiple levels: object transform, pose bones, material slots, even individual shader node values.

Worked example: a character rig used in three shots

1. Create the master rig – In char_master.blend build a rigged character (armature + mesh). Save.
2. Link into a shot file – Open shot_01.blend. Choose File → Link, navigate to char_master.blend, enter the Collection folder, select the character collection, and click Link. The collection appears in the Outliner as a linked (grey) entry.
3. Create the override – In the Outliner, right‑click the linked collection → Override Library → Hierarchy. Blender creates a local override collection (white icon) that mirrors the hierarchy but is editable.
4. Edit shot‑specific pose – Select the override armature, go to Pose Mode, adjust a few bones for the shot’s acting. Because the armature is now an override, the pose keys are stored locally.
5. Update the master – Back in char_master.blend, add a new facial control bone and save. Return to shot_01.blend and choose File → Reload (or restart Blender). The new control appears in the override armature, while the pose you keyed in step 4 stays exactly as you left it.

Repeat steps 2‑4 for shot_02.blend and shot_03.blend. Each shot gets its own override collection, so each can have a unique pose while sharing the same master rig.

Trade‑offs and limitations

Aspect	Impact
Learning curve	Understanding which data‑blocks accept overrides (objects, collections, materials, node trees) takes practice; some types (e.g., simulation caches, certain constraint targets) still require proxies or manual workarounds.
Performance	Each override adds a local data‑block. In scenes with dozens of overridden collections the dependency graph can become heavier; profile with Window → Toggle System Console → Debug → Depsgraph if you notice slowdown.
Path stability	If the source .blend is renamed or moved, all overrides break and must be re‑linked. A disciplined folder structure (e.g., /assets/characters/char_master.blend) mitigates this.
Version requirement	Full support starts at Blender 2.80; older files opened in 2.79 will lose override information.

Quick verification you can run today

Open Blender 3.6 (or any 2.80+ build) and follow these steps to confirm the behavior on a minimal scene:

1. Create a new file A.blend. Add a cube (Shift+A → Mesh → Cube), set its location to (0,0,0), and save.
2. Create a second file B.blend. File → Link → select A.blend → Object → Cube. The cube appears linked (grey).
3. With the linked cube selected, choose Object → Make Override → Library Override. The Outliner now shows an override entry (white).
4. Move the overridden cube to (3,0,0). Save B.blend.
5. Return to A.blend, scale the original cube to (2,2,2), and save.
6. Reload B.blend (File → Reload). The overridden cube should now be at (3,0,0) and have the new scale (2,2,2), proving that local transform overrides persist while source geometry updates flow through.

If the location reverts to (0,0,0), the override was not created correctly — check the Outliner for the override icon.

Actionable next step

Pick one asset that currently lives in multiple shot files as a full copy or proxy. Convert it to a linked collection with a Library Override hierarchy, then make a single shot‑specific change (pose, material tint, light intensity). Verify that a later update to the master asset propagates without overwriting your change. Once comfortable, roll the workflow out to the rest of the pipeline and document the folder‑naming convention to keep paths stable.