Fieldsets are almost functionally equivalent to Blueprints, except that they exist for you to be able to create reusable fields.

While Blueprints attach directly to content like collections or forms, Fieldsets are not directly attached to anything.

Fieldsets contain fields, just like Blueprints, but the benefit of using a Fieldset is that you can import their fields (or the whole thing) into other Blueprints. You can even import fieldsets into certain fieldtypes, like Grid, Replicator, or Bard.

Fieldsets can be a simple flat list of fields, or organized into sections when you want to group related fields together for reuse across blueprints.

There are 2 ways to create fieldsets:

• In the Fieldsets area of the control panel.
• Creating a YAML file in the appropriate place within resources/fieldsets/. More on that in a moment.

Once created, you can begin to define its fields.

Whether you manually create your fieldsets's YAML file, or use the control panel, they will all end up as YAML files in the resources/fieldsets directory.

resources/
  fieldsets/
    bard-image.yaml
    bard-quote.yaml
    common.yaml

You can even nest fieldsets in subdirectories to further organize them. Use . in the handle to indicate a subdirectory.

You can change where fieldsets are stored by setting the fieldsets_path option in config/statamic/system.php:

'fieldsets_path' => resource_path('fieldsets'),

At its most basic, a fieldset has an array of fields.

fields:
  -
    handle: content
    type: markdown
  -
    handle: featured
    type: toggle

Fieldsets can optionally organize their fields into sections, just like blueprints. This is useful when you're building a reusable set of fields that you want grouped visually (like SEO metadata, Open Graph tags, or address fields) wherever they're imported.

A fieldset uses either a flat fields array or a sections array. If you save a fieldset with a single, unnamed section, Statamic collapses it back down to the flat fields structure automatically.

title: SEO
sections:
  -
    display: Metadata
    fields:
      -
        handle: meta_title
        field:
          type: text
      -
        handle: meta_description
        field:
          type: textarea
  -
    display: Open Graph
    instructions: Controls how this page appears when shared on social media.
    collapsible: true
    collapsed: true
    fields:
      -
        handle: og_title
        field:
          type: text
      -
        handle: og_image
        field:
          type: assets
          max_files: 1

Each section supports the following keys:

As mentioned earlier, a Fieldset is not inherently attached to anything. In order to use a field (or fields) in a fieldset, you'll need to approach it from the Blueprint side.

See the Reusable Fields section of the Blueprint docs for more details.

When a blueprint imports a fieldset that has sections, you can control how those sections appear in the final publish form using section_behavior.

# blueprint
sections:
  main:
    display: Main
    fields:
      -
        handle: content
        field:
          type: markdown
      -
        import: seo
        section_behavior: preserve

The control panel surfaces this automatically — when you link a fieldset that contains sections, the "Section Behavior" control appears in the import settings, and a badge on the field indicates whether sections are being preserved or ignored.