I've built dozens of sites in Webflow. I genuinely like it. The visual builder is excellent for marketing sites, landing pages, and portfolios. But after three years of pushing it on client projects, I've developed a very clear picture of where Webflow breaks down -- and it breaks down hard when you try to scale.

This isn't a hit piece. It's a field guide. If you're evaluating Webflow for a project that goes beyond a brochure site, you need to know these limitations before you're six months in and stuck. I'll walk through each limitation with real numbers, explain why it matters, and tell you what we actually use instead on production projects.

Table of Contents

1. The 10,000 CMS Item Ceiling

This is the big one. The limitation that's bitten more of our clients than any other.

Webflow caps CMS collections at 10,000 items on the Business plan ($39/mo). You can stretch to 20,000 with add-ons, and Enterprise pricing (starting around $50K/year) can push that to 50,000–100,000. But for most teams, 10,000 is the wall.

That sounds like a lot until you do the math. A blog publishing 3 posts per week hits 10,000 in about six years -- fine. But a real estate listing site with 5,000 properties, each tagged with locations and amenities? You'll blow through 10,000 CMS items in months because tags and references count against the limit too.

The deeper problem isn't just the count. Webflow's CMS has no aggregation functions -- no SUM, no COUNT, no multi-criteria filtering at the database level. You can't query across relationship levels. And when you export? You get flat JSON/CSV that loses all your references.

In 2025, Webflow shipped improvements: 2x collection lists per page, 5x nested lists, and 3-layer deep nesting. These help with presentation, but the raw item cap hasn't moved for standard plans.

What to use instead

For content-heavy sites, we move clients to a headless CMS paired with a modern frontend framework. Sanity.io is our go-to -- the free tier has no item limits, and the Growth plan at $99/mo gives you team features. Contentful works well for enterprise teams at $489/mo for the Premium tier.

We typically pair these with Next.js or Astro for the frontend. If you're curious about that stack, we've written about our headless CMS development approach and Next.js builds in detail.

2. No User Authentication or Member Dashboards

Webflow has no built-in login system. No user sessions. No authentication flows. If you need users to sign in, manage a profile, or access gated content -- Webflow can't do it natively.

Yes, third-party tools like Memberstack ($25–95/mo) bolt on authentication. But you're adding client-side JavaScript on top of a system that wasn't designed for it. There's no server-side session management, which means security depends entirely on the third-party embed. And you're now paying Webflow's hosting fees plus the auth add-on.

For anything that resembles a web application -- a customer portal, a SaaS dashboard, a membership community -- this is a dealbreaker.

What to use instead

If you want to stay no-code, Bubble.io ($29/mo Starter) handles users and privacy rules natively. For developer-led projects, Supabase (free tier, $25/mo Pro) gives you PostgreSQL-backed auth with row-level security. We use Supabase paired with Next.js for most client portals -- it's fast to build and you own the data completely.

3. Custom Code Embed Character Limits

Here's one that catches people off guard. Webflow enforces a 10,000-character limit on global custom code (the <head> section) and 5,000 characters per page.

That's not a lot. A single analytics setup with Google Tag Manager, cookie consent scripts, and schema markup can eat most of your global budget. Want to add A/B testing with Optimizely? Personalization with Segment? A chat widget? You're going to run out of characters.

And this limit doesn't increase on higher plans. Even Enterprise doesn't expand it. You end up loading scripts from external CDNs as a workaround, which adds latency and complexity for something that should be trivial.

What to use instead

WeWeb ($49/mo Pro) lets you inject unlimited code through its Vue.js-based builder. But honestly, if you're hitting code embed limits, you've probably outgrown visual builders entirely. A Next.js or Astro project gives you full control over every line of code in your <head> and beyond.

For quick wins, hosting utility scripts on Cloudflare Workers (free for 100K requests/day) offloads the character crunch without a full migration.

4. API Rate Throttling That Kills Integrations

Webflow's API caps you at 60 requests per minute on most plans. Enterprise bumps it to roughly 120/min. That's it.

To put this in perspective: if you're syncing CMS items to an external database and you have 10,000 items with pagination returning 100 per request, that's 100 API calls just to read everything. At 60/min, it takes nearly two minutes -- and that's assuming nothing else hits the API during that window.

Need real-time updates? Webflow's webhook support is limited to forms, orders, and basic CMS events. No webhooks for design changes, custom events, or granular updates. You end up polling, which burns through your rate limit fast.

What to use instead

Strapi (free self-hosted, $99/mo cloud) gives you uncapped REST and GraphQL APIs. Directus is another strong option with unlimited API access on self-hosted deployments. Both are open-source, so you can scale your infrastructure without permission from a vendor.

5. Zero Server-Side Logic

Webflow is a static site builder at its core. There are no server-side functions, no edge functions, no middleware. You can't process a payment without a third party. You can't resize an image on the fly. You can't run a cron job.

