When you encounter issues trying to import material packages (.eaglepack files) into Eagle, the following content will help you understand possible causes and provide solutions.

Common Causes

Insufficient storage space: Ensure your device has enough available storage space to accommodate the material package to be imported
Corrupted material package file: The material package may have become corrupted during transfer or download

Solutions

Check storage space
- Confirm that the device storing the library has sufficient available space
- If space is insufficient, please clean up some unnecessary files to free up space
Verify material package integrity
- If the material package was copied from another device or downloaded via network, it's recommended to re-copy or re-download
- Ensure network connection is stable during download to avoid file corruption
Attempt to repair corrupted material package
- Change the material package file extension from .eaglepack to .zip
- Extract the file
- Check if the extracted content includes the pack.json file and corresponding info folder
- Verify that files within the info folder (original files, thumbnails, and metadata.json) are complete and can be opened normally
Manually import available files
- If only some files can be extracted, you can manually import these files into Eagle
- Please note: Files imported this way will lose their original folder structure, tags, and other operation records within Eagle, requiring manual re-addition

Important Notes

If the pack.json file or info folder in the material package is missing or has abnormal size (such as 0 KB), Eagle will be unable to read and load properly
Files imported after manual repair need to be reorganized, categorized, and tagged again

How to fix damaged or unimportable asset packages?