You know the loop. You remember a material you made months ago, and to use it again you have to dig up the old project, open it, find the asset, and Migrate it over. Five minutes, every time.
Asset Library is an editor panel that ends that. You drag an asset from the Content Browser into it and it gets saved to a shared folder on your machine, with its dependencies, independent of any project. From any other project you open the panel, pick the asset, and import it.
Migrate already copies dependencies, so that part isn’t new. The useful bit is that the asset now lives somewhere you can reach from any project instead of being stuck inside the one that made it.
It also does folders, search by name, filtering by type, a dependency picker, real thumbnails, and a badge on each asset showing which engine version saved it so you don’t pull something incompatible into an older project. It’s editor only, has no runtime cost, and compiles on 5.1 to 5.7.
It’s on Fab as a paid plugin, link here https://www.fab.com/listings/b92051c9-c625-40e8-84ad-8d19f7e9f8eb. Saying that plainly instead of burying it.
I’m mostly curious how other people deal with this. Do you keep a library project, a synced folder, something else? Interested to hear what this approach might be missing