A command-line tool for analyzing and inspecting Unity build output—AssetBundles, Player builds, Addressables, and more.
| Command | Description |
|---|---|
analyze |
Extract data from Unity files into a SQLite database |
dump |
Convert SerializedFiles to human-readable text |
archive |
List or extract contents of Unity Archives |
find-refs |
Trace reference chains to objects (experimental) |
# Show all commands
UnityDataTool --help
# Analyze AssetBundles into SQLite database
UnityDataTool analyze /path/to/bundles -o database.db
# Dump a file to text format
UnityDataTool dump /path/to/file.bundle -o /output/path
# Extract archive contents
UnityDataTool archive extract file.bundle -o contents/
# Find reference chains to an object
UnityDataTool find-refs database.db -n "ObjectName" -t "Texture2D"Use --help with any command for details: UnityDataTool analyze --help
Use --version to print the tool version.
First, build the solution as described in the main README.
The executable will be at:
UnityDataTool/bin/Release/net9.0/UnityDataTool.exe
Tip: Add the directory containing
UnityDataTool.exeto yourPATHenvironment variable for easy access.
On Mac, publish the project to get an executable:
Intel Mac:
dotnet publish UnityDataTool -c Release -r osx-x64 -p:PublishSingleFile=true -p:UseAppHost=trueApple Silicon Mac:
dotnet publish UnityDataTool -c Release -r osx-arm64 -p:PublishSingleFile=true -p:UseAppHost=trueIf you see a warning about UnityFileSystemApi.dylib not being verified, go to System Preferences → Security & Privacy and allow the file.
