kubiq

This plugin is ment mostly for developers. You need to use its functions in your theme or plugin to make it works.
This plugin offers functionality like face detection crop, focal point selector for every image, function to output responsive <picture> sizes and more.
<h3>Why to use this plugin?</h3>
WordPress will automatically create a lot of smaller images for every uploaded image. 
You mostly need just 1 or 2 of them, so this is a waste of your server space and resources. 
Also cropped images are generated from the center by default, which can be a problem many times.
This plugin allows you to:
<ul>
<li>disable autogenerated image sizes</li>
<li>dynamically generate only needed image sizes for only needed images</li>
<li>delete generated image sizes from this plugin individually or all together</li>
<li>specify different focal point that will be in the focus while creating cropped versions of the image</li>
<li>automatically detect focal point by face detection algorithm</li>
<li>disable big image size threshold, so image bigger than 2560x2560px will be NOT scaled down</li>
</ul>
<h3>How it works</h3>
<ol>
<li>if you disable existing autogenerated image sizes, then newly uploaded images will not create its sizes</li>
<li>you need to specify in your code what size is needed for the image</li>
<li>image is dynamically created on the first visit of the page and is stored in <code>uploads</code> folder</li>
<li>every next visit of that page will just load already generated image</li>
</ol>
<h3>Functions</h3>
bis_get_attachment_image_src( $attachment_id, $size, $crop )
Function inspired by default <code>wp_get_attachment_image_src</code>. 
If you used Fly Dynamic Image Resizer before, you don’t need to replace <code>fly_get_attachment_image_src</code> functions in your code – there is a fallback, so you can deactivate Fly Dynamic Image Resizer and it will still work.
Parameters:
<ul>
<li>
attachment_id (integer)(required) 
The ID of the image attachment 
Example: <code>123</code> or <code>get_post_thumbnail_id()</code> or <code>get_field('my_image')</code>
</li>
<li>
size (array)(required) 
An array with the width and height 
Example: <code>[ 1920, 1080 ]</code>
</li>
<li>
crop (boolean/integer/array/string)(optional) 
Skip this or pass <code>false</code> or <code>0</code> if you don’t want to crop, just rescale, 
otherwise pass <code>true</code> or <code>1</code> to use focal point crop that is selected in admin media (by default center), 
or pass array with string x-axis and y-axis parameters like <code>[ 'right', 'bottom' ]</code> 
or pass array with numeric x-axis and y-axis parameters like <code>[ 0.5, 0.8 ]</code> 
or pass string <code>'face'</code> to automatically detect face position (can be exhaustive on server resources)
</li>
</ul>
Returns:
<pre><code>array(
 'src' => (string) url of the image,
 'width' => (integer) width in pixels,
 'height' => (integer) height in pixels
)
</code></pre>
 
bis_get_attachment_image( $attachment_id, $size, $crop, $attr )
Function inspired by default <code>wp_get_attachment_image</code>. 
If you used Fly Dynamic Image Resizer before, you don’t need to replace <code>fly_get_attachment_image</code> functions in your code – there is a fallback, so you can deactivate Fly Dynamic Image Resizer and it will still work.
Parameters:
<ul>
<li>
attachment_id (integer)(required) 
The ID of the image attachment 
Example: <code>123</code> or <code>get_post_thumbnail_id()</code> or <code>get_field('my_image')</code>
</li>
<li>
size (array)(required) 
An array with the width and height 
Example: <code>[ 1920, 1080 ]</code>
</li>
<li>
crop (boolean/integer/array/string)(optional) 
Skip this or pass <code>false</code> or <code>0</code> if you don’t want to crop, just rescale, 
otherwise pass <code>true</code> or <code>1</code> to use focal point crop that is selected in admin media (by default center), 
or pass array with string x-axis and y-axis parameters like <code>[ 'right', 'bottom' ]</code> 
or pass array with numeric x-axis and y-axis parameters like <code>[ 0.5, 0.8 ]</code> 
or pass string <code>'face'</code> to automatically detect face position (can be exhaustive on server resources)
</li>
<li>
attr (array)(optional) 
An array of attributes 
Special attribute <code>retina</code> allows you to automatically generate srcset for <code>@2x</code> retina devices 
Example: <code>array( 'retina' => true, 'alt' => 'Custom alt text', 'class' => 'my-class', 'id' => 'my-id' )</code>
</li>
</ul>
Returns:
<pre><code><img src="https://web.com/wp-content/uploads/bis-images/1234/your-image-500x500-f50_50.jpg" width="500" height="500" alt="Alt text">
</code></pre>
 
