unity-cleaner

To find unused Unity assets, you can run an audit that traces dependency trees across scenes, prefabs, and scripts to locate orphaned materials or textures. It safely flags unreferenced files for preview-confirmed deletion.

Reducing Unity bloat involves detecting duplicate files using content-hash analysis to identify identical assets. It also surfaces large files contributing heavily to project size, allowing you to safely remove redundant data before release.

Locating missing script references in Unity requires a reference health check that scans prefabs and scenes for broken dependency chains. It identifies the missing components so you can repair or safely remove them before preparing a release.

Yes, safe cleanup workflows allow you to preview deletions and confirm removals before modifying a Unity project. This ensures that only verified unused assets, empty folders, and missing script components are deleted during the audit.

Finding empty Unity folders is handled through an empty-folder discovery scan during a project audit. It identifies these directories and applies safe preview-confirmed deletion workflows to remove them without breaking valid asset paths.

Yes, Unity project cleanup includes dependency tree inspection that traces usage across assets, prefabs, scenes, and scripts. This dependency tracing ensures you can accurately identify what is truly unused before applying any deletions.