#1
Zero Ownership
A Webflow build can easily run tens of thousands of dollars, and almost none of it produces something you can take with you. The design, layouts, components, and animations exist only inside Webflow. The code export is a static snapshot without your CMS content, and it can't be brought back in or run as a working site.
Your written content can be exported to a spreadsheet, but images and files come out as links back to Webflow's servers, which stop working if the project is deleted.
If you ever leave Webflow, you keep your words and lose everything you paid to have designed and built. Moving to another platform means paying for the site again from scratch. That switching cost is a large part of why both Webflow and the agencies building on it benefit from long-term client relationships.
#2
Stacking Subscriptions
Webflow bills separately for your team's workspace and for each published site, then adds paid tiers for features like file uploads, multilingual content, and AI usage.
Connecting Webflow to anything else usually means another subscription. Webflow's built-in integrations are limited, so most connections run through third-party apps, and nearly all of them charge their own monthly fee once you go past a basic free tier. Memberships, advanced forms, translation, data syncing, and automation services like Zapier or Make are common examples.
Each one adds its own bill, its own usage limits, and its own point of failure, for functionality a WordPress site often handles with a single plugin.
#3
No Plugins
WordPress has tens of thousands of plugins for things like memberships, events, booking, directories, and advanced forms. Webflow has a much smaller app marketplace, and its own membership and workflow features have been discontinued. Most of these needs end up as paid third-party tools bolted on from the outside.
#4
Content Limits
Every plan caps how much content you can store, how many content types you can create, and how many fields each can have. Pages can only display 100 items in a list without pagination, and showing related content (like posts by category inside a list of categories) is tightly restricted. Larger content libraries outgrow lower plans quickly.
#5
All-or-Nothing Publishing
Publishing pushes every change across the whole site at once. You can't publish one finished page while another is still in progress, and it's easy to accidentally push staging work live. The features that solve this are only available on Webflow's Team and Enterprise platform plans.
#6
No Real Change History
Webflow keeps backups you can restore, but you can't see what changed between versions or who changed it. Rolling back means restoring the whole site to an earlier point, losing everything done since.
#7
Form Restrictions
Every plan has a monthly cap on form submissions. Accepting file uploads, like resumes or documents, requires a higher-tier plan and is limited to 10MB per file. Many businesses end up paying for HubSpot, Tally, or a similar service to handle forms.
#8
Feature Conflicts
Some paid add-ons don't work together. Webflow's multilingual add-on isn't compatible with Webflow Ecommerce, so a store in multiple languages isn't possible natively.
#9
Limited Content Editing
The content editor is basic compared to the WordPress block editor. Teams used to building flexible page layouts, reusable sections, and rich articles without help will find it restrictive.
#10
Still Developer-Dependent
Webflow is marketed as freeing marketing teams from developers, and for simple page edits it does. But custom integrations, tracking, advanced functionality, and structural changes still require a specialist, and Webflow specialists typically charge more than WordPress developers.