Every piece of dynamic behavior requires an external service: Zapier for automation ($29.99/mo Starter), Stripe embeds for payments, Cloudinary for image processing. Each integration adds another point of failure, another monthly bill, and another vendor to manage.

When clients come to us with a Webflow site that's accumulated five or six integration layers, the total cost often exceeds what a custom-built solution would have been.

What to use instead

Xano ($79/mo Unlimited) provides a no-code backend with API endpoints and serverless functions. For developer teams, Firebase (generous free tier, pay-per-use) or Supabase Edge Functions handle server-side logic without managing infrastructure.

Our preferred approach is a Next.js app with API routes or server actions -- you get SSR, middleware, edge functions, and everything runs in one codebase. Check out our Next.js development capabilities for how we structure these projects.

6. Static Page Cap at 100

Webflow limits you to 100 static pages on paid plans. Free and Starter plans get even fewer.

Dynamic pages (generated from CMS collections) don't count against this limit, which is fine if your content maps cleanly to collections. But many sites need unique static pages -- service pages, location pages, landing page variants for ad campaigns. A regional business with 150 locations can't create individual static pages for each one.

You can work around this by cramming everything into CMS collections, but then you're constrained by the CMS limitations from point #1. It's turtles all the way down.

What to use instead

Framer ($15/mo Mini) offers unlimited pages and ships with AI-assisted page generation. For larger projects, any static site generator -- Astro, Next.js, Hugo -- has no page limits at all. Hosting on Vercel or Netlify is often cheaper too.

7. Bandwidth and Asset Restrictions

Webflow's bandwidth caps scale with plan tier:

  • Free: 1GB/mo
  • Basic: 50GB/mo
  • CMS: 200GB/mo
  • Business: 400GB/mo

That sounds reasonable for text-heavy sites, but any project with video content, large image galleries, or downloadable assets can blow through it. Background videos are capped at 30MB per file. Overages force plan upgrades.

For context, Vercel and Netlify both offer unmetered bandwidth on their free and paid tiers (with fair use policies). You're paying Webflow for bandwidth that's essentially free elsewhere.

What to use instead

Vercel (free Hobby tier, $20/mo Pro) with a global CDN handles bandwidth without the anxiety. Pair it with Cloudinary or Mux for media delivery, and your asset pipeline is faster and cheaper than Webflow's built-in hosting.

8. Weak Filtering, No Aggregations

If you've ever tried to build a product catalog or directory in Webflow, you've felt this pain. The CMS has no support for:

  • Multi-criteria filtering (e.g., "show items where price < $50 AND category = shoes AND color = red")
  • Aggregations (count, sum, average)
  • Full-text search beyond basic matching
  • Complex relationship queries

The 2025/2026 nesting improvements (3 layers deep) help with display, but the underlying query engine hasn't changed. You can't sum a column of prices. You can't count items matching a condition. For anything beyond "list items in this collection, sorted by date," you'll need custom JavaScript -- which brings you back to the code embed limits.

What to use instead

Builder.io ($299/mo Pro) offers visual CMS with query-level filtering. But for real filtering power, use a headless CMS with GraphQL -- Sanity's GROQ query language is particularly good at complex filtering and aggregations. We've built product catalogs with 50,000+ SKUs on Sanity without breaking a sweat.

9. E-Commerce That Doesn't Scale

Webflow's e-commerce is fine for selling a handful of products. But it lacks:

  • Subscription billing (no recurring payments without third parties)
  • Multi-currency and multi-language (manual duplication required for translations)
  • ERP and inventory integrations (limited webhooks, API throttling)
  • Advanced product variants (limited options per product)

The Ecommerce Plus plan runs $39/mo per site, and you're still boxed in by CMS limits for product counts. Content is tied to design -- you can't reuse product data across a mobile app and website without rebuilding.

What to use instead

Shopify ($39/mo Basic) handles commerce at any scale with a massive app ecosystem. For headless commerce, Saleor (open-source) or Shopify's Storefront API paired with a Next.js frontend gives you full control. We detail this architecture in our headless CMS development capabilities.

10. Hosting Lock-In and Export Limitations

This is the one that keeps CTOs up at night. You can't fully export a Webflow site.

You can export HTML/CSS/JS on paid plans, but you lose:

  • CMS data relationships
  • Form functionality
  • E-commerce features
  • Interactions and animations (partially)
  • Hosting configuration

Webflow strips Cache-Control headers, you can't set custom server rules beyond basic 301 redirects, and there's no .htaccess equivalent. Your site lives on Webflow's infrastructure, and moving away means rebuilding.

Scaling costs jump dramatically: Business at $39/mo to Enterprise at $10K+/year. That's a steep cliff when you could host the same content on Vercel for $20/mo.

What to use instead

Any stack where you own your code. WordPress (free core) on Vercel via headless, or a Next.js + Sanity build deployed to any host. You own every file, every configuration, every redirect rule. Migration means git push, not a rebuild.

