Why are synchronized local files different from the footprint shown in the cloud of the network disk?

There are five scenarios where the local sync folder storage space is not as large as the amount of space that is fast enough for cloud storage.

1. Selective synchronization is set up on the local computer, and some files in the Sync folder are not synchronized to the cloud. This can cause local occupancy to be larger than the cloud.

2. The files stored in the fast enough cloud settings are not synchronized, and these files will not be automatically synchronized to the computer's local hard drive. This can cause cloud space to occupy larger than the local.

3. Files are moved to the cloud Recycle Bin after they are deleted. When the Recycle Bin is not emptied, these files also occupy the storage space in the cloud. This can cause cloud space to occupy larger than the local.

4. There are other folders mapped to the Sync folder, because the mapping feature does not actually store the files in the Sync folder. So when you view the Sync folder size, the size of the mapped file is not counted. But the mapping file will take up the cloud's storage space after it has been synchronized to the cloud. This can cause cloud space to occupy larger than the local.

5. The user has a LAN shared folder where the files are stored only in the user's local space. This situation can cause local storage space to be larger than the cloud.