Streaming live at 10am (PST)

ETA for lift on 100 static page limit?

I would like to know where we are on removal of 100 static page limit.

Words can not describe the disappointment when while working on 95th page of my site, I was issued warning that only 5 pages remain and prompted to add hosting. I came to Webflow for responsive design features and the ability to export code, not to be force-fed CMS and hosting. And I certainly didn’t sign up to pay $16/mo for “responsive design (but only up to 100 pages).” Such critical and debilitating limitation should be clearly specified in the plan description, which it is not

One forum user notes being quoted “50% additional charge for 50 more pages.” Coming from static site background, the idea of page limit is ludicrous, and PAYING for additional pages, even more so. CMS is not suitable for all projects and for my particular site, needlessly complicated and an overkill.

Most other platforms do not impose this type of limit, and if they did, have lifted them. Here are a few:




It looks like others have been waiting a while on this As paying users, I believe we are owed a straight answer as to whether Webflow has intention to ever implement and if so, a timeline (days, weeks, months), so that an alternate solution may be identified if necessary. If nothing else, prospective users will learn from my experience and not find themselves effectively stuck in the middle of a project.

Please advise and thank you for your consideration.


I’m curious, what is the use case that needs more than 100 static pages? I imagine that maintaining 100 static pages would be more complicated than representing the common designs / relations with CMS data and templates.

The wishlist has status tags: future, in backlog, planning, development, beta, shipped. That wishlist item doesn’t have any of those statuses, so there isn’t an ETA. I’m sorry that we don’t have more info on this request for now.

I’ll ask about putting that limit on the pricing page.

1 Like

Thank you and I appreciate your comments. Site is primarily for presentation of images and once deployed, won’t need much updates or maintenance. I can’t use Lightbox, as it lacks the ability to customize (default black background, caption overlapping image, fixed font, etc.).

I also do not wish to go the CMS route in case site has to be moved to a different platform anytime in the future. I understand CMS may now be exported to CSV, but I’m not a developer and wouldn’t even know what to do with it as some others on this forum

Workaround I’ve found, is to use my allowance of 10 sites as staging areas so to speak. Generate the files, export, then put them back together locally before uploading to server. Not ideal and cumbersome at best, but it’s the most realistic solution I can come up with for now, especially considering time and resources already invested in getting up to speed with Webflow and this project specifically. Webflow works for me every other way and I’d love to be able to endorse it whole-heartedly. This, however, is a tough one to justify.

Anyone else experiencing or sympathetic to this issue, please vote for this wishlist. Thanks.

P.S. Apologies for “Weekly” autocorrect typo on original post (obviously meant “Weebly”).

+1 on the need for more than 100 pages. Collections are great, but not always the right tool for the job. Some reasons why Collections will not always work:

  • Inability to create nested URI structures that some clients require
  • Collections become too complex on some pages due to many components
  • Lack of design flexibility that some clients require
  • Collections as well have relatively low limits on qty and items that we run into and work around by building landing pages

As is, we cannot consider Webflow as a solution for large sites until the 100 page limit is removed and will have to recommend other competing solutions.

1 Like

I see Webflow’s philosophy of enforcing such limits as reasonable by conception, but too crude by implementation.

For example, this 100 page limitation could have been implemented by making a warning message appear upon trying to create your 101-st page. The message could have embedded gifs, displaying the possibilities of collections, plus an option, to request more pages for your particular account at an extra fee.

This would let Webflow know why you need more pages and why collections are not useful for you, at the same time. This is a feedback loop which would keep them creative in coming up with better solutions, while the automatic, “adamant” limitation approach keeps them in the dark about unexpected cases, where their philosophy turns out inadequte.

Also, in the pages panel there could be some notice saying “100 pages limit” with a question mark tooltip, explaining why. Same with pricing page. Otherwise people would think it’s a technical disadvantage instead of a planned constraint.

Large organizations need a higher limit, too. Not every page can fall under an Event, Blog collection, etc. There shouldn’t be a restriction on Enterprise plans.

1 Like

Hi, If I wanted more static pages what would Webflow charge me? So, I already have 100, and say I wanted another 100 static pages, what would the charge be? I am serious because it may be relevant to me. Thank you.

Email Ask them about solutions to get past 100 static page limit and request lifting the limit. Specifically mention not to be confused with CMS.

I got past 100 static page restriction on one of my sites and only payed a few bucks more a month for hosting additional pages.

good luck!

1 Like

Webflow has repeatedly stated that 100 static pages is a fixed limit and there was no option to increase it. Are you stating that they did? Please provide more details.


2017 or 18, I was working on a project when we hit the 100 static limit (we worked on a bunch of landing pages for google and facebook ads on about 100k/mo ads).

We had deadlines and my associates and myself pestered webflow everyday to increase the limit for at least a week. They eventually increased the limit and increased hosting fee for it.

Looking back, this might have been a one off thing.

That was the only time I hit the 100 page limit. I use CMS and subdomains for everything else now.

1 Like

Two major problems that have caused us high-page-count websites is 1) high-performance multi-lingual and 2) crude single-page CMS limits, which kill Designer performance, and must be split up (a direct recommendation by Webflow to us).

100 pages instantly turns into 50 with a mere two languages. A big CMS? “This hurts Designer performance. Split it.” The latter has nothing to do with rendered website speed, but Webflow’s own limited, poorly-managed Designer.

And, yes, for serious layout changes, it’s a nightmare. But Webflow has these walls setup everywhere, so I think some users are stuck between a rock and a hard place.

1 Like

Hi, None of this makes any sense to me. Right now Webflow is riding high, but decisions like this only cause some of its happy customers to resent it. Even if the company wanted to rinse every penny out of its customers, then why don’t they charge more for the extra pages and publish a rate page.

I can’t understand why we can’t have a page published around the 100-page limit because a lot of people seem to have an issue with it. As I said, although I resent paying for more pages, I would still pay more if the option was available. I would always like to stay within the 100-page limit as it’s in my interest, but I need to have that option.


1 Like