Honestly, if it wasn’t for the fact I got my clients here, and moving them would be an option, I’d be gone for long time already. For now, however, I refuse to create new websites for any new client on Webflow; I’m slowly moving away to other platforms. Sorry not sorry, but when support can’t even reply in time which is the very foundation of good business, I’m out.
1 Like
I stayed up until 2am last night working on critical updates for the sites I created but selfishly thought oh I’m going to need some sleep. The site editor was blazing fast and stable that I’ve seen in awhile.
Woke up at 6:30am to get through the back log and schedule naps. Shame on me at this point for thinking todays the day. 
All of this. It’s been incredibly frustrating the last couple of months to work on Webflow. Either super slow, or just not working. Updating a class name? Lol, refresh your browser page because it just won’t.
I’m currently here because the lightbox can’t use the v- word link isn’t working, so now I’m trying to see if I’m the boob (it looks it’s not just me today.)
Webflow has become crazy expensive for people who sell the product too. Workspaces need constant upgrading when your team or portfolio grows (which generates more revenue for Webflow already).
Client projects need a new billing tier when they request admin access (which, should be a free seat, because let’s be honest, if I’m unable to help due to serious illness or injury, they don’t have admin access to share with someone else. Which should be a huge business contingency concern for everyone who freelances and gives a shirt about their clients.)
Dear Webflow - look at actual feature requests. Make your product stable, and stop being a money grabber for things that should consider the client first.
6 Likes
Well, after this outage, Webflow needs to offer like 2-3 free months for all freelancers & agencies. 3 days in a row is f’n crazy.
I understand that sometimes things can go wrong, 2-4h of downtime here and there, but 3 days. That’s totally unacceptable and someone needs to pay for this.
Let me guess, you replaced some engineers with AI Agents? 
15 Likes
What if this is all one giant A/B test and A works and we are all B? So they can continue to build their data and use cases for shoving Optimize down our throats constantly?
What if this is all a new Analyze uptime report launch? So they can continue to shove Analyze down our throats constantly?
3 Likes
Hey everyone! I’m a new member of the webflow community and wow these past few days have been eye-opening. It’s really crazy that in this day and age that such a widely used and expensive product could be unusable for basically everyone for TWO days. If Google can host a billion videos on youtube…I know it’s comparing apples to oranges but it’s kinda unacceptable in the 21th century to be cut off from the flow of information like this.
I’m new to this and wanted to see if people more experienced than me at web development have ideas on other products similar to webflow I could switch to.
3 Likes
Over the year, webflow has:
- Deleted features that people used (x2)
- Increased prices (while deleting features, charging more for less!)
- Made plans more complicated
- Decreased the number of editors making us pay more for our clients with more team’s sites
- Added features no one asked for to justify price hikes
- Has now been effectively down for 36 hours
I really really love the Designer, but that’s basically Webflow’s one redeeming quality at this point… I honestly don’t think sticking with Webflow is a good business decision at this point when so many alternative designers with effectively the same featureset have come out in the couple years. Their leadership has proven time and time again we can’t trust them to make the right decisions about our websites.
One of my client sites can’t receive form submissions right now and I cannot overstate the business impact for them. They’re pissed and I think they’re going to fire us or demand some money back and I don’t know what to do honestly…
I’m so frustrated I want to scream
5 Likes
Webflow was 100% vibe-coded
3 Likes
$4 billion company and they don’t understand their own backend infrastructure so they’re literally on a zoom call with AWS right now asking them desperately to fix this because they need to be ready to promote another Ai slop feature literally zero people asked for during the Webflow Conference in September so their shareholders can see another 1% increase in their ownership stake before they sell this off to Adobe in 3 years and it goes the way of Dreamweaver.
3 Likes
I think it needs to be noted that, not coincidentally, the new CEO was installed almost exactly a year ago. Her first action was to lay off a sizable chunk of their staff, and then… Everything you describe.
I’m heartbroken. I love this platform (when it works). And I’m panicked. Although I don’t have as much invested in Webflow as many of you, it’s still pretty central to my work.
They desperately need leadership back that actually understands their customer base and isn’t just trying to wring every penny from us while skimping on vital infrastructure.
5 Likes
I see the thread has been unlocked and I saw some folks saying elsewhere that it was locked as people were disrespectful etc. Which may be the case, I’ve also seen many posts on the forum, on Slack and Twitter asking for support for the devs, to understand that they’re having a difficult time, and to show support.
I have to respectfully disagree with the premise here. We’re not here to “support” Webflow and their dev team - it’s the other way around.
Here’s the thing: we pay Webflow for a service. They provide that service in exchange for our money. This creates a pretty straightforward contractual obligation that flows in ONE direction - they owe us service quality, not the other way around.
Why the “let’s support the team” framing is backwards:
Economic reality: Our subscription fees literally fund their salaries. We’re already supporting them financially every month.
Professional accountability: When you go to a restaurant and get bad food, you don’t say “let’s support the stressed chef in the kitchen.” You expect better food or you take your business elsewhere.
Power dynamics: Framing paying customers as needing to emotionally “support” the company flips the relationship on its head. It makes us responsible for the provider’s feelings instead of them being responsible for service quality.
Market mechanics: Companies improve through market pressure and honest feedback. When customers start cushioning every failure with unconditional support, there’s less incentive to fix the underlying problems.
Look, respectful communication? Absolutely. But there’s a big difference between being respectful and being asked to provide emotional labor for a company we’re paying.
When platforms have stability issues that directly impact our businesses and clients, we have every right to express that concern forcefully. The “be nice to the devs” response essentially asks us to subsidise their operational mistakes with our patience on top of our money.
The real solution isn’t customer sympathy - it’s Webflow investing in better infrastructure, communication, and accountability systems.
We’re not their therapists. We’re their customers and like I’ve said elsewhere; we’re not asking for miracles, just for open communication and a genuine effort to address the issues that are costing us time, credibility, clients.
27 Likes
Amen to that, brother.
2 Likes
This is crazy yo. I have nothing nice to say but that.
I think this situation perfectly illustrates how little companies actually care about their users. It’s all about growth and keeping shareholders happy. The cycle is always the same: attract users, make them dependent, then slowly degrade the product in pursuit of profit. Eventually, the platform dies.
I really hope we’re not at that point with Webflow yet. I switched over from Wix two years ago and invested serious time mastering this tool. I don’t want to go through another migration or add yet another platform to the 20+ tools I’ve already had to learn over the last decade.
The typical SaaS lifecycle:
- Early phase: Build a great product, focus on users.
- Growth phase: Attract creators, freelancers, agencies. Make it feel like a community.
- Investor phase: Monetize. Cut “non-scalable” features, push pricing up, remove flexibility.
- Decline phase: Loyal users get squeezed. Innovation slows. Power users jump ship or get locked in. Are we here now?
I won’t panic-migrate yet, but watch Webflow’s next 6–12 months and I hope the decision makers will enlighten.
12 Likes
And now I’ve been told I cancelled my plans at my end when I know for certain that I did not. They told me they can’t reinstate them at their end either. They said they’ll pass me to another team because my situation is apparently not simple to sort out. I paid 1 basic hosting (year) in February, a second basic hosting (year) only a few days ago and Core (Year) in end of March. Why on earth would I cancel them? This is proving to be a nightmare. It does not help that you can’t speak to a person and you have to wait hours for a response. The stress levels at the customers I’m losing is great. @Veronica-Webflow @lindatong I need to have someone reinstall those. I paid for them.
1 Like
I can help - there is much easier way out
This topic is temporarily closed for at least 24 hours due to a large number of community flags.