MobileRead Forums - View Single Post - Forma Can I safely delete the ".kobo-images" folder? It's taking 500MB of space.

davidfor · 10-13-2019, 08:36 AM

Most of this has been covered, but...

It is completely safe to delete the ".kobo-images" directory. It will be recreated when needed. The firmware will download covers for purchased books during the next sync and regenerated them for sideloaded books as needed.

As @NiLuJe, the KoboTouch driver can send cover images to the device when sending books. I'd completely forgotten that the plugin needed to be updated to use the new options. I have spend some time adding this today and have just released the updated firmware.

The driver and the utilities plugins options are separate, because the are separate things. And it is very likely, that you want to handle things differently when using them. For example, I usually have the cover sending options turned off in the KoboTouch driver, but have them turned on when using the KoboTouchExtended driver (because of how the covers are generated/extracted). These are set-and-forget. With the plugin, I can choose what I want to use at the time I am sending the covers to the device.

As has been mentioned, you can delete just some of the cover images. The device uses three. The smallest is used in the list and the middle sized one is used in the details page and on the home screen. The largest is used for the screensaver. You can remove any of these without affecting things to much. If you remove all of them, they will be regenerated the next time they are needed. This is done by regenerating the full size cover and then using that to generate the other images. But, if only the screensaver sized cover image is removed, it does not get regenerated. The next size down image is used instead. This will look terrible, but, it works and save space.

For this reason, I have also added an option to the remove covers function of the plugin to only remove the full sized cover. If you use this for all book you have read, or not planning to read soon, it will save space but not sacrifice the screensaver quality.

I do need to do some checking with this. I think if only the cover size used for the lists exists, that the others will be generated when needed. If that is correct, the others would save space as they would be generated when needed, but paging through the library would use the stored images.

I've considered for a while adding an option to the driver to send a smaller or lower quality image for the screensaver cover. I think I'd just use the 800x600 as that is the size used by the Touch. Or fiddle with the quality. This is set to 90, but could be reduced. I've no idea which would work better. I am not going to add more than one choice, just a "Save space by using smaller screensaver covers" option.

10-13-2019, 08:36 AM	#27
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Most of this has been covered, but... It is completely safe to delete the ".kobo-images" directory. It will be recreated when needed. The firmware will download covers for purchased books during the next sync and regenerated them for sideloaded books as needed. As @NiLuJe, the KoboTouch driver can send cover images to the device when sending books. I'd completely forgotten that the plugin needed to be updated to use the new options. I have spend some time adding this today and have just released the updated firmware. The driver and the utilities plugins options are separate, because the are separate things. And it is very likely, that you want to handle things differently when using them. For example, I usually have the cover sending options turned off in the KoboTouch driver, but have them turned on when using the KoboTouchExtended driver (because of how the covers are generated/extracted). These are set-and-forget. With the plugin, I can choose what I want to use at the time I am sending the covers to the device. As has been mentioned, you can delete just some of the cover images. The device uses three. The smallest is used in the list and the middle sized one is used in the details page and on the home screen. The largest is used for the screensaver. You can remove any of these without affecting things to much. If you remove all of them, they will be regenerated the next time they are needed. This is done by regenerating the full size cover and then using that to generate the other images. But, if only the screensaver sized cover image is removed, it does not get regenerated. The next size down image is used instead. This will look terrible, but, it works and save space. For this reason, I have also added an option to the remove covers function of the plugin to only remove the full sized cover. If you use this for all book you have read, or not planning to read soon, it will save space but not sacrifice the screensaver quality. I do need to do some checking with this. I think if only the cover size used for the lists exists, that the others will be generated when needed. If that is correct, the others would save space as they would be generated when needed, but paging through the library would use the stored images. I've considered for a while adding an option to the driver to send a smaller or lower quality image for the screensaver cover. I think I'd just use the 800x600 as that is the size used by the Touch. Or fiddle with the quality. This is set to 90, but could be reduced. I've no idea which would work better. I am not going to add more than one choice, just a "Save space by using smaller screensaver covers" option.