How Blender asset dependencies work

External files

An Image Texture node, a world shader, and many other data-blocks can point at a file outside the project. Common image types include PNG, JPG, EXR, HDR, TGA, and WEBP. Models and other linked files work the same way when the project stores a path to them.

The path is either relative to the .blend file, which is the usual choice when you enable relative paths, or absolute, such as a full drive letter. Relative paths survive moving the whole project folder together with its textures. They break when you move only the textures, or only the .blend file.

Packed data

File → External Data → Pack Resources copies image data into the .blend file. The project can then open on another machine without the original folder. Unpack writes that data back out.

Packing changes the dependency. A search for the original file on disk can miss a project that only contains the packed copy. A project that is still linked externally can show a hit even when the file is currently missing from that path.

Missing textures

Blender shows a missing image as a pink or magenta material when the path does not resolve. In the open file, File → External Data → Find Missing Files lets you point Blender at a folder and retry those paths. Report Missing Files lists what the open project cannot find.

That repair is per open file. It does not search the rest of your library for every project that used the same texture. LinkedFiles reads saved projects in a folder you choose and can still list the asset name a project expects when the path is broken. It does not relink the file. Use Blender’s Find Missing Files on the projects you need to repair.

Linking and appending

File → Link creates a dependency on another .blend file. Collections, objects, and materials stay connected to that source, which is why a library .blend is dangerous to rename without checking who links it.

File → Append copies the data in. After a full append, that copied data does not keep following the source file. If you were trying to find projects that still update from a library, appended copies will not show up as a link to it.

What LinkedFiles reads

LinkedFiles scans .blend files in the folder you select, including subfolders, and looks for references to the one asset you picked. Results are grouped by project and can include the object, material, and node. The index is stored on your PC. Refresh it after projects change.

It does not draw a full dependency graph, edit .blend files, or pack and unpack images. For a single-file search, use find which projects use an asset. Before you delete something that returned no hits, read check a file before you delete it.

FAQ

Does LinkedFiles relink missing files?

No. It reports references it can read in saved .blend files. Blender’s Find Missing Files command, in the open project, is what retargets paths.

Are packed images the same as external files?

No. Packing copies image data into the .blend file. An external search for the original PNG or EXR can miss a project that only has the packed copy.

What is the difference between linking and appending?

Linking keeps a reference to the source .blend file, so later edits to that source can show up in the projects that link it. Appending copies the data into the destination file, which then no longer depends on the source for that data.