# Unused Assets Finder

![](https://521907794-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MA3FzVzHVW8EDfWJmCT%2F-MIWI0t6LVwpZ6DjN-MU%2F-MIWITtRshRy3S7QKRX9%2FCoverImage_1950x1300.jpg?alt=media\&token=766b8a0a-7cb8-4c13-af7f-4843f85e6156)

Unused Assets Finder does what it says on the tin.

This fast, reliable and customizable plugin allows you to find, export and remove unused assets WITHOUT relying on a build to find what assets are not used.

[Website](https://www.unusedassetsfinder.com) | [Readme](https://www.unusedassetsfinder.com/documentation/readme) | [Changelog](https://www.unusedassetsfinder.com/documentation/changelog)

**Features**

* Create a Rule Set, which allows you to filter your search to only find unused assets that fit your criteria. For example, only finding .fbx files.
* Async code, so it's super fast
* Works on Unity versions 2017.1 and above

Once all unused assets are found, the results are displayed in a familiar way, mimicking the export package window, which has a search bar so you can search results for specific files.

The Unused Assets Finder will remove any empty folders while exporting your assets, keeping your project tidy and uncluttered.

**Compatible with**

* PlayMaker
* Dynamic Bone
* Easy Mobile Pro

**Report Issues / Suggesting Features**

[We're committed into fixing bugs and issues as soon as we can and also hearing what features you'd like to see! Feel free to tell us by submitting an issue and we'll get back to you as soon as we can](https://bitbucket.org/UnusedAssets/unusedassetsplugin/issues?status=new\&status=open)

**Notes**\
This requires the .Net 4.x Scripting Runtime to work


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.unusedassetsfinder.com/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.