Restrict Thumbnail Creation

Hi Amit,

We use those image sizes in the metadata. Google recommends having those exact image sizes in the metadata so it can use the best format for each situation (rich snippet, carousel, mobile).

So it’s good for SEO and we highly recommend keeping those thumbnail sizes. You could use a plugin like https://www.ads-software.com/plugins/fly-dynamic-image-resizer/ to not have WordPress generate those thumbnails for anything else but the recipe images.

Kind regards,
Brecht

Thanks for your reply Brecht.

I checked out Fly Dynamic Image Resizer. Unfortunately it providers no settings option. So i can’t choose/restrict which images to generate dynamically.

My issue right now is that because of WPRM my website is creating 3 additional images of EVERY image that I upload (and 95% of these are specific to the post and not particularly to WP Recipe Maker section). The additional 3 images generated by WPRM Metadata are unnecessary. Further, when I choose to turn on Retina, each of these 3 images will be duplicated (i.e. 6x) and when I generate WEBP then again all these additional files will be duplicated (i.e. 12x). This is a HUGE strain on my storage, CPU and image conversion for files that I am not using. (This is effectively creating more unused files for me than those in actual use).

I need to turn off WPRM custom images. Requesting you to suggest a solution not dependent on an additional plugin. I respect / understand the SEO implications you mentioned, but I will manage that.

Thanks in advance!

Regards,
Amit

I recommend against is, but you can add the following code to your theme’s functions.php file to not have it generate those thumbnails:

function wprm_remove_metadata_image_sizes() {
	remove_action( 'after_setup_theme', array( 'WPRM_Metadata', 'metadata_image_sizes' ) );
}
add_action( 'after_setup_theme', 'wprm_remove_metadata_image_sizes', 9 );

For anyone else reading this: these are 3 really small images so the impact on storage will not be an issue for most people and if it is the Fly plugin mentioned above will solve this for you. I highly recommend not using this code for SEO reasons.