The custom fields plugin for WordPress, rebuilt from scratch for 2026.
Not just an ACF clone — a ground-up rebuild with custom table storage, typed APIs, and AI schema generation.
text, textarea, number, range, email, url, password
image, file, wysiwyg, oembed, gallery
select, checkbox, radio, true/false, button group
relationship, post object, page link, taxonomy, user
date picker, time picker, color picker
tab, accordion, message
repeater, group, flexible content, clone
PHP-rendered Gutenberg blocks
From a plain text field to a full repeater — every data shape you need, already built in.
Define your data model once — query it over REST, PHP, and GraphQL without writing a line of resolver code.
Every field is exposed over REST, PHP and a fully typed GraphQL schema — no resolver boilerplate. Same data, in your stack's idiom.
query { post(id: 42) { title fields { hero price gallery } } }
Postmeta hammers the DB with 12 JOINs for every field read. Field Forge queries a single purpose-built table — the difference is visceral.
No configuration wizards. No bloat. Install, define, build.
Every other WordPress custom fields plugin — ACF, SCF, Meta Box, Pods — stores field values in wp_postmeta. This works fine for small sites, but on sites with 1,000+ posts or heavy use of repeaters and flexible content, the N+1 query problem starts eating performance. A page that loads 20 posts with 10 fields each can fire 200+ SQL queries.
Field Forge ships with implementations of every major ACF template function: get_field(), the_field(), get_fields(), have_rows(), the_row(), get_sub_field(), get_row_index(), get_row_layout(), update_field(), delete_field(), get_field_object(). Plus support for acf_register_block_type() for PHP-rendered Gutenberg blocks.
Describe the field group you want in plain English, and the AI generates it. "Hero section with title, subtitle, background image, and CTA button" → a complete field group with 4 fields, correct types, and sensible defaults. Field Forge ships with 12 built-in templates (hero, FAQ, testimonials, features, pricing, team, CTA, gallery, contact, product, SEO, quicklinks) and falls back to an AI call for custom descriptions.
Field Forge auto-generates TypeScript type definitions (.d.ts) for every field group in your site. Plus GraphQL SDL output. Plus auto-registration with WPGraphQL if it's installed. For teams using Next.js, Astro, Nuxt, or any JavaScript frontend against WordPress as a CMS, this turns custom fields from a type-safety nightmare into a fully-typed API.
Every plan includes all 32 field types, custom table storage, the ACF compat layer, AI schema generation, TypeScript and GraphQL generation, the visual builder, local JSON sync, schema versioning, and every integration.
Yes. Field Forge implements the full set of ACF template functions (get_field(), the_field(), have_rows(), etc.) and supports acf_register_block_type() for PHP blocks. Theme code written for ACF or SCF keeps working after migration without changes.
ACF is the original commercial plugin, owned by WP Engine since 2022. SCF is WordPress.org’s free fork of ACF created in October 2024 during the WP Engine / WordPress.org dispute. Field Forge is a completely new plugin with modern architecture (custom table storage, AI features, TypeScript/GraphQL) that’s compatible with both. Complete comparison →
Yes to all three. Elementor dynamic tags read Field Forge values natively. Gutenberg custom blocks can use get_field() in render callbacks. WPGraphQL auto-registers Field Forge types when both plugins are active.
Yes — the ACF importer copies your field groups into Field Forge’s own storage, then runs a batched migration of all existing field values. After import, you deactivate ACF and Field Forge takes over. Your theme code is unchanged.
No. AI features route through our managed backend. Your first paid Forge activation grants the shared welcome credit pack once per account, and you can buy non-expiring top-up packs when needed.
Yes. Field Forge Free is on WordPress.org with unlimited field groups, 24 field types (including relationship, post object, taxonomy, and user), the visual builder, location rules, and the ACF compatibility layer. Paid plans unlock AI, TypeScript/GraphQL, the compound field types (repeater, flexible content, group, clone), options pages, and value migration tools.
14-day refund. One-click migration from ACF and SCF. Beta/manual mapping paths for Meta Box, CMB2, Carbon Fields, Pods, and Toolset.
Every Forge plugin runs on the same engine and design language — add the rest and they click together out of the box.