Augusto D'Amario Ok very nice! Do you do this on the fly and if so, does original image size being large affect the loading time anyhow?
tim: Right after the image is loaded, an optimized WEBP version is created, which is then used for the preview on the storefront.
Augusto D'Amario That is very good news, thanks. Gave my coworkers hard time for nothing :)
Hi tim! Swatches are created as WEBP images to optimize performance on the storefront, especially for mobile devices. Please let me know if you encounter any scenarios where swatches are generated in a different format.
Augusto D'Amario My bad, I did not express clear enough. Lets imagine a product that is in real life 2meters * 2meters, printed at 300dpi. The production files for the product are large in size. In step1 of template creation I upload a 1gb dynamic image. This image then needs to load every time customers wants to see a preview. Am I right? To mitigate this big file, we upload a new one, in web optimised quality, in step2. Internally we call it a thumbnail :) Are we doing as intended? So the feature is for customily to generate this web quality previews of dynamic images/libraries without a manual intervention
Hello Tim! I understand your point. For previews, WEBP versions of the images are created automatically. If you inspect your browser on the storefront, you should see that the loaded images are optimized as WEBP. (see bellow screenshot) Note: The only exception is for vectors, where it’s possible to replace the vector with an image for preview purposes.