How the Wix CMS Works: Collections, Dynamic Pages, and Limits

The Wix CMS stores repeating content — team members, listings, blog-style entries — as items inside a collection, and any dynamic page you build connects to that collection to display them. Wix's help center puts it plainly: "In Wix, any dynamic page that you add connects to a collection in your CMS (Content Management System). This way, you can automatically populate pages, by entering content in your collection" (Wix, "CMS: What is a Dynamic Page?", checked September 2026). Here's how collections, dynamic pages, plan-based limits, and content import/export actually work.

What is a collection, and what is a dynamic page?

A collection is the CMS's storage container — a set of items that share the same structure. A dynamic page is what displays that content on the live site: "A dynamic page is a page that can change its content, while keeping the same design and layout" (same source). The connection between the two is the point of the whole system: "Depending on the item viewed, any element connected to your collection will change. Any other element on the page remains the same" (same source). You design the page once, and every item in the collection reuses it.

What's the difference between a dynamic list page and a dynamic item page?

Wix builds two page types around a collection, and they serve different jobs. A dynamic list page shows multiple entries at once — Wix describes it as letting you "showcase various items from your CMS collection in an organized index" (Wix, "CMS: Adding and Setting Up a Dynamic List Page", checked September 2026), typically as a repeater, gallery, or table. Each item in that list links out to a dynamic item page — a single reusable template. Wix's own description: "Use dynamic item pages to instantly produce a large number of pages, each representing a different item from your CMS collection," acting as "a template, with each collection item getting its own unique version and web address" (Wix, "CMS: Adding and Setting Up a Dynamic Item Page", checked September 2026).

In practice: build a list page for browsing (a directory, a portfolio grid, a blog index), and a paired item page for the individual entry's full detail, the same relationship a collection page and a collection list have on other platforms.

What are the CMS item limits by plan?

Wix's help center gives specific collection-item ceilings, and they scale sharply by plan. Per plan, total items across all of a site's collections: Free (non-Studio) sites are capped at 1,000 items, Free sites on Wix Studio accounts at 10,000; among Premium plans, the Light plan allows 1,500 items, Core 4,000, Business 20,000, and Business Elite and Elite plans scale to 10,000,000 (Wix, "CMS: Understanding Collection Storage Limits and Quotas", checked September 2026). Total database storage follows the same tiering: Light, Core, and Business plans include 10 GB, while Business Elite and Elite plans get 100 GB, a figure the page states takes effect January 7, 2026. Each individual item is separately capped at 512 KB of field data, though media files are stored outside that limit.

If your content plan is genuinely large — a product catalog or directory in the tens of thousands of items — check your specific plan's item cap against your real content volume before you build around it, since jumping from Light's 1,500 to Business's 20,000 is a plan change, not a setting.

Can I import and export CMS content in bulk?

Yes, in both directions, through CSV. To export, Wix's help center describes going to CMS in the dashboard, opening the collection, and using "More Actions" to "Export to CSV" — you can export the entire collection ("all items and fields, including hidden and system fields"), filtered data, or just the field names for a template (Wix, "CMS: Exporting Content from Your Collection", checked September 2026). Non-Latin characters export as UTF-8, and time fields come out in UTC+0.

Importing has its own hard limits, worth knowing before you prepare a file: "The file size cannot be larger than 1 GB" and "the file cannot have more than 50,000 items," with a maximum of "1,000 total fields" (Wix, "CMS: Importing Content into a Collection", checked September 2026). Column mapping matters: if you don't map a CSV column to an existing field, "all the values in the field will be erased when the import is complete" — a real risk if you're doing a partial re-import, though this doesn't apply to system fields like ID or Created Date. Importing again with matching item IDs updates those existing items rather than duplicating them, which makes CSV a usable path for bulk edits, not just a one-time migration.

Who can access and change a collection's content?

Wix's permission system for a collection is more granular than a simple public/private toggle. You can set separate rules for who can view, add, update, and delete content, applied to different roles: "Admin" (site owners and CMS-admin collaborators, whose access can't be changed), "Collaborators" with CMS access, a member's own "Item's creator" role (permissions that apply only to items that member created), and "Members" generally (Wix, "CMS: About Collection Permissions", checked September 2026). At the simpler end, view and add permissions can also be set broadly to "Everyone" (any site visitor) or restricted to "Members only." This is what lets you build something like a public directory anyone can browse but only signed-in members can contribute to, without writing any custom code.

Do I actually need the CMS, or is a static page enough?

If every page on your site is genuinely one-off, a collection adds structure you don't need. It earns its place once you have several items that share a shape — team bios, case studies, a resource directory — where building a dynamic list-and-item pair once beats hand-building the same layout for every entry. For a broader look at how Wix's CMS compares to a fuller structured-content system, see how Webflow's CMS and Framer's CMS each handle collections, fields, and plan-based limits — the general shape (collection, item, list page, detail page) is consistent across all three platforms, even though the specific caps and permission models differ.

A quick planning checklist

• Does your content repeat in a predictable shape? That's a collection candidate.
• Do you need a list page, an item page, or both for this collection?
• Which item-count tier does your current or planned Premium plan give you, and does your real content volume fit it?
• Who should be able to view, add, update, or delete this collection's content — visitors, members, or only collaborators?
• If you're migrating content in, is your CSV under 1 GB and 50,000 items, with columns mapped to the right fields?

Where does Figment fit in?

Not here. Figment publishes a Figma design as a live website through its Figma plugin — it has no collections, no dynamic pages, and no CMS of its own. A site with repeating, structured content that needs a database behind it is a Wix, Webflow, or Framer job; Figment's route fits a design-led, mostly static site, not one built around a content collection.

Bottom line: the Wix CMS is a real structured database — collections, dynamic list and item pages, and a permissions model with separate view/add/update/delete rules — not just a label for a blog widget. Item limits scale from 1,000 on a free site to 10 million on Business Elite and Elite plans, CSV handles bulk import and export with a 50,000-item cap per file, and whether you need any of it comes down to one question: does your content repeat, or is every page genuinely one-off?