WebP Conversion Tool for CMS Assets

Easily compress and convert all your CMS assets into WebP files for improved site performance.

Building on previous WebP image support capabilities, we’re excited to announce that you can now convert your CMS images into WebP files across all Collections in your Webflow sites for improved performance.

Compress and convert all CMS assets across your Collections.

To learn more about the WebP conversion tool and how it works, visit Webflow University.


Hi, @matthewpmunger.

I can’t compress “all” assets in my CMS Collections. From what I saw, only images that are inserted into image fields are compressed. Images within Rich Text fields are not compressed/converted to WebP. Can you please confirm if this is true?


Any ideas on this, @matthewpmunger?

This is a great new feature! I notice that there are some stipulations:

You can convert as many assets as you want to WebP files. However, there is a request limitation of 100 assets per request, and 10 requests per minute.

I have a CMS collection with 1K+ entries that have multiple image fields. When I use this new feature, it quickly says that my conversion is complete and that I should publish. There is no indication as to HOW many of my files have been converted, how many files are left to convert, or how many requests I have made or have left.

Is there anything that can be done to track this or are we just supposed to keep track of how many times we click the “Compress Assets” button per 10 minutes and then at some point in the future maybe everything that can be converted will be?

I can’t compress “all” assets in my CMS Collections.only first few are being compressed,any update on this?


At this time, there is no progress indicator so it sounds like for your site it’ll be a good idea to roughly keep track of when the whole CMS has been parsed. I can definitely see how feedback on the process would be very valuable.

After the initial first pass, the action will only process new images that have been added whether that is to new CMS items or existing ones.

The action will only replace image assets if there are file size savings to be had with the compression, so you won’t always see a webp replacement.

The feature does work with images that are within Rich Text fields, but images will only be replaced if there are file savings to be had with compression. If the file size is not an improvement, the the original asset file will remain.

Hey @edrock the limitation that you have quoted is just for static asset compression from within the Assets panel. This limitation does not apply to the CMS conversion tool.

The CMS compression tool will do an initial pass on all CMS image assets. Once you see the success message then you know it has finished processing all of them.

Any subsequent runs of the CMS compression tool will only scan for new or replaced assets.

Hope that helps.

Cripes I thought it would do all assets within the rich-text fields. Will this be added soon or do I manually have to re-import approx 20,000 images across hundreds of rich text fields one by one? :) We are close to our bandwidth limit at times

Hey @blackrainbow it does work for CMS rich text.

Hey @matthewpmunger! Thank you for clarifying this. It was my understanding from reading a plethora of other posts that images inside Rich Text Fields are not converted and compress. I have ran the tool multiple times on my site, and have yet to see a single image from the body of the article (images inside a RTF) converted and compressed. Can you please clarify how to make it work? I’ve run the tool at least 60 times already.