If you're currently locked into Webflow and evaluating a migration, reach out to us -- we've done this transition many times.

Comparison Table: Webflow Limits vs. Alternatives

Limitation Webflow Limit Best Alternative Alt. Starting Price Scale Advantage
CMS Items 10,000–20,000 Sanity.io Free / $99/mo Unlimited items
User Auth None native Supabase Free / $25/mo Full auth + RLS
Code Embeds 10K chars global Next.js/Astro Free (open source) No limits
API Rate 60 req/min Strapi Free / $99/mo Uncapped
Server Logic None Xano / Next.js $79/mo / Free Full backend
Static Pages 100 max Astro / Next.js Free Unlimited
Bandwidth 400GB/mo max Vercel Free / $20/mo Unmetered
Filtering Basic only Sanity (GROQ) Free / $99/mo Advanced queries
E-Commerce Basic shop Shopify $39/mo Full commerce
Export/Portability Partial HTML only Any headless stack Varies Full ownership

When Webflow Still Makes Sense

I don't want to leave the impression that Webflow is bad. It's not. It's a focused tool that does certain things very well.

Webflow is a great choice when:

  • You're building a marketing site with fewer than 50 pages
  • Your content team wants visual editing without developer involvement
  • You need to ship fast and the site won't grow past a few hundred CMS items
  • Design fidelity matters more than dynamic functionality
  • You don't need user accounts, complex filtering, or server-side logic

For everything else -- web apps, large content sites, e-commerce at scale, anything requiring authentication -- you're better off with a headless architecture from the start. The upfront investment pays for itself the first time you don't hit a wall.

We've seen the pattern repeatedly: teams start in Webflow, grow for 12–18 months, hit the CMS limit or need auth, then spend more money migrating than they would have spent building properly from day one. About 40% of Webflow users with content-heavy sites report migrating after hitting the 10K item ceiling.

If you're planning a project and wondering which approach fits, take a look at our pricing or get in touch for an honest assessment.

FAQ

What is the Webflow CMS limit in 2025?

Webflow's CMS caps at 10,000 items on the Business plan ($39/mo). You can add extra capacity in 10K-item increments for roughly $20–50/mo each, pushing to 20,000. Enterprise plans (starting around $50K/year) support 50,000 to 100,000+ items, but the exact numbers require custom negotiation. For most teams, the practical ceiling is 10,000–20,000.

Can you build a web app with Webflow?

Not really. Webflow has no server-side logic, no native authentication, no database beyond its CMS, and no ability to run custom backend code. You can bolt on third-party services like Memberstack and Zapier to approximate app-like features, but you'll pay more in add-ons and deal with more integration complexity than if you'd built with a proper app framework like Next.js or used a no-code app builder like Bubble.io.

What are the main things Webflow cannot do?

The top limitations are: no user authentication, a 10,000 CMS item cap, no server-side functions or API routes, limited custom code embeds (10K characters global), API rate throttling at 60 requests/minute, no advanced CMS filtering or aggregations, basic e-commerce without subscriptions, a 100 static page limit, bandwidth caps, and hosting lock-in with limited export options.

Is Webflow good for e-commerce?

For small shops selling fewer than 50 products with simple variants, Webflow's e-commerce works fine. For anything larger -- subscriptions, multi-currency, complex inventory management, ERP integrations -- you'll need Shopify or a headless commerce solution. Webflow's e-commerce is a feature, not a platform.

How do I get around the Webflow 10,000 CMS limit?

You have three options: pay for Enterprise (expensive), use CMS add-ons to push to 20,000 (still limited), or migrate your content to a headless CMS like Sanity.io or Contentful. The headless approach is usually the best long-term move because it completely removes the item ceiling and gives you API-first access to your content from any frontend.

What's better than Webflow for large websites?

For content-heavy sites, a headless CMS (Sanity, Contentful, Strapi) paired with Next.js or Astro gives you unlimited content, full code control, better performance, and lower hosting costs. For no-code alternatives with fewer limits, Framer offers unlimited pages and WeWeb allows unlimited custom code. The right choice depends on your team's technical capacity.

Can Webflow handle 100,000 pages?

Not on standard plans. Even with Enterprise pricing, you're pushing against CMS architecture that wasn't designed for that scale. A static site generator like Astro or Next.js with ISR (Incremental Static Regeneration) on Vercel handles 100,000+ pages routinely with build times under 10 minutes using on-demand generation.

Is it hard to migrate away from Webflow?

Yes, harder than it should be. Webflow's export gives you HTML/CSS/JS but strips CMS data relationships, form logic, e-commerce functionality, and some interactions. A migration typically means rebuilding the frontend in a new framework and moving content to a headless CMS. Plan for 4–8 weeks depending on site complexity. The sooner you migrate, the less content you'll need to restructure.