The CMS field types you can use and how they map to ACF — text, wysiwyg, number, select, image, gallery, date, color, url, relationship, oembed, and more.
Where: CMS → field type picker — Pick a field type
Key ideas
- Rich type set: text/textarea/wysiwyg, number/range, checkbox/boolean/radio/select, image/file/gallery, date/time, color/url/link, email/tel, relationship, oembed.
- Page/term fields: Special page-* and term-* fields bind to WordPress page/taxonomy data.
Steps
- Add a field to a collection.
- Pick the closest field type for the content.
- Bind an element to it.
Common type families
- Text: text, textarea, WYSIWYG, email, telephone, URL/link.
- Number/choice: number, range, checkbox, boolean, radio, select.
- Media: image, file, gallery, oEmbed.
- Time/appearance: date, time, date-time, color.
- References: relationship and page/term-specific fields.
Pick by data semantics
Choose the type that represents the stored content, not merely how it looks in one component. A URL is not plain text, an image is not only its rendered URL, and a relationship is not a duplicated label.
Limitations and important notes
- Changing an exported field’s machine name or type after WordPress content exists can require migration.
- The destination needs compatible ACF/WordPress configuration.