CMS Collection

A CMS Collection in Bubble is a structured group of data that stores similar content together, like a list of blog posts or product records. It works like a table in a database.

Understanding CMS Collections helps you organize your app's content clearly. Without proper structure, your data becomes hard to query, display, or manage as your app grows.

Key Takeaways

• Structured content storage: A CMS Collection groups similar data entries so Bubble can retrieve and display them efficiently.
• Custom fields: Each collection holds fields you define, like title, image, date, or category, based on your needs.
• Dynamic pages: Collections power dynamic pages in Bubble, letting one page template display many different records.
• Repeating groups: Most collection data displays through Repeating Groups, which loop through entries and show each one.

What is CMS Collection in Bubble?

A CMS Collection in Bubble is a data type that stores structured content records in your app's database. You define the fields, and Bubble stores each entry as a separate record you can retrieve, filter, and display on any page.

Bubble treats your database like a set of tables. Each table is a data type, and a CMS Collection is how you think about those tables when you're managing content.

• Data type as collection: In Bubble, a CMS Collection is essentially a custom data type built to hold repeating content entries.
• Field definitions: You set the fields for each collection, such as title, body text, image, author, or publish date.
• Entry management: Each record in the collection is one piece of content, like a single blog post or a single product listing.

Collections in Bubble sit inside the Data tab. You can build them visually without writing any database queries or SQL commands.

How CMS Collection Works in Bubble

Bubble stores collection entries in its built-in database. You add fields to a data type, create entries manually or through workflows, and then retrieve those entries on your pages using Bubble's data expressions and Repeating Groups.

You build a CMS Collection by going to the Data tab and creating a new data type. From there, you add the fields that match your content structure.

• Adding fields: You pick a field name and choose a data type like text, number, date, image, or another data type.
• Creating entries: You add entries manually in the App Data tab, or your app creates them through user actions or workflows.
• Fetching on pages: A Repeating Group or text element can pull data from the collection using a "Do a search for" expression.

Once your collection is set up, any page in your Bubble app can query and display it. Filters and sorting let you show only the entries that match a condition. According to Bubble's official documentation on database structure, each data type acts as its own table.

Why CMS Collection Matters for No-Code Apps

CMS Collections are the foundation of any content-driven Bubble app. Without them, you cannot build blogs, directories, product catalogs, or any feature that requires storing and retrieving a list of records.

Most Bubble apps need some form of structured data. Whether you're building a job board, a course platform, or an e-commerce store, collections hold the core content.

• Scalable content: Collections let you add hundreds or thousands of entries without changing your page design at all.
• Dynamic pages: One page template can display every entry in a collection, saving you from building individual pages by hand.
• Searchable and filterable: Bubble's search expressions let users find specific entries based on field values, categories, or dates.

Teams building content-heavy apps should define their collections early. A clear data structure at the start saves significant rework later as the app grows in complexity.

How to Use CMS Collections With Dynamic Pages in Bubble

Set a page's type to your data type, then send the entry to the page when a user clicks on it. Bubble passes the record through the URL, and the page displays that specific entry's fields automatically.

Dynamic pages in Bubble are powered by CMS Collections. Each entry in the collection gets its own URL, making your content browsable and linkable.

• Page type setting: In the page settings, set the content type to match your collection's data type so the page knows what record to expect.
• Link with data: When linking to the page, use the "Send more parameters to the page" option to pass the specific entry.
• Display field values: Use dynamic expressions like "Current Page [DataType]'s Title" to pull the right content for each visitor.

This pattern is how Bubble developers build blogs, listing pages, and product detail views. It is one of the most used patterns across all types of Bubble apps.

Conclusion

CMS Collections in Bubble give your app a clean, queryable structure for storing content and records. Defining them well early makes your app easier to build, scale, and maintain. At LOW/CODE Agency, we've helped 450+ clients build and scale apps on Bubble and other no-code platforms. Our clients include global brands like Medtronic, American Express, Coca-Cola, Zapier, and Sotheby's.

Frequently Asked Questions

What is the difference between a CMS Collection and a data type in Bubble?

They are the same thing. In Bubble, a data type is the technical term, and CMS Collection describes how you use it to store content.

Can I import data into a Bubble CMS Collection?

Yes. Bubble lets you upload CSV files to populate a collection with existing data without entering records one by one.

How many entries can a Bubble CMS Collection hold?

Bubble supports large numbers of records, but performance depends on your plan. Higher plans support more database capacity and faster queries.

Can two collections reference each other in Bubble?

Yes. You can add a field of type "another data type" to create a relationship between two collections, like linking a post to an author.

Do CMS Collections in Bubble support images and files?

Yes. You can add an image or file field to any collection, and Bubble stores the uploaded file in its built-in file storage system.

Is a CMS Collection the same as a Bubble database table?

Functionally, yes. Each data type in Bubble works like a table, and each entry in the collection is a row in that table.