Oeh this improves my workflow !! no longer changing tabs to compression websites...

Amazing! The message was very clear and easy to understand!

Thank you, this saves a lot of time!!

Wow! Awesome thank you!

Very gggggod and interesting

Are there any plans for adding the AVIF support? I was quite disappointed when I discovered I couldn’t upload my AVIF image collection. There are several major websites on the web already using this format, Unsplash for example. It’s supported across all major browsers.

@Webflow

Ай бұрын

We'll let the team know, thank you for your feedback.

Technical question - is there an option to exclude a dedicated image field in a cms collection? We specifically upload jpg images into a field that is used to auto-populate email newsletter templates via RSS. At the moment, this does not work with webp.

@Webflow

Ай бұрын

Hey Fathom! That's not possible today unfortunately. Will share this note with the note as feedback. Thank you!

@fathom5209

Ай бұрын

@@Webflow Ok. Marketing hype aside, I do think it is important to communicate these sorts of points with your audience of users so they can make fully educated decisions. Few no-code users would be aware that webp is not supported by RSS - the primary mechanism for automated newsletters.

How to perform image sitemap?

Can’t we get one small but mighty update please :) a button in the Lottie asset window to clear all unused Lottie’s

It ruins the quality :) We need to have options to balance the quality and file size.

@musicalboy9122

Ай бұрын

it never ruins the quality

@ItsMeEd

Ай бұрын

​@@musicalboy9122 Oh yeah, it does. I have to use other WebP services to maintain somewhat good quality.

@petigubi

Ай бұрын

Agreed. I would never use it because images compressed by Webflow look unacceptable.

@Webflow

Ай бұрын

The optimization results can vary in quality depending on the source image. Since this feature applies to all CMS images with no ability to skip certain images or only process specific items/assets, it should be used strategically. As with static image compression, there are no controls over how the compression processes. Similar to video compression controls, to get the best results each asset should be optimized manually. The benefit of Webflow's asset compression is speed and ease use since it is built in. For granular control, we recommend optimizing assets prior to uploading to Webflow.

@ItsMeEd

Ай бұрын

If the feature is in Webflow, it means it has to be useful and is created to speed up the way Webflow developers work, right? I'm sharing my feedback with you so we can improve the product together because I love Webflow and my business is built around it. Most WebP converters do not decrease the quality as much as Webflow's native compressor does, and I use the same source file. I agree that it's super easy to use and it speeds up devs work, including mine. For example, in Photoshop, you get to choose if you want light compression or not, which means the same logic works in this case. My suggestion is to give us an option to choose whether we need light compression or hard compression.