# \[Request\] Quixel megascans need an own Sub-Library

**URL:** <https://forums.unrealengine.com/t/request-quixel-megascans-need-an-own-sub-library/2087330>\
**Category:** Feedback & Requests\
**Tags:** library, Megascans, fab\
**Created:** [October 25, 2024, 11:26am UTC](https://forums.unrealengine.com/t/request-quixel-megascans-need-an-own-sub-library/2087330 "2024-10-25T11:26:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BDC\_Patrick](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/bdc_patrick/32/1104221_2.png) [@BDC\_Patrick](https://forums.unrealengine.com/u/BDC_Patrick)\
**Post date:** [October 25, 2024, 11:26am UTC](https://forums.unrealengine.com/t/request-quixel-megascans-need-an-own-sub-library/2087330/1 "2024-10-25T11:26:13Z")

</div>

If you Add Quixel Megascans stuff to your Fab library, you litter the whole thing.  
Actually, added over 1000 Assets… and i need to scroll down for 1000 Assets to find my first Code Plugins and stuff… it’s annoying and a mess.

Please give the Megascans their own library Category!
