Largest size (pixels) poster pic used in emby...advice to bulk convert

[Ronstang 294]

Something tells me that we all have huge collections of media that many have very hi-res poster.jpg files that are wasting space in the database which then leads to slower load times.  Yes, I like my hi-res files also, especially when I have to edit them to repair damage as I like "as original" posters instead of sterile ones.  But...once the poster is as desired I don't see a reason to have a hi-res one as the poster file that wastes database space.  I currently resize all finished posters to 1000x1500 which cuts down on some of the wasted space but something tells me these are still too large and emby "resizes" them on the fly.  I'm not sure how they are stored in the database but any way it seems to me that any size poster file larger than emby needs is a waste of resources.

What is the largest size in pixels poster file emby needs?  I would like to resize all my poster files to this size to save on database space and load times.  Of course I would like to keep my hi-res ones also.  That being said is there any way to automate the conversion across an entire hard drive converting all "poster.jpg" files to the desired size and saving the hi-res one with an altered name for later use if need be?

[roaku 842]

The resized images Emby creates are stored in the cache folder, not a database.

The source images are also stored either in the metadata folder or with the media, depending on server configuration.

Using smaller source files will free up some hard drive space and slightly speed up the initial loading of an image to a given client when the cache images are generated for it, but I think that's it.

Especially since you want to keep the hi res versions, I don't think you need to change anything, as Emby is already designed to handle this for us.