The strongest Secure Custom Fields alternative for most sites is Advanced Custom Fields (ACF), the original plugin SCF was forked from, with the larger ecosystem, add-ons, and pro features. The best free option is Pods, which builds content types and fields together, while Meta Box is the most extensible for complex projects. We ranked these from our index of 55,000+ WordPress plugins.

Why people switch from Secure Custom Fields

• SCF is a fork that trails ACF’s own releases and pro features, so people wanting the source and its Pro tier move to Advanced Custom Fields (ACF).
• Developers who prefer defining fields in code rather than the UI move to CMB2 or Carbon Fields.
• Teams building complex custom content structures move to Meta Box or Pods.
• Users wanting content types and fields together in one free tool move to Pods.

Advanced Custom Fields (ACF) – The original plugin

Advanced Custom Fields (ACF), now owned by WP Engine, is the plugin Secure Custom Fields was forked from, with a mature UI, a large add-on ecosystem, and a Pro tier for repeaters, flexible content, and options pages. Against Secure Custom Fields, it has the fuller feature set and the paid Pro version SCF lacks. What it does not do: the most requested features, including repeater and flexible content fields, require the paid Pro licence.

Choose Advanced Custom Fields (ACF) if you want the original with its Pro features and ecosystem.

CMB2 – Code-first fields

CMB2 is a free, developer-oriented toolkit for building metaboxes and custom fields entirely in code. Against Secure Custom Fields, it suits developers who want fields version-controlled in their theme or plugin rather than clicked together in the admin. What it does not do: it has no visual field builder, so it is impractical for site builders who do not write PHP.

Choose CMB2 if you build fields in code and want them in version control.

Meta Box – Extensible projects

Meta Box, by MetaBox.io, is a lightweight, highly extensible framework for custom fields, with a large library of extensions for custom post types, relationships, and settings pages. Against Secure Custom Fields, it scales further for complex, developer-driven projects. What it does not do: much of its power comes through separate extensions, so a full solution can mean assembling and paying for several add-ons.

Choose Meta Box if you want a lean core you extend for complex custom content.

Pods – Content types plus fields

Pods is a free, community-maintained tool that creates custom post types, taxonomies, and fields together in one interface. Against Secure Custom Fields, it combines content modelling and fields without a paid tier. What it does not do: its interface is less polished than ACF’s, and its approach can feel unfamiliar to those used to a pure fields plugin.

Choose Pods if you want to build content types and fields in one free plugin.

carbon-fields – Developer code framework

Carbon Fields, from Htmlburger, is a free, code-based framework for defining custom fields, metaboxes, and theme options in PHP. Against Secure Custom Fields, it appeals to developers who want fields declared in code with no admin UI. What it does not do: it has no visual builder and a smaller community, so documentation and support are thinner than ACF’s.

Choose carbon-fields if you are a developer who wants a code-first fields framework.

When to stay on Secure Custom Fields

Stay on Secure Custom Fields if you want a maintained, WordPress.org-hosted fork that stays free and is backed by Automattic, especially if you only use core field types. It is API-compatible with much of ACF’s free feature set, so for basic custom fields there is little functional loss. Switching mainly matters if you need ACF Pro features or a specific ecosystem.

How we ranked these

Every plugin here is scored by the WPS Score, a single 0 to 10 rating built from 21 signals covering maintenance, support responsiveness, compatibility, performance, and ratings quality across our index of 55,000+ plugins. Rankings are derived from that data, not editorial preference, and no plugin author can pay to change a score. How the WPS Score works.

Frequently asked questions

What is the difference between Secure Custom Fields and Advanced Custom Fields?

Secure Custom Fields is a fork of Advanced Custom Fields created after a dispute between WP Engine and Automattic, and it is maintained on WordPress.org. It mirrors much of ACF’s free functionality, but ACF, owned by WP Engine, continues its own development and offers the paid ACF Pro tier that SCF does not.

What is the best free alternative to Secure Custom Fields?

For site builders, the free version of Advanced Custom Fields and Pods both offer visual field builders at no cost. Developers who prefer defining fields in code often choose CMB2 or Carbon Fields, which are free and version-control friendly.

Can I switch from Secure Custom Fields to ACF without losing data?

Because Secure Custom Fields is a fork of ACF, the two store field data in a compatible way, so most sites can move between them with care. Always back up first and test on staging, since field group settings and any Pro-only fields may need attention.

The verdict

For most sites the best Secure Custom Fields alternative is Advanced Custom Fields (ACF), the original with its Pro features and ecosystem. Meta Box suits complex developer projects and Pods those wanting content types and fields together for free. If you only need core field types and value a free, Automattic-backed fork, staying on Secure Custom Fields is entirely valid.