Hi @throughthelineltd
Could you check which generation method you have selected in the plugin settings (Find in post, Generate from title, Both, or Use default image)?
The “Image size” setting (your 405 x 405) only applies to images the plugin draws itself with the “Generate from title” method, where your post title is rendered on a background color. It does not resize images picked up by the “Find in post” method. With that method, the plugin downloads the first image found in your post content at whatever size the content uses.
So if you want the plugin to produce 405 x 405 files, switch the generation method to “Generate from title”. If you’d rather keep using the images from your post content, the plugin will save them at their embedded size, and you would control the display size through your theme or a registered image size instead.
About the filename: the random string at the end is intentional. It’s a short unique hash added so that two posts with the same title don’t overwrite each other’s image file, and so browsers and CDNs don’t keep serving an old cached image after you regenerate a thumbnail. It’s harmless and there’s currently no option to turn it off.
If you’re already on “Generate from title” and still getting 1024 px images, let us know your exact plugin version and we’ll dig deeper.
Hi,
Thank you.
We tried “Generate from title” and “Find in Post” are now trying “Find or use default image”.
Most of our posts have one image and we want that to display on the search results page as the thumbnail – hence the 400×400 sizing. We are not showing the “featured image” on the posts page itself as a banner etc , so we just need it at a small size.
Example…
Post title: “MEREM:1982.12 – title of main web site goes here”
…and the plugin is now creating these images;
MEREM1982.12_20322_faf2b.jpg – at original size 830×1024 – 252kb
MEREM1982.12_20322_faf2b_result.jpg – at 400×493 – 73kb
MEREM1982.12_20322_faf2b-324×400.jpg – at 324×400 – 36kb
MEREM1982.12_20322_faf2b-324x400_result.jpg – at 324×400 – 45kb
and the site is using MEREM1982.12_20322_faf2b.jpg as the featured image, being a duplicate of the one at the original size 🙁
So we’ve ended up with 406kb of additional images for this one post with no real gain, and we have 8000 posts to try and organise this for.
When we used “Find in Page” we ended up with a single image called (for example) – “MEREM1982.12_20322.jpg” – at full size, but at the moment I’m thinking we use the “Find in Post” method – download the images, resize them all to 400×400 and re-upload ? That would work for us – your plugin doing the hard work of populating the featured image field with the appropriate file name which is still a game changer in terms of managing this aspect of the site 🙂
Hi @throughthelineltd
Thanks for the update, glad the methods are clearer now.
Your plan will work, and one tip can make it even more efficient: if you insert the image into the post from the Media Library using the regular Image block, the plugin recognizes it and assigns the existing attachment as the featured image, without creating any new file. The extra “original” copy you noticed appears when the image tag in the content doesn’t carry the standard wp-image class. We’ve logged an improvement for that on our side.
About the 400×493 and 324×400 versions: those are not created by our plugin. They are extra image sizes registered by your theme or another plugin, and WordPress generates them for every image you upload, regardless of the featured image. The 0x0 trick in Settings > Media only disables the WordPress built-in sizes, not sizes registered by themes and plugins. If you want to stop those too, that would need a small code snippet or a plugin that can do that, but keep in mind your theme may rely on them for layout.
We’ve also logged your feedback about applying the configured dimensions to images taken from post content as a feature request. Thanks for flagging it!
