Secure Custom Fields is the WordPress.org fork of Advanced Custom Fields that the WordPress team adopted into the .org plugin directory. The plugin is API-compatible with ACF, so existing field groups, theme code calling get_field(), and postmeta keys all keep working. Field values still write to wp_postmeta with the configured field name as the key, and SCF reads them through the same internal functions the ACF community already uses.

SleekPixel reads SCF field groups through the SCF API and exposes each field group as a separate template scope. A field group attached to the 'post' post type with a 'subtitle' field, a 'cover_image' field and a 'reading_time' field can each feed template slots by name. The share card pulls SCF field values directly through get_field()-equivalent calls so it stays in sync with anything theme code uses.

The 1200 by 630 PNG lands in uploads on every post save. The SEO plugin's og:image filter publishes the URL into the post head, and scrapers see a card that reflects the actual SCF field values on every post update.

Secure Custom Fields, like ACF before it, exists because editorial teams need more structure than the default post fields provide. Subtitles, deck text, contributor name, reading time, sponsor flag, geo tag and translation status all show up as SCF fields on real editorial sites. The structure is the point: the team can rely on the subtitle being filled, the reading time being computed, and the contributor being attributed.

The investment in that structure pays off on the page and gets thrown away at the share preview, where scrapers see the featured image only. SleekPixel pushes the structure into the share. The card reads the SCF fields the team filled in, applies the brand palette and lands in uploads on every save.

Readers who share the post get a preview that names the same subtitle they will read once they click. The cost is one license. The benefit is field-aware share previews on every SCF-mapped post URL.