- Split model by floors - Split model by function such as ( Curtain walls, steel, .. ) maybe in a separate model - Use native families not imported from 3ds max or SKP - split by HZ zones if applicable - keep heavy equipment in a separate files or in CLOSED worksets

1. Reduce polygon count or use Level of Detail (LOD) techniques to make models less storage-intensive. 2. Invest in high-capacity external SSDs or HDDs for storing large projects. 3. Utilize cloud platforms like Google Drive, Dropbox, or OneDrive for secure, scalable storage. 4. Compress model files using formats like .ZIP or .RAR to reduce storage size temporarily. 5. Use texture compression methods to minimize file sizes without quality loss. 6. For large projects, opt for services like AWS, Google Cloud, or Azure, offering specialized tools for 3D assets.

One strategy that always give me good results is apply the 5's concept around my workstation allowing me to have enough space to deal with the day by day workload. The few days when the workload is low is the moment when I put back on the server the source files such as .las files and Civil3d Models. Often I also divide to conquer, modulating the tasks into smaller pieces. Finally, I use file conversions (.dxf to dwg, .las to .laz) or compressing using 7z for the remaining files that are still relevant but not in the near future.

Managing large 3D models on limited storage involves external and optimization strategies. I use high-capacity external SSDs to offload files and cloud services like Google Drive for backup and access from anywhere. To optimize file sizes, I employ tools like Blender’s decimation modifier to reduce polygon counts while retaining quality and compress files using software like 7-Zip. A clean folder structure helps manage active projects efficiently, while archiving unused assets ensures my workstation stays responsive. Combining these methods balances performance, accessibility, and storage needs.

External. Absolutely invest in a great hard drive. I have found that compressing files doesn’t always let you recover them at the full resolution, and cloud storage is prone to other issues, like access and, again, storage space.

The balance between cloud storage and external drives depends on the project (the legalities around sensitive material both for what cloud storage solutions you can use, and if it's safe and appropriate to store files locally) but also the dev's physical situation. Cloud storage isn't great when you're working rural and have a horrible connection, but at the same time, external drives are prone to breaking and data loss. Not to mention being physically lost My rule of thumb is use both, and if I need to share files often with coworkers, I'll go cloud, and use external drives as cold storage. And the inverse for personal or small scale projects. Regardless, optimisation should always be your first call when running into storage issues.

I recently faced a similar storage issue and resolved it with these steps: Clean Up: Remove temp files, unused data, and unnecessary running apps. Compress Files: Use formats like .zip or .rar for temporary size reduction. Simplify Models: Keep only the elements visible in camera or render views. Optimize Textures: Compress and reduce texture resolutions where possible. External Storage: Use portable SSDs for fast and reliable access to large files. Version Control: Implement Git LFS or similar tools for efficient asset versioning. These strategies reduced the load on my workstation and allowed smoother rendering.

You can also compress the unused files on your system. It will definitely give you more space to storage. 1. Also you can try cleaning autosave data which you don’t need at that time. 2. If you are using zbrush try to make less layers in the sub-tool and before saving try deleting the morph target will also help.