Show how close a user is to reaching the maximum number of uploaded assets
Show how close a user is to reaching the maximum number of uploaded assets
At a glance
A community member discovered a 200-asset limit per project in Webstudio, which they felt could be problematic for larger client projects. They suggested displaying the asset count and limit in the Project Settings panel to avoid surprises. Other community members responded, noting that the limit was set arbitrarily and could be increased. One community member shared that their site had 175 assets, mostly for design case studies, and they were likely to hit the 200-asset limit soon. The Webstudio team acknowledged the feedback and increased the asset limit for everyone.
I didn't realise there was a limit of 200 assets per project until I hit the limit.
If I was working on a client project and had a legitimate need for over 200 assets, I would've been in a real pickle. I probably would've already spent days building the site in Webstudio at this point, only to find out I would have to start again on a different platform.
I would suggest showing the user how close they are to this limit, and any other per-project limits, in the Project Settings panel, so they don't get caught off-guard.
it was done basically to avoid someone misusing the service as a storage or spam ,I am sure its not the case for you, so I am super curious to see your project
My site uses 175 image assets, and that's after going through and removing all the duplicates where I uploaded an asset, tweaked something about it after I saw it on the page, and then reuploaded a new version of it.
You're more than welcome to take a look at the project - its staging domain is portfolio-266c3
My design case studies have lots of screenshots and graphics in them, and I've got 4 full case studies on the site. I'm likely to 200 hit the limit for real if/when I add another case study in the future.
The testimonial profile images and small icons also make a fairly big chunk of the assets too
This is true, I agree. In Webflow I opted not to use a CMS because a) the price was too high for my limited use case (I would only need 1 collection, and that would be for the case studies) b) I liked being able to customise each case study's page template to fit the kind of work I did. Having static pages made it much easier to manage the layout changes between case studies.
My new style of case study is much simpler and would be more suitable to a CMS-driven template though, so I think that would have been an option for my new site