Am I not using Webflow CMS properly if I need more than 30 fields for each case study section? Can I add a non-collection section to a collection page in Webflow? Is there a better way to build case studies using Webflow that allows for more flexibility? Thank you.
TL;DR
- Break up content using Multi-Reference fields, linking a main Case Studies Collection to a Case Study Sections Collection for extra content.
- Use Rich Text Fields instead of multiple text/image fields to maximize efficiency.
- Add static sections to CMS pages for summaries, CTAs, or testimonials that don’t need to be in the CMS.
- Consider Webflow CMS API or JavaScript for complex cases requiring more than 30 fields.
If you find yourself exceeding 30 fields for a Case Study in Webflow CMS, you may need to reconsider how you structure your content. Below are ways to work around this limitation and create more flexible Case Studies.
1. Understand the Webflow CMS Field Limit
- Webflow limits CMS Collections to 30 fields per item (except in Enterprise plans, which allow 60).
- This can be restrictive for complex Case Studies with many text blocks, images, and rich media.
2. Use Multi-Reference & Single-Reference Fields
- Instead of storing all details in one CMS item, create related Collections:
- A Case Studies Collection with general details.
- A Case Study Sections Collection storing additional blocks of content (text, images, videos).
- Use Multi-Reference Fields to connect them.
- This allows a dynamic page structure using Collection Lists instead of a single CMS entry.
3. Add Static (Non-Collection) Sections to a CMS Page
- Yes, you can place non-collection (static) content on a CMS Collection Page.
- Simply drag a regular Section outside the dynamic Collection areas.
- Use this for elements like custom case study summaries, call-to-action sections, or testimonials added outside the CMS structure.
4. Use Rich Text Fields Strategically
- A Rich Text Field can contain formatted text, images, and even embeds.
- Instead of using separate text/image fields, consolidate content using a single Rich Text Field with structured content.
5. Consider Custom Code & API Workarounds
- Use the Webflow CMS API to store and pull additional data from an external database if necessary.
- Work with JavaScript to dynamically display hidden sections based on item details.
Summary
If you need more than 30 fields per Case Study, use Multi-Reference fields, Rich Text Fields, and static sections as workarounds. You can still add custom static sections to a CMS page for additional flexibility. If needed, consider external databases via API for high-content scenarios.