How to find which Blender projects use an asset
A texture, model, or HDR can sit in a shared folder while the projects that reference it are scattered across shots. A filename search shows where the file is stored. It does not show which .blend files point at it.
Why this is hard to see inside Blender
Blender stores the path to an external file on the thing that uses it: an Image data-block on a texture node, a linked library, or another external reference. That path can be relative to the .blend file or absolute. There is no reverse index on disk that lists every project using wood_floor.png.
Opening each project and checking the Shader Editor, the Image Editor, or Outliner → Blender File works for one scene. It does not scale to a folder of client work, old shots, and backup copies.
What a folder search misses
Windows search, Everything, and similar tools find a file by name or path. They can also find the text of a path if it happens to be stored in a way the search index reads. They do not tell you the object, material, or node that uses the file, and they do not understand a packed image that no longer points at the loose file.
Blender’s File → External Data → Find Missing Files solves a different problem. It tries to repair paths inside the open project. It does not answer “which other projects use this texture?”
How to trace one file with LinkedFiles
- Install a LinkedFiles early access build on Windows 10 or 11 (64-bit).
- Select the texture, model, HDR, or other file you want to trace.
- Select the folder that contains your .blend projects. Nested folders are included.
- Run Find Usage. The first scan builds a local index. Later searches use that index until you refresh it.
- Read the results by project. Each hit can include the .blend file, object, material, and node path.
Blender does not need to be open. Save projects first. Unsaved changes are not in the file on disk, so they will not appear until you save and scan again. Details are in the documentation.
What the result is useful for
- Checking a shared texture before you replace or recolor it.
- Seeing which shots still point at an old model.
- Listing projects to update before you move a folder and break relative paths.
LinkedFiles does not rewrite those paths. It shows the projects that reference the file you selected. Path behavior is covered in how Blender asset dependencies work.
Limits
- One selected file per search. This is not a report of every asset in the library.
- Only saved .blend files in the folder you choose are scanned.
- A packed image may not match the loose file on disk.
- Broken paths can still show the asset name the project expects. A missing file and a used file are not the same result.
FAQ
- Does this work for textures and HDRIs?
- Yes, when the project references that file externally. LinkedFiles can trace common images, including PNG, JPG, EXR, HDR, TGA, and WEBP, plus other files linked from Blender.
- Will a packed image show up as the file on disk?
- Not necessarily. If the image data is packed inside the .blend file, the project may no longer point at the loose file you selected.
- Does LinkedFiles change the projects it scans?
- It reads saved .blend files and stores an index on your computer. The documentation does not describe editing those projects or rewriting their paths.