Any benefits over srcset?

Hello, my friend,

Indeed what the plugin does is not very easy to explain in few words and I understand that the description can sometimes be confusing. Here we go:

– does this plugin provide any extra benefits over using images with srcset attribute?

If you implement the src attribute fully and correctly, ie you know all your breakpoints, you have all relevant sizes of your images per per breakpoint and you can actually set the src attribute of every image in your HTML, then the Adaptive Images plugin might not have much to offer!

However, these are exactly the same reasons why you would use the Adaptive Images plugin! Because you cannot handle all these parameters by hand and throughout the whole of your website easily. The goal of the Adaptive Images plugin is to provide a uniform way of simply not caring about these parameters.

– will it override image size provided by srcset attribute?

No it won’t. It will not touch your HtML at all, apart from a very particular case (CDN support, still an experimental mode) where it will add a url GET parameter on the src of an image. Other than that nothing else!

– also how it behaves when images are cropped for mobile? E.g. Revolution Slider.

Actually this is one of the cases where the Adaptive Images plugin really shines. Because it will filter and resize all your images, even the ones that have not been taken care of initially. It’s not that it detects anything magical. It just filters all image requests and, if an images is bigger than the device screen and according to the plugin’s settings, then it downsizes it.

Hope this helps!

Cheers,
Takis

Hello, no worries, here are my answers:

– do I understand correctly that after installing your plugin I can disable thumbnail creation on image upload and delete most of thumbnails already created. Anyway these images won’t be used most probably

If I understand this correctly, then I would generally advise that you let your theme and plugins choose the thumbnail sizes they need. You might need them in the future, if you ever choose to disable the Adaptive Images plugin and they even might use the thumbnail sizes in places that we cannot predict right now. So best is to let each tool do its job and hope that it does it transparently and independently. I can vouch that the Adaptive Images plugin will do that at least!

– if plugin can’t detect device viewport will it provide original image or those specified by srcset (of course if that size if thumbnail already exist)

In this case the Adaptive Images plugin will serve the original image requested. This could be the full image or any other thumbnail size depending on the case.

– I can’t get the idea of using breakpoints if plugin is supposed to deliver images of exact needed size. Breakpoints are used for delivering the closest image defined by srcset. But this solution still needs some css scaling. If I understand the idea of your plugin correctly it resizes images to the exact dimension of viewport, so I don’t understand why breakpoints needed

Actuall, no, the Adaptive Images plugin does not serve images exactly to the size of any device. It has a bunch of settings to actually help you set some breakpoints and then it will try to deliver images as close to these breakpoints. Otherwise it would be created tons of useless images.

– is there a way to disable plugin for bigger resolutions as I want to use image zoom functionality on desktop?

Actually you control this via the breakpoint settings of the Adaptive Images plugin that I mentioned above. For instance, if you have a maximum breakpoint of 1024px then all screens above that will ultimately be served with the original image requested at each time. So big devices will get bigger resolutions. This is something for you to decide upon and control. And it doesn’t have to be final. It is a setting and it can be changed at will!

Cheers,
Takis

Hello, my friend,

I found your plugin while searching for solution to WP media library mess caused by the way how it creates all the thumbnails on upload – completely unneeded waste of disk space. That’s why I want to disable creation of thumbnails and use your plugin instead. If one day I will have to switch back I will regenerate thumbnails easily, so there’s no need to keep them apart smallest thumbnail size which is used in media library on backend. Do I miss something?

To be honest I do not find the existence of many thumbnails too problematic. That is if they are not too many! If the theme treats the thumbnails respectfully and does not set more than 3-4 or of them, then I usually do not see any problems even in high-traffic content-intensive news websites.

Actually the size of the original images is usually so much bigger than the size of the thumbnails (thumbnails should be no more than a fraction of the total) that I tend to worry more about the original images. I have seen numerous websites using PNGs where they are not necessary or huge JPEGs where it is not needed.

Indeed someone might run into a problem in a hosting where many file reach the limits of the systems inodes, etc, but at this scale we are probably talking about a website with greater (than the usual) needs, so a dedicated hosting would be appropriate there.

By the way if I don’t set any breakpoints at all will the plugin serve images of exact needed size which do not need css scaling?

If you do not set any breakpoints (and in this case you do not need the plugin after all) the plugin will serve the image requested by the browser, whichever that may be depending on the src or srcset of the image element. CSS would only scale an image for the eyes of the user.

– if you choose to keep thumbnails created by WordPress and your theme you already have most probably more than half of images you will ever need. There are already standard WP medium-large (768px) and large (1024px) thumbnails which can be used for popular breakpoints. But your plugin has it’s own image storage, which will cause unneeded creation of images resulting in slow load when image is requested for the first time and extra usage of disk space. Maybe these images should be kept together? Or at least such an option should exist?

We have made a design decision here to keep things separated for reasons of transparency, separation of concerns and uniformity. We thought it would be best to not mix what the Adaptive Images plugin does with what the rest of the WordPress does. The theme might change, the plugins might change, we did not want to count on such things. There is a small redundancy here, I agree, but it is only a small fraction of the total in the end.

Also, the Adaptive Images plugin creates resized versions of images only when and if it is necessary, so it turns out that even less files are created!

As far as the load is concerned, there is absolutely no extra load on the website, other than the small overhead of creating the resized images the first time they are requested (and that is if and when they are requested at all). Practice has shown that this load is generally quite acceptable and even unnoticeable.

– also would be nice to have an option to disable the plugin for images which have srcset attribute

This is technically too complex and actually goes against the transparency and uniformity principle of the Adaptive Images plugin. We do not want to neither touch or be dependent on the website’s HTML. We just want to filter image requests.

– having webp support would be great

Indeed it would and it is in our roadmap already!

Cheers,
Takis

Hello, my friend,

I think I understand what you are saying, but the Adaptive Images plugin does not crop images. It only resizes them keeping their original aspect ratio. So I believe what you are describing is more a CSS and/or layout related issue.

Could you show me an example perhaps?

Cheers,
Takis