Build Report Tool

What shows up when the build is inspected

Build Report Tool puts Unity’s build information into a front-end that is easier to read than the default build output. Once a project is built, it shows the assets that were included and how much storage space each one takes. That makes it useful when a project needs close attention on build size, especially if the goal is to keep a build small or identify which files are taking up the most room.

The tool is focused on the contents of the build itself. Instead of presenting build data as something hidden inside Unity’s internal reporting, it surfaces the included assets in a way that can be checked directly. That makes the report more practical when the main question is not just whether the build succeeded, but what actually went into it.

There is also a clear limitation worth keeping in mind: the plugin does not detect the building of Asset Bundles or Addressables. That includes usage of plugins like VRWorld Toolkit. For projects that rely on those systems, the report will not cover that part of the pipeline, so the tool is strongest when the build content is coming through Unity’s regular build process.

Asset usage, dependencies, and unused files

One of the most concrete parts of the tool is the Asset Usage/Dependencies view. It shows which asset is using which, so it becomes easier to understand why something is being included in the build. That matters when an asset appears in the output unexpectedly, because the dependency chain gives a direct way to trace the inclusion back to its related files.

The Unused Assets List serves the opposite purpose. It highlights files that are not included in the build, which helps when a project has material that is no longer being used. That can be especially helpful in larger projects where old assets may remain in the folder structure long after they stop being part of the active build.

These two views work as a pair. The dependency side answers why something is present, while the unused list points to what is not making it into the build at all. Together they give a clearer picture of the project’s asset footprint without needing to guess where the extra content is coming from.

• Asset Usage/Dependencies: Shows which asset depends on which other asset and why it ends up in the build.
• Unused Assets List: Identifies files that are not included in the build.

Reports you can save and settings you can review

The Save to XML option lets build reports be stored as XML files. That makes it possible to keep multiple reports for reference instead of relying on a single snapshot. It also gives teams a way to pass the data along to teammates without needing to re-run the same build report each time.

Project Settings are another part of the report. The tool shows which build settings were used on the project at the time of building. That is especially relevant for Continuous Integration systems, where automated builds may need to be checked after the fact and compared against the settings that produced them.

The DLL List adds another layer of visibility by showing exactly which managed DLLs are being included in the build and how much space they take. That is useful when a project depends on managed code and the build needs to be checked for what is actually being packaged. The DLL List also works on Personal Edition and mobile, which broadens the range of project setups where it can be used.

Version history and compatibility notes

The package is listed as a unitypackage and is compact in size at 567.3 KB, with an asset count of 238. The latest version is 3.13.5, and the first publication dates back to Apr 17, 2013. The latest release date shown is Feb 11, 2026.

Compatibility is tied to Unity versions as well. The original Unity version is 4.6.5, and the supported versions list includes 4.6.5, 5.0.4, 2017.4.40, 2018.4.36, and 2019.4.41. A note attached to the current release says that all new versions require at least Unity 2019.4. If an older Unity version is needed, the note says a special package can be created.

The release notes for version 3.13.5 mention a fix for upcoming breaking changes in Unity 6.5 involving Application.consoleLogPath, along with a fix for Reveal in File Browser on Linux. They also note that the plugin has no MonoBehaviour or ScriptableObject classes, so it is safe to delete when it is being replaced.

For teams that need a direct audit of what enters a Unity build, this tool gives a readable report on included assets, dependencies, unused files, build settings, and managed DLLs in one place.