Wix CMS Explained: Collections, Dynamic Pages, Backups and Roles

For a small business, that means one team page, one portfolio page or one listings page that grows as you add rows, without building a new page each time. The thing I'd want every owner to know before they start: restoring your site from site history doesn't roll back your CMS content. Pages and designs revert. Collection content and structure don't. For that you need CMS backups, which work separately.

The four parts of the Wix CMS

Part	What it does
Collection	A database of items, laid out like a table, where each row is an item and each column is a field
Field	Holds one type of content per item, such as text, an image, a URL or a document
Dataset	The invisible link between your page elements and a collection; it doesn't appear on your live site
Dynamic page	A page designed once that shows collection content; list pages show many items, item pages show one

Every collection has a Primary field, marked with a flag, which is called Title by default. Give each item a unique value there. Wix uses it to build the dynamic item page URL, and an item with an empty Primary field can't get one.

Getting started with collections

1. Open your editor and click CMS on the left, then Start Now or Add to site.
2. Pick a preset, which comes with a collection and dynamic pages, or start by adding your own content.
3. To build your own, go to CMS in your dashboard and click Create Collection.
4. Choose a Content collection, a Catalog collection for items you'll sell with cart and checkout, or a Category collection for grouping items.
5. Start from scratch, create it with AI, or import from a CSV file.
6. Name the collection, then use + Add Field and + Add Item to fill it.

Choose field types with care. Changing a field's type later can break links if that field's already used on your site, and you can't change the type of Primary fields, System fields, or fields in collections added to Wix Multilingual's translation manager.

Datasets and what visitors can do

Each dataset connects to one collection, and each connected element connects to one field. Pair a dataset with a repeater and you design one item that repeats for every row. The dataset mode decides what visitors can do:

• Read: elements display collection content but can't change it.
• Write: input elements add new content but can't display or edit existing content.
• Read and Write: elements display content, and input elements can add or edit it.

In dataset settings you also choose how many items load at a time, filters and sort order. If you turn on Random order, all other sorts and pagination switch off.

Dynamic pages and your page count

Dynamic list pages show many items in a repeater, gallery or table, and each links to a dynamic item page with its own URL ending. Wix says a site can have up to 298 pages, including up to 100 static pages. Dynamic and app pages may create a URL for every item, but only the main page counts toward that quota. That's the real reason to use the CMS for anything you'll list dozens of times.

Sandbox and live collections

A collection can have a live version, which visitors see, and an optional sandbox version for testing in the editor. On new sites the sandbox is disabled by default. If you switch it on, changes in one don't affect the other until you sync. Unsynced sandboxes are a common cause of content showing in Preview but not on the live site, and Wix also links them to 404 errors.

Import, export and the field you can wipe by accident

You can import from a CSV file and export to CSV for Google Sheets or Excel. Here's the trap. When you import into an existing collection, any field you don't map to a column has every value erased. System fields such as ID and Created Date are safe. Export first, edit the spreadsheet, then import it back with every field in it.

CSV import limit, as of October 2026	Value
Maximum file size	1 GB
Maximum items per file	50,000
Maximum fields	1,000
Delimiter	Commas only
Non-Latin characters	Encode the file in UTF-8
New catalog collections	Can't import directly; import into a content collection first, then convert it

Exports come in three flavours: the entire collection, only the filtered items, or just the field names. Time fields export as UTC+0.

Backups, history and what each one undoes

Wix keeps an automatic weekly backup of all your collections whenever you edit them, and you can save up to 3 manual backups. A fourth replaces your oldest. Restoring a backup permanently deletes changes made after that date, including visitor submissions saved since. Collections you created after the backup aren't removed. App collections from Wix Stores, Wix Bookings and Wix Events aren't covered, because their content comes from the app. To bring back one item, use item history instead.

Roles for teammates

Under Roles and Permissions you can create custom roles with CMS permissions: Manage Content, Edit Drafts, Manage Backups, Manage Indexes and Manage Collections. Backups and indexes also need Manage Content ticked, or the collaborator can't get into the CMS at all. Admin roles always get full CMS access, and you can't restrict that. For people who add and update items, set advanced collection permissions too.

Managing collections from your phone

In the Wix app, tap Manage, then Settings, then CMS. You can add, edit, duplicate and delete items, search, and switch to views you built on desktop. You can't change a collection's structure in the app, and default field values don't apply to items added there.

When content won't show

Most problems come back to four checks: every element's connected to the dataset, collection permissions let the right people view the content, the dataset mode fits the job, and your browser isn't blocking Wix cookies. Many can be traced from More Actions and View Connections inside a collection. If Preview works but the live site doesn't, publish again and sync the sandbox.

Is the Wix CMS worth setting up?

I'd set it up the moment you've got more than a handful of similar things to show, like team members, case studies, properties or events, because you design once and add rows forever after. Take a manual backup before any import. I'd skip it for a five-page brochure site, where the Wix Editor alone is quicker. If you're building for clients, the same CMS sits inside Wix Studio.

A CMS collection is a database, and once your content's structured like that, a lot of the copy-and-paste around it can be automated. I run AI training and workshops for teams, and help businesses with AI enablement and workflow automation, so the busywork runs itself and people get time back. Most of that work is with SaaS marketing teams and small businesses. Here's how we can work together.

Frequently asked questions

Does restoring Wix site history restore my CMS content?

No. Restoring site history reverts pages and designs, but the content and structure in your CMS collections aren't reverted. Use CMS backups to restore collections.

How many items can I import into a Wix CMS collection?

A single CSV file can hold up to 50,000 items and 1,000 fields, and can't be larger than 1 GB. Split bigger imports into separate files.

How many manual CMS backups can I keep on Wix?

Up to 3 manual backups. Saving another one replaces your oldest manual backup. Automatic backups are saved weekly when you edit collections.

Do dynamic pages count toward the Wix page limit?

Only the main dynamic page counts toward the quota, not each item or URL it creates. A Wix site can have up to 298 pages, including up to 100 static pages.

Can I edit Wix CMS collections on my phone?

Yes. In the Wix app you can add, edit, duplicate and delete items and search collections, but you can't change a collection's structure there.