How do I group fields in a Webflow Collection?

Groups are labels for the people editing items

A long Collection is hard to scan when every field sits in one flat list. Field groups split that list into named sections. Webflow describes them as a visual aid. Grouping does not change how fields behave. It does not change item data, filtering, sorting, API queries, or the published site.

Site managers and designers can create, edit, reorder, and delete groups. The path is the CMS tab, then the Collection, then Collection settings. Groups cannot sit inside another group. Field groups are also unavailable on Ecommerce Collections, meaning Products and Categories.

Example: a Team members Collection has a photo, a short bio, an email, and a phone number. Two groups, Profile and Contact, make each person easier to update. The public team page does not change because those labels exist. Visitors never see the group names.

Create a group and move fields into it

Open Collection settings. Click Add group. Type a group name and a group description. Click Create.

You can then drag existing fields into the group. You can also click Add field inside the group and create a field there. A name such as Contact, with a description such as 'Email and phone for this person', tells an editor what the section is for.

When someone edits an item, they can expand or collapse each group. Webflow remembers that collapsed state for each team member. If you collapse Contact, it stays collapsed for you until you expand it. A colleague can leave the same group open. The memory is per person, not a setting you publish.

Four fields may not need a group. A Collection with a dozen fields usually does. Add groups when editors scroll past the field they came to update.

Rename a group or change the order

To rename a group, open Collection settings. Click the Options icon to the right of the group name. Click Edit. Change the name, the description, or both. Click Save.

To reorder, drag a group to a new position in Collection settings. The fields inside move with the group. Put the block editors need first at the top. Profile can sit above a notes group that only your team fills in.

Example: a group named Misc should have been called Press. Edit the name and save. The fields inside stay on the same elements they were already connected to. The live site does not gain a new heading, because the group name never published. Editors see Press the next time they open an item.

Deleting a group keeps every field

Deleting a field group does not delete any fields. Webflow moves those fields to the default Custom fields group, and they keep working. Open Collection settings, click the Options icon beside the group name, and click Delete.

Use that when the label is no longer helping. Use a different action when you want the field itself removed from the Collection. Removing the Contact group leaves email and phone on the item. Buttons that already read those fields keep reading them.

If a group description is stale but the fields are right, edit the description instead of deleting the group. Delete is for the label. It is not a cleanup tool for old content.

Skip groups on Products and Categories

Products and Categories do not support field groups. On those Collections you will not get the same Add group path. Leave their fields in the list Webflow already shows.

On a normal Collection, groups help a handoff. A new editor can open an item, expand Contact, and update the phone without hunting through SEO fields and image fields in one scroll. The published page still depends on how you bound each field in the design, not on which group holds it in the editor.

After you drag fields around, open one item and confirm the sections read in a sensible order. Then update a value you already show on the site, such as the phone number, and confirm the live page still prints the field it printed before. The group change should not be what changed that page.