bis_get_attachment_picture( $attachment_id, $sizes, $attr )
Parameters:
<ul>
<li>
attachment_id (integer)(required) 
The ID of the image attachment 
Example: <code>123</code> or <code>get_post_thumbnail_id()</code> or <code>get_field('my_image')</code>
</li>
<li>
sizes (array)(required) 
An array with the <code>key => value</code> pair 
where <code>key</code> means breakpoint 
and <code>value</code> is array of width, height, crop and alternative_attachment_id 
Example: <code>[ 767 => [ 767, 400, 1, 987 ], 9999 => [ 1200, 500, 1 ] ]</code> 
This will generate <code><source media="(max-width:767px)" srcset="image987_767x400.jpg"></code> 
and <code><source media="(max-width:9999px)" srcset="image_1200x500.jpg"></code> 
and <code><source media="(min-width:10000px)" srcset="image.jpg"></code> 
If you will provide also key <code>0</code> then it will replace <code><img></code>.
</li>
<li>
attr (array)(optional) 
An array of attributes 
Special attribute <code>retina</code> allows you to automatically generate srcset for <code>@2x</code> retina devices 
Example: <code>array( 'retina' => true, 'alt' => 'Custom alt text', 'class' => 'my-class', 'id' => 'my-id' )</code>
</li>
</ul>
Example: 
To generate perfect fullwidth hero image, that will looks great on 4K devices and also on small phones, but it will load only needed size, you can use:
<pre><code>echo bis_get_attachment_picture(
 get_post_thumbnail_id(),
 [
 375 => [ 375, 500, 1, 987 ],
 575 => [ 575, 500, 1, 987 ],
 767 => [ 767, 500, 1, 987 ],
 991 => [ 991, 500, 1 ],
 1199 => [ 1199, 500, 1 ],
 1399 => [ 1399, 500, 1 ],
 1600 => [ 1600, 500, 1 ],
 1920 => [ 1920, 500, 1 ],
 2560 => [ 2560, 500, 1 ],
 3440 => [ 3440, 500, 1 ],
 3840 => [ 3840, 500, 1 ],
 ]
);
</code></pre>
Returns:
<pre><code><picture>
 <source media="(max-width:375px)" srcset="https://web.com/wp-content/uploads/bis-images/987/your-image-375x500-f50_50.jpg">
 <source media="(max-width:575px)" srcset="https://web.com/wp-content/uploads/bis-images/987/your-image-575x500-f50_50.jpg">
 <source media="(max-width:767px)" srcset="https://web.com/wp-content/uploads/bis-images/987/your-image-767x500-f50_50.jpg">
 <source media="(max-width:991px)" srcset="https://web.com/wp-content/uploads/bis-images/123/your-image-991x500-f50_50.jpg">
 <source media="(max-width:1199px)" srcset="https://web.com/wp-content/uploads/bis-images/123/your-image-1199x500-f50_50.jpg">
 <source media="(max-width:1399px)" srcset="https://web.com/wp-content/uploads/bis-images/123/your-image-1399x500-f50_50.jpg">
 <source media="(max-width:1600px)" srcset="https://web.com/wp-content/uploads/bis-images/123/your-image-1600x500-f50_50.jpg">
 <source media="(max-width:1920px)" srcset="https://web.com/wp-content/uploads/bis-images/123/your-image-1920x500-f50_50.jpg">
 <source media="(max-width:2560px)" srcset="https://web.com/wp-content/uploads/bis-images/123/your-image-2560x500-f50_50.jpg">
 <source media="(max-width:3440px)" srcset="https://web.com/wp-content/uploads/bis-images/123/your-image-3440x500-f50_50.jpg">
 <source media="(max-width:3840px)" srcset="https://web.com/wp-content/uploads/bis-images/123/your-image-3840x500-f50_50.jpg">
 <source media="(min-width:3841px)" srcset="https://web.com/wp-content/uploads/2022/11/your-image.jpg">
 <img width="4000" height="2000" src="https://web.com/wp-content/uploads/2022/11/your-image.jpg" alt="Some alt" loading="lazy">
