Support Log in
Comparison

Field Forge and Secure Custom Fields Compared

How Field Forge and Secure Custom Fields (SCF) differ: storage, ACF function support, importing SCF field groups. SCF facts as of October 2026.

Updated October 2026

Facts about other plugins on this page come from their WordPress.org listings or their own sites and were read in October 2026; they may have changed since. Facts about Field Forge come from its code.


About Secure Custom Fields (SCF)

Secure Custom Fields (SCF) is listed on WordPress.org by WordPress.org and shows 100,000+ active installations there (October 2026). Source: WordPress.org listing. The ACF and SCF guide has the background.


About Field Forge

  • Field values are kept in a table of Field Forge’s own, wp_fieldforge_values, not in wp_postmeta.
  • 35 field types, a visual field group builder, Local JSON sync and schema versioning.
  • It defines the common ACF template functions (get_field(), the_field(), have_rows() and others) and acf_register_block_type() for PHP blocks.
  • Pro adds AI schema generation and TypeScript and GraphQL type generation.
  • It has an importer for ACF and SCF field groups and values.

Moving from Secure Custom Fields (SCF)

  1. Back up the database and the files first. Use your host’s backup tool.
  2. Install Field Forge next to SCF. Field Forge’s compat layer only takes over once SCF is deactivated.
  3. Run the importer: Field Forge → Tools → Import from ACF. It copies the field groups and the values into Field Forge’s storage. Values are copied in batches of 50 posts through a background queue.
  4. Check the result. Field Forge does not compare it for you. The import screen shows the numbers of groups and errors; check a few posts and field groups against SCF yourself.
  5. Deactivate SCF. Field Forge’s compat layer takes over, and theme code that calls the ACF template functions it defines keeps working.
  6. Check the same pages again. If something looks wrong, reactivate SCF and contact support.

Read the migration guide →


If you stay with Secure Custom Fields (SCF)

If SCF already covers your site, keep it. The importer does most of the copying, but you still check the result yourself.


Frequently asked questions

Will my SCF code still work after migration?

Field Forge defines get_field(), the_field(), have_rows(), get_sub_field(), update_field(), delete_field() and acf_register_block_type(), among others. Theme code that calls these keeps working after you deactivate SCF. Code that uses other functions or hooks needs a check.

How does the SCF importer work?

Field Forge → Tools → Import from ACF copies your field groups and then your values into Field Forge’s storage, in batches of 50 posts through a background queue. The import screen shows the numbers of groups and errors. Check a few posts yourself.

Can I run SCF and Field Forge together?

During the migration, yes: install Field Forge next to SCF. Its compat layer only takes over once SCF is deactivated.

What does Field Forge cost?

See the pricing page. Paid plans have a 14-day refund. AI credit packs are sold separately.

Where does Field Forge store field values?

In a table of its own, wp_fieldforge_values, instead of wp_postmeta.

What is the difference between ACF and SCF?

ACF is listed on WordPress.org by WP Engine and shows 2+ million active installations there (October 2026). Secure Custom Fields (SCF) is listed there by WordPress.org and shows 100,000+ active installations (October 2026). Field Forge can import field groups and values from either one.

Does Field Forge help with headless WordPress?

Pro has a Headless Types panel with Generate TypeScript and Generate GraphQL buttons, and Field Forge has a REST API. With WPGraphQL active, Pro registers its types there.


Try Field Forge

See pricing → 14-day refund on paid plans. AI credit packs are sold separately on the pricing page.

FAQ

Frequently Asked Questions

Field Forge defines get_field(), the_field(), have_rows(), get_sub_field(), update_field(), delete_field() and acf_register_block_type(), among others. Theme code that calls these keeps working after you deactivate SCF. Code that uses other functions or hooks needs a check.

Field Forge → Tools → Import from ACF copies your field groups and then your values into Field Forge’s storage, in batches of 50 posts through a background queue. The import screen shows the numbers of groups and errors. Check a few posts yourself.

During the migration, yes: install Field Forge next to SCF. Its compat layer only takes over once SCF is deactivated.

See the pricing page. Paid plans have a 14-day refund. AI credit packs are sold separately.

In a table of its own, wp_fieldforge_values, instead of wp_postmeta.

ACF is listed on WordPress.org by WP Engine and shows 2+ million active installations there (October 2026). Secure Custom Fields (SCF) is listed there by WordPress.org and shows 100,000+ active installations (October 2026). Field Forge can import field groups and values from either one.

Pro has a Headless Types panel with Generate TypeScript and Generate GraphQL buttons, and Field Forge has a REST API. With WPGraphQL active, Pro registers its types there.

Ready to switch

Ready to Switch to Field Forge?

Every feature is in every paid plan. Starting at $40/yr.

Forge AI Assistant Online

Hi! I'm the Field Forge AI assistant. Ask me anything about the plugin — setup, features, troubleshooting, or development.

Just now
Powered by Forge AI · Browse docs