Just a tick. I was working on other things unrelated to Webflow so I wasn’t plugged in and I see it’s still an issue. The frustration in these threads didn’t emerge from nowhere. It emerged from Webflow’s failure, to prevent the issue, to communicate transparently, and to provide any meaningful accountability or compensation for the damage done.
Telling paying customers to “be respectful” when they’re trying to surface a real platform failure is a deflection tactic. Respect is earned, especially in a crisis. They don’t get to publicly fumble their infrastructure and then demand politeness while ignoring direct questions and silencing the most active community threads.
And locking down the main thread? That wasn’t to protect the Webflow support team. That was to dilute visibility. The fact that it happened at least twice, in the middle of what could be catastrophic to several paying customers makes it hard to trust. It scatters legitimate criticism into a bunch of smaller, easier-to-ignore conversations. It’s insulting to pretend that’s community moderation. That’s corporate damage control 101. No thread I’ve seen have used slurs, only panicked and frustrated people trying to figure it out. Many have even resorted to running their replies through AI to make sure their replies are clear and stripped of the color.
People are not “acting like jerks.” They are acting like people whose work and clients were directly impacted. Some lost money. Others lost trust. We showed up in good faith. They locked the door and kept us out of our workspaces.
It looks like it’s getting stable again, but this was a stain on Webflow’s reputation.
I can’t WAIT for the conference in September!