Hekate and its different file sized backups

Backups could always be split or not regardless of the format. emuMMC however cannot be used as a single file on FAT32 so the universal solution is for it to be automatically split. I believe partition-based is still slightly faster than file-based on top of the fact that it is less prone to corruption. And exFAT is far from safe.

 

The file based emummc was created a lot more recently, after a lot of research and better understanding developed. 2 GB parts are safe. 4 GB parts are more efficient. Changing something about the past isn't really a priority when it there is no issue caused by how it already is.

Also, a full-sized backup on an exFAT isn't going to be as prone to corruption due to the lack of constant reads/writes. It's only meant to be read, after being written once. It's not made with the file-based emuMMC constant read and writes in mind.

 

File-based emuMMC is a rather new utility compared to making backups which the latter has been around since the scene's inception. For backing up the eMMC, CTCaer may have wanted to encourage people to use smaller SD cards to dump it just so that they have a dump available. As an example, Hekate lets you dump the eMMC as 1 GB parts but only if the space doesn't exceed 2 GB. As for file-based emuMMC, it won't be functional without an SD card that can support its entire size of around 30 GB but there is also less of a need to make shortcuts if the SD card is formatted as FAT32 so 4 GB parts is sufficient.