Asset Inspector ~~~~

May 7, 2026 · View on GitHub

Editor window for inspecting Unity asset references: it shows how each scanned asset hangs together in the project (serialized dependencies plus raw guid: usages), with optional Addressables / bundle context.

All logic ships in AssetInspector.cs so you can copy this file into /Editor/ folder.

How it works

Dependencies (tree)

For the asset you analyze, the tool walks direct links using Unity’s importer graph:

AssetDatabase.GetDependencies(assetPath, false)

Then it repeats per dependency (excluding the node itself), keeping an ancestor set so cycles do not recurse forever. Results are drawn as an indented tree so you can see which dependency pulled in another.

External GUID lines

Separately it scans lines of the serialized asset that contain guid: patterns, and lists each occurrence with ±2 lines of context.

Bundles / Addressables

Explicit Addressables groups are resolved via lightweight reflection against Addressables settings (when installed).
Optionally you can load an Addressables BuildLayout text export for extra bundle names on rows (see the window’s settings foldout).

Results View	Selecting Assets

Functionality	What you get	Purpose
Dependency tree	Nested list of everything the asset pulls in through `GetDependencies`	Refactor or delete an asset without surprises; see whether a texture is only used “under” a material, cross-bundle usage, etc.
External GUID rows	Lines in the file that reference other assets by GUID (with context)	Track down stringly references, odd scenes, or assets that do not show up as normal dependency edges.

Exclude .cs / filter fields narrow the visible dependency list (and exports); they do not change the underlying dependency graph Unity reports.