</picture>
</code></pre>
 
<h3>There is no fallback for <code>fly_add_image_size</code> function</h3>
If you used Fly Dynamic Image Resizer before, you need to remove <code>fly_add_image_size</code> functions from your code. 
You can create your own variables for sizes if you need it, like
<pre><code>define( 'MY_CUSTOM_SIZE', [ 1000, 200 ] );
</code></pre>
and then just us it inside functions, like:
<pre><code>echo bis_get_attachment_image( get_post_thumbnail_id(), MY_CUSTOM_SIZE );
</code></pre>
 
<h3>Support other extensions than JPG, PNG and WEBP</h3>
This plugin works by default only with JPG, PNG and WEBP files, 
but you can easily allow any other mime types, 
just use this code eg. in <code>wp-config.php</code> or in your <code>functions.php</code>
<pre><code>define( 'BIS_ALLOWED_MIME_TYPES', array( 'image/jpeg', 'image/png', 'any_other/mime_type' ) );
</code></pre>
 
<h3>Get selected image focal point</h3>
Focal point data are stored in the attachement post metas. 
There is also custom sanitize function, that you can use.
<pre><code>$focal_point = sanitize_focal_point( get_post_meta( get_post_thumbnail_id(), 'focal_point', true ) );
</code></pre>
Returns:
<pre><code>array( 0.5, 0.8 )
</code></pre>
which means that focal point is 50% from left and 80% from top

Better image sizes

Dynamically generate only needed image sizes for only needed images, with manually selected focal point for crops

aiwatech

In modern web designs, designers create different sizes of images on the web pages for attractive layout. If a web page is built using wordpress, a developer has to register every image size in theme to make sure, if client uploads an image of different size, it does not break the layout.
With a new WordPress installation, by default it creates three sizes e.g. thumbnail (150 x 150), medium (300×300), large (1024×1024) which means whenever a new image will be uploaded, WordPress will keep at least four copies of images on the server, one original image and 3 cropped image copies based on image sizes.
When developer/designer needs different size of image, they will register more image sizes e.g. hero, product thumbnail, product large image, team member image etc depending on design of the page.
Now lets say we have 3 default and 3 custom image sizes defined in theme, and now whenever a new image will be uploaded, WordPress will create 6 image copies and 1 original image even we need to use only 1 for a specific area on the website, remaining copies will remain on the server and will occupy space. Imagine when we have lots of posts, pages having different images, how many unnecessary images WordPress creates on the server which are useless and just eat server space. In case of Woo-Commerce website if you need to upload a new slider image for home page or a hero image for about page, it will create a lots of copies including different sizes of products image sizes which woo-commerce registers itself.
Ultimately website speed gets effected and server space as well.
To solve this issue, we built a plugin WP Image Sizes this plugin allows user to decide which image sizes should be created for every image being uploaded through WordPress.
After installing WP Image Sizes, it will create a setting page from where user can assign image sizes to each CPT. e.g. user can assign one size for hero/slider CPT, one size for team member, testimonials. After assigning image sizes to each CPT when user will upload a new image, WP Image Sizes will only allow WordPress to create copies of image sizes which were assigned to the CPT.
In case user tries to upload an image from a Media, it will show options in media uploader to select which image size user wants and WP Image Sizes will only create that image size.
WP Image Sizes plugin saves a lot of space on the server and plays a role to make WordPress website a bit fast.
<h3>PRO</h3>
WP Image Sizes plugin is also available in a professional version which includes more features <a href="https://aiwatech.com/product/wp-image-sizes-pro/" rel="nofollow ugc">See here</a>

WP Image Sizes

Select the only image sizes for post types you want to be generated. Eliminate unnecessary image sizes.

Better image sizes vs WP Image Sizes