How do I delete a Collection field in Webflow?

Remove a field that nothing on the site uses

Open the CMS panel and click the Collection name. Open Settings, or the cog beside the Collection. Click the field, then click the trash icon.

That path works when the field is unused. Webflow's Collection fields article says you can delete any Collection field that is not used on the site, except default Ecommerce fields. Name and Slug come with every Collection. A custom field you added yourself, and never connected, is the simple case.

Example: a Blog posts Collection has a plain text field named Deck. No card, template, or setting reads it. Open Deck and use trash. Then publish the whole site. Manage CMS Collections says a schema change needs that publish before the live site reflects it.

Trash stays shut while something still uses the field

If the field will not delete, it is still connected. The Collection fields article says a field you cannot remove from Collection settings is likely tied to an element or a setting. Manage CMS Collections says the same limit in plain language: you cannot delete a custom field that is in use in your designs, on Collection pages and their settings, or on Collection lists and their settings.

Stop clicking trash. Find the connection. Webflow recommends a backup before you disconnect a field, because removing connections can affect the design and code embeds. Save that backup after the Designer shows your latest changes, and before you start unhooking the field.

A Price field on Products is a different block. Default Ecommerce fields cannot be removed. Trash is for a custom field you added, once nothing on the site still reads it.

Disconnect every use, then delete the field

First, open the CMS panel and click the Collection. Next, open Settings and click the field. Then click the view field connections icon. Hover a connection and click Disconnect, then confirm Disconnect. Repeat until that list is empty.

When nothing remains, use trash in Collection settings.

If trash still will not work, check the Collection page settings. The field may be used in SEO, Open Graph, RSS, site search settings, or custom code. Remove those uses, go back to Collection settings, and delete the field.

Example: Deck is bound to the excerpt on each blog card. View field connections shows that card. Disconnect it. The card no longer reads Deck. Trash can then remove the field. If Deck is also the SEO description on the Collection page, clear that setting too, or the field stays locked.

Check tools outside Webflow after the field is gone

Some sites send Collection fields to Zapier or to another app through the CMS API. After you delete the field, check those connections. They will not update themselves just because the Designer let you delete the field.

Webflow notes that restoring a backup after you delete a Collection field can still cause trouble for those integrations. Take the backup before you disconnect the design. Treat it as a restore point for the site, and still review any outside tool that mapped the old field.

You do not need an outside tool for an ordinary blog field that only appeared on the template. Disconnect, delete, and publish. Review Zapier or an API client only when you know the field left Webflow.

Publish the whole site and read the template

Deleting the field in Collection settings is not the last step. Publish the whole site so the schema change is what visitors get. Open the live template and the list that used to show the field. The old binding should be gone. Pages that still use other fields should show those fields as before.

If a spot is empty where the old text used to be, the element is still on the page and no longer has a field. Bind a different field, or remove the element, then publish again. The empty gap is the design catching up. It is not a sign that trash failed.

Leave Name and Slug in place. They are how each item is identified and addressed. Remove the extra field that editors no longer fill in, once every connection to it is gone.