All items with pictures changed their status to "staged changes"

Hey guys,

I just recognized that the status of all published items (>2.000) that include pictures (also in different collections) changed their status to “staged changes”.

Any idea what happened? Is it “safe” to publish?


Hi @michael Thanks for posting this, this definitely sounds like odd behavior but is difficult to tell what you’re referring to without more information. Feel free to DM me if you prefer.

What sites are you seeing this issue occur in? When did it start occurring? Can you send me the site Read-Only links please?

Please send me screenshots of the behavior you’re describing.

Can you please try the following:
(1) Try to reproduce the error while being logged into Webflow using Incognito mode with browser extensions turned off: Browse in private - Computer - Google Chrome Help
(2) If the problem persists, please take a screenshot of your Console and send it to me: Chrome DevTools - Chrome Developers

Could you please let me know what browser version you’re using by sending me your information from this page?

There should be a small share link when you visit the page which you can send to me.

Thanks in advance!

Hi @michael, my apologies this isn’t a bug. :smiley:


Actually we pushed an update yesterday to re-measure responsive images to make that feature even stronger, so you’re fine to re-publish your site, it’s not a bug. :grimacing: It should in fact make your site load speeds a bit faster.

​Please let me know if this is helpful, or if you have any additional questions, I’m happy to help further. :smiley:

Same this happened to my client’s site at . Here is a screen capture showing > Monosnap

Ok cool …

Does that mean that all images in the CMS will be responsible automatically, so that we wont have to create thumbnails/preivews any more?

@pixelcactus @michael it was fixing this issue: Responsive variants of PNGs are much larger than originals

Yep, created new responsive image variants that are appropriately sized :bow:.

In detail, it’s making sure that we’re not pushing images that are larger than the original uploaded image. So if a responsive variant is bigger than the original image, we will use original image as a responsive variant and not use a larger variant.

Please let me know if you have any questions :smiley:

Just wanted to comment here that this also occurred for me. Generally speaking I love how agile and active you are in improving the product but I wanted to caution updates that affect republishing content…

for example, one of my clients has the rss feed linked into a mailchimp campaign, this update of content made every post look “new” to mailchimp… when he published his latest content update (along with the hundreds of updated content from the pictures) it ended up sending out a very confusing email to his list.

I was able to turn off other rss integrations and publish the updates then reactivate everything to keep things transparent for the rest of my clients, but had I known this would happen I could have ensured it didn’t affect any of my clients.

Again, kinda hard to stay ahead of these types of changes and get the word out in a reasonable timeperiod before pushing live, but if possible, having a little heads up on this type of update would be useful.


Who is affected by this? Every Webflow client using CMS? Only a handful edge-cases?

@Reed_Debaets, @Marci

Hi all. Sincere apologies for not communicating this change better. In all honesty we did not anticipate this being a visible change or having some of the side-effects you’re seeing with integrations. Bringing it to our attention is greatly appreciated.

This specific change involves responsive images (both assets in the asset manager and CMS).

The CMS item changes you’re seeing are happening because it populates CMS items that have images with more image data—so that we can better select image variants used on your site (the ones that end up in an <img>'s srcset attribute). It also makes sure variants are generated correctly in certain rare edge cases where they could be improved.

This optimization task runs when you open the Designer / Editor. So opening an old site a year from now or restoring an older site version of your site would cause it to run and make those changes.

In the short term: We’re working on a better way to communicate in-app whenever this happens to give better context about what the staged changes are.

In the long term: We’re working on ways to better manage future improvements to responsive CMS image variants that doesn’t integrate so tightly with CMS item updates.

1 Like

Thanks for the explanation :slight_smile